FWIW, quitting Xcode and purging the folders mentioned by @SubvertDev allowed me to resolve the package dependency error. Im on Xcode 16 on macOS 14.5, and had the error in a fairly large Xcode Project with lots of dependencies.

I was able to get a key frame decoded by ensuring I properly populate the extra data for the CMFormatDescription, but have yet to get GOP frames working.

Ah, so this appears fixed in macOS 15. Older Virtualization Framework systems (ie older hosts) won't work. https://developer.apple.com/documentation/virtualization/using_icloud_with_macos_virtual_machines Can we get confirmation that: macOS 14 (13, 12, 11 etc) running as a guest on a macOS 15 workstation would get a Secure Enclave identity allowing the macOS 14 (13, 12, 11 etc) guest OS to sign into iCloud, use Xcode, etc?

This really needs to be resolved. The ability to test, debug, and build apps in professional workflows requires ease of setting up VMs and debugging apps. Xcode requires Apple ID login, which does not work in a VM like UTM. This means I can't easily debug my software on new OS'es without updating my entire system? Thats insane in 2024 with containerized workflows as a defacto standard. Come on.

I haven't had a chance to test my vanilla m1 for performance numbers, but it seems like macOS 12.3 has fixed the H11ANEDevice::H11ANEDeviceOpen kH11ANEUserClientCommand_DeviceOpen call failed result=0xe00002bc error I have also been getting on M1 Pro / M1 Max systems.

@ccmargo - totally concur. Its beyond me why this is now a critical error.I cant even strip a universal library down to its x86_64 arch in a script file phase, it errors prior to hitting the script. This is a huge disruption to developers who rely on 3rd party tooling.Why does Apple constantly have to re-invent the wheel?