Feedback Assistant report: FB25173765.
I am investigating an iOS Simulator runtime verification failure on an Apple M1 Mac:
- macOS 27.0.1 (26A434)
- Xcode 27.1 RC (27A9275)
- CoreSimulator 1174.9.2
- iOS 27.1 RC Simulator runtime, arm64, build 24A94232
The official download/export command completed successfully:
xcodebuild -downloadPlatform iOS -exportPath <export-directory> -buildVersion 27.1 -architectureVariant arm64
It registered the runtime and produced a complete .exportedBundle, including ExportedMetadata.plist, BuildManifest.plist and the Cryptex support files. Xcode's required components are installed, and xcodebuild -checkFirstLaunchStatus returns 0. Updating macOS from 27.0 to 27.0.1 did not resolve the verification failure.
xcrun simctl runtime list -j reports a Ready “Patchable Cryptex Disk Image” with signatureState Unknown. Running:
xcrun simctl runtime verify <runtime-image-identifier>
returns exit code 1 with:
Signature verification failed: (-67054 a sealed resource is missing or invalid
The registered iPhone Duo simulator has not been booted. No security protections, signing settings or quarantine attributes have been changed, and the existing runtime has not been forcibly removed.
Xcode 26.4 release notes, issue 166834291, document secure import of the complete .exportedBundle with xcodebuild -importPlatform. I have not yet run that separate import.
Is reimporting the complete bundle a supported recovery for this failure? Does the importer reuse an already registered identical build, and what additional or temporary internal disk space should be reserved? If a different recovery is appropriate, could Apple provide a supported procedure that retains signature and Cryptex validation? Also, is simctl runtime verify the appropriate validation for this runtime format?
I have seen community reports involving the inner DMG, but have not assumed those are a confirmed fix or that their validation is equivalent. I would appreciate an official recommendation before proceeding.