User Profile

No iCloud support is an M1 VM was a terrible decision made by Apple. I cannot test my own software that has Sign on with Apple on an M1 VM. Can't use any iCloud storage that an app might use during testing on an M1 VM. I cannot build software with a Apple Developer account on an M1 VM. I am being redundant here to make this painfully clear. Please add in this feature and support iCloud 100% inside a VM. Please don't make it terribly hard for any VM author to support like forcing them to get an unobtainable highly restricted entitlement. This should have worked out of the box from day 1. It should just be a flag in the framework such as, iCloud supported YES or iCloud supported NO via an info.plist. Whoever chose not to allow iCloud within an M1 VM wasn't considering the implications this has on all Apple Developers. Because of this, I have to do all test directly on bare metal.

The virtual keyboard thing did not work for me. Then I realised I was accessing our file server third Remote Desktop and directly on the computer. Plugging in a keyboard and mouse to the Server allowed my to turn on JavaScript Apple Events in Safari and set the password.However, you can't always do this, so the next best thing is use an accessbility scripting feature and have the machine think a user is doing the clicks, allowing you to set the password:-- The delays can be shorter, coordinates may vary-- Best way to get the coordinates is with Apple screen capture (command-shift-4) from upper right to lower left-- if one spends the time, the click events can be converted to Accessibility AppleScript objects by capturing them as variables, or checking the events and using the events instead of the click coordinatestell application "System Events" tell application "Safari" activate end tell delay 1 -- click develop menu (make sure its on first) click at {430, 12} delay 1-- click Allow Javascript menu from Apple Events click at {615, 615} delay 1 -- Click the Allow Button click at {1010, 386}end tell