I cannot use my Apple ID in macOS 13

[fluxbeard]

Hi,

i have successfully installed macOS 13 Ventura Beta 2 with the workaround from macOS 12.4 Image with beta profile. But now I cannot log in with my Apple ID. I always get a message : "Verification failed. The Action could not be completed."

What can I do?

[robfeldmann]

Unfortunately this is a known limitation for VMs running on Apple Silicon (maybe all VMs?):

@_inside

You can’t sign in with an Apple ID for iCloud or other services, but Xcode works just fine (including logging in with a developer account). It’s not as fast, obviously, but I have done some “real” work with Xcode running within the VM and it’s been fine.

There's a developer forums post as well (h/t @chockenberry) that you should read and file a feedback.

In beta 1, I was unable to sign in to my developer account in Xcode, but with beta 2 and this repo that is now possible at least.

[victoraraujo01]

Hi @robfeldmann! Did you have to do anything before being able to sign in to your developer account on Xcode or it just worked?

I'm currently on beta 2 of both Ventura and Xcode (and using the latest release of VirtualBuddy) but I'm still getting the "Action could not be completed" message.

[robfeldmann]

It just worked for me this latest time. I don't recall doing anything special. 🤔

[ddaddy]

It's not working for me either. I get The action could not be completed. message on Beta 3.

[voidref]

One workaround for the Xcode account issue is to "Export Apple ID and Code Signing Assets..." from the Apple IDs pane of the Accounts pref in Xcode and then re-import them in the VM version of Xcode.

[kikeenrique]

I've tried this and after importing session appears as expired, and trying to login still fails.
Using latest macOS 13 beta 3 Update.

[ddaddy]

I tried this also. Transferred my assets to the VM. I can't build and run a MacOS app through Xcode as it wants me to select a team. I also have trouble getting a host built Mac app running in the VM.

[HarshilShah]

Running into this same issue, I can't seem to log into Xcode at all. Anyone able to get it working?

[kikeenrique]

I've been researching a bit about this topic and it seems related to hardware validations that are not valid in the case of Apple virtual machines.
Check UTM gathered info here: UTM - 3617 - macOS Guest - App Store/iCloud Login Failure
It maybe possible to tune NVRAM to simulate real hardware, but I've not tested it.
I've seen that VirtualBuddy already has code to play with NVRAM variables.
So the question now is, tuning them would make login work?

[krlmlr]

I thought I had to use my Apple ID to upgrade to a beta version of the OS, but #194 worked without that for me.

[insidegui]

Good news from WWDC: it looks like Virtualization is getting official support for Apple ID / iCloud

[rismay]

Tried this (macOS 15 + macOS 15 VM) but it didn't work for me. Hopefully soon

[wojciech-kulik]

It still doesn't work with macOS 15 Beta 3. Doesn't it require some integration on VirtualBuddy side?

[insidegui]

@wojciech-kulik Nope, it's automatic. It's working for me here. As a reminder both host and guest must be running macOS 15 Beta 3, and this only works for iCloud login, not other Apple Account features (such as App Store or Xcode sign in)

See: #366 (comment)

[wojciech-kulik]

Meh Apple... it's very limited then. The purpose of using VM on my machine is to avoid installing Beta versions directly... Anyway, thank you for the hint!

[FelixLisczyk]

There is a known issue listed in the Xcode 16 release notes, so it might be fixed in the future.

(Virtualization/Known Issues) When running in a virtualized macOS environment, Apple ID sign-in is not supported in Xcode. (127624414)

https://developer.apple.com/documentation/xcode-release-notes/xcode-16-release-notes