From gpt-5 with max context after explaining the situation and using the test project's code as context: APNs registration in iOS Simulator does not reliably work in virtualized macOS (GitHub Actions VMs, Anka, etc.). The simulator’s APNs path depends on host hardware services that aren’t fully available/exposed in VMs, so callbacks may never arrive (neither success nor failure). This matches your observation that it always works on bare metal but never in the VM. Simulator APNs registration does not consistently work in virtualized macOS. Validate notification UI/delivery in CI without APNs. Use xcrun simctl push to inject a notification payload locally (no device token required). Your permission UI test already handles the prompt.

Got it. ❯ xcodebuild -downloadComponent metalToolchain Beginning asset download... Downloaded asset to: /System/Library/AssetsV2/com_apple_MobileAsset_MetalToolchain/4ab058bc1c53034b8c0a9baca6fba2d2b78bb965.asset/AssetData/Restore/022-17211-415.dmg Done downloading: Metal Toolchain 17A324. ❯ xcodebuild -importComponent metalToolchain [1] 72228 trace trap xcodebuild -importComponent metalToolchain

Thank you! Would love to see these kinds of posts for any new releases too :)

FB22313446

❯ pkgutil --pkg-info-plist com.apple.pkg.MobileDevice <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>groups</key> <array> <string>com.apple.findsystemfiles</string> </array> <key>install-location</key> <string>Library/Apple/</string> <key>install-time</key> <integer>1772135996</integer> <key>pkg-version</key> <string>4.0.0.0.1.1762585687</string> <key>pkgid</key> <string>com.apple.pkg.MobileDevice</string> <key>receipt-plist-version</key> <real>1</real> <key>volume</key> <string>/</string> </dict> </plist> I can't reply in the thread above as a comment due to limited text amount.

I extracted the MobileDevice.pkg from 26.4 Xcode and installed it on 15.x. I can now create a VM for the 26.4 release.

Little request for the devs at apple: Please make these MobileDevice pkgs available on the downloads site for every release. I shouldn't need to download the whole Xcode.app and extract it manually each time I need this pkg. <3

Weirdly I had to install it twice on one older M1. I did it first with sudo installer -pkg MobileDevice-26.4.pkg -tgt / and then had to use the GUI to install. Just FYI for anyone who has the same issue

FB: FB22492511

No log in to the GUI at all, then run the tests.

To further clarify: Unless autologin is enabled or we sign in to the GUI/VNC with a user, we can't do much of anything with macOS VMs.

Hmm, yeah, I tried the unlock method already. That was a solution at some point according to google, but honestly I've never had to use it. I tried and the error is still: Thu Apr 16 10:07:11 40 5a27c75d-0a35-4aeb-9ec1-e77e77f66210.log (ankahv) 578: 5a27c75d-0a35-4aeb-9ec1-e77e77f66210: failed to start: Error Domain=VZErrorDomain Code=-9 "The virtual machine encountered a security error." UserInfo={NSLocalizedFailure=Unable to access security information., NSLocalizedFailureReason=The virtual machine encountered a security error., NSUnderlyingError=0x8df12c450 {Error Domain=NSPOSIXErrorDomain Code=22 "Invalid argument" UserInfo={NSLocalizedFailureReason=Failed to get current host key., NSUnderlyingError=0x8df12c030 {Error Domain=NSPOSIXErrorDomain Code=22 "Invalid argument" UserInfo={NSLocalizedFailureReason=Failed to create new HostKey., NSUnderlyingError=0x8df12c090 {Error Domain=NSPOSIXErrorDomain Code=22 "Invalid argument" UserInfo=0x8decadd40 (not displayed)}}}}}} My concern is that this was fine and worked without issue, leading me to believe this is a regression not an enhancement request. We only started seeing this fail when we upgraded to 26.4.1 host OS. Are there any other logs or tests I can run to help clarify this for the team?

Ok, sorry about this. I just tried manually and it looks like the error message on a 15.x host is different and wasn't being caught on our end. Does not look like a regression anymore. And this is using unlock-keychain too. I need to dig a bit more on my end. It's unclear to me how this has been working on AWS EC2 Mac since they don't have a logged in user to the GUI.

Opened FB22523292 as suggestion

AHA, fixed. I had to do these on the host. Something was wrong with the host's password I guess :shrug: sysadminctl -oldPassword "${PW}" -newPassword "${PW}" security unlock-keychain -p "${PW}" ~/Library/Keychains/login.keychain-db