FB: FB22492511

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

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

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.

❯ 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.

FB22313446

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

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

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.

By default Anka VMs have SIP and Firewall disabled. I can reproduce on a vanilla macOS VM using the latest 16.4 Xcode, Simulators etc. I don't see any ~/Library/Logs/CoreSimulator/ logs indicating a problem there. I've generated a sysdiagnose from the VM right after reproducing the issue which should be helpful for the Apple team: https://drive.google.com/file/d/1tkbnm8bxuJwlAoAU6-0u1_v-LeQpt95D/view?usp=sharing

Nevermind, I had to security unlock-keychain first

Looks like it may be fixed in 15.3 Mac-mini:~ anka$ xcrun simctl list devices --json | head { "devices" : { "com.apple.CoreSimulator.SimRuntime.iOS-18-2" : [ { "dataPath" : "\/Users\/anka\/Library\/Developer\/CoreSimulator\/Devices\/DE110594-CF92-470F-B10E-5636C4CD9EBC\/data", "dataPathSize" : 18337792, "logPath" : "\/Users\/anka\/Library\/Logs\/CoreSimulator\/DE110594-CF92-470F-B10E-5636C4CD9EBC", "udid" : "DE110594-CF92-470F-B10E-5636C4CD9EBC", "isAvailable" : true, "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-16-Pro",

Bump, same here.

Veertu has built Anka Virtualization to get as close as possible to Docker/containers as possible on macOS (intel and arm). You can use it to run ephemeral macOS VMs from templates of different version of macOS. We have plugins for almost all of the commonly used CI/CD platforms, like Jenkins, Github Actions, etc.

Bug number: FB16084148