AppleID Login failing in virtualized OS

Logging in with my Apple ID anywhere in the system (feedback assistant, Xcode, iCloud, etc.) fails when running under virtualization. Is this a known 'issue'? (networking in general is working fine)

Answered by DTS Engineer in 790410022

Apple just started seeding macOS 15 beta, where the Virtualization framework supports iCloud logins for macOS 15 guests. For the details, see Using iCloud with macOS virtual machines.

IMPORTANT This requires macOS 15 as both the guest and the host.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

I learned about virtualisation possibilities with macOS and Apple Silicon in videos from WWDC 2022. I bought a MacBook Pro M1 with 64GB RAM and 2TB disk storage so I can run several VMs for my use cases.

Beside some use cases described above I want to mention the usage of Homebrew and MacPorts. With VMs it is possible to use both.

I created a VM for testing how to compile Joplin for Apple Silicon. A VM allowed me to use HomeBrew while I have MacPorts installed on my physical system. The usage of an Apple ID in a VM is essential to have the same workflow as in a physical system (Xcode, notarise, etc... ).

We are having the same issues as everyone else. I had hoped the virtualization framework would be more useful, but the inability to login to our developer account means we can't sign our apps within Xcode or test them via the App Store. I filed FB11839055.

This is a real "got to have"!

This is a key requirement to make macOS Guest virtualization useful.

The feature is complete useless without appleID log in

Does anyone know how the AppleID authentication is being blocked in virtual machines? Does it look like an intentional macos limitation, or a security feature of some kind?

This is essential.

I need to be able to setup and teardown virtualized software development environments for various reasons. That requires the ability to download and install Xcode on a virtual machine. As it stands, I cannot download and install Xcode on a virtualized Mac OS machine and therefore cannot do what I need to do.

Please prioritize a fix for this!

There are just too many things that appear to be not working if not signed in into iCloud. The list could go on and on, but here is the latest road block that I've bumped into: I've tried installing an extension for Safari and guess what -- I need to sign in with Apple ID on App Store! So, no installing and testing even on this front.

I wish it was much simpler than this, but it looks like the ability to sign in with Apple ID is a must!

yep, this is nuts. Needs resolving. Would love to use my Mac Studio for both my home and work, but they need to be entirely separate from a data perspective and a management one. Simple solution, beaten down entirely by this.

Extremely frustrating. I just purchased a shiney new M2 doorstop. I love the 'idea' of Apple Silicon, but for virtualization it's awful. I was resigned to compromising my needs and using a Dell XPS for virtualizing my Windows/Linux environments, but I bit the bullet and bought a nice M2 MacBook Pro with 32Gig of ram specifically and only to virtualize my macOS environments. I tried using UTM, ran into this issue and figured that UTM might be a little flaky, so I bought Parallels and had the same issue - which is ridiculously infuriating. Using your Apple Id is central to the macOS experience, its tentacles reach into everything, if it doesn't work, then macOS (effectively) doesn't work either. It's the equivilent of saying, "macOS works in a vm, but there isn't any mouse support!" - it's bonkers. I am pleading, Apple, please, please address this!

Not only did it not work, but IT DIDN'T SAY WHY IT DIDN'T WORK. I like to run a VM here and there to compartmentalize work without polluting my main environment. I can add a bunch of apps by direct download, but I can't install ANYTHING from the App Store, sign into Music, etc. Do you want to encourage me NOT to use Apple's ecosystem?

New MacBook Pro M2 Max, 64GB ram, 2TB hdd. 67 freaking billion transistors... Cannot basically work with a virtualized environment. If I would have known about that limitation, I probably would have bought a System76 linux machine. On the other hand I would have surely miss the great battery times. But seriously guys, we do not buy powerful machines like that just to surf the web and read e-mails. I did spit quite a good amount of cash for an extra 32GB just for that reason (virtualization). So that issue has been dragging for a year now and people in this thread have enumerated a nice extensive list of valid reasons why we need the feature. At least let us know if you're not planning to do anything about it (so I can go another direction for my development workflow)

I am trying to use a Monterey VM because Ventura cannot properly handle printer settings which makes Ventura worthless for running professional tools like a RIP.

Now this problem is rearing its ugly head. There is some Apple software which I would also like to use.

It is dismaying that Apple has created this dismal situation.

This is a big problem for us, too.

AppleID Login failing in virtualized OS
 
 
Q