ENVIRONMENT
Device : MacBook Pro 16,1 CPU : 6-Core Intel Core i7, 2.6 GHz RAM : 16 GB DDR4 GPU : AMD Radeon Pro 5300M + Intel UHD 630 macOS : 26.5 (Build: 25F71) Xcode : 26 (also tried Xcode 16 — same issue)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
ISSUE SUMMARY
Xcode crashes immediately on launch after updating to macOS 26.5. The issue started right after the macOS update — Xcode was working perfectly before.
Both Xcode 26 and Xcode 16 are affected. Fresh reinstall does not help.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
ERROR — xcodebuild -version output
dyld: Library not loaded: @rpath/DVTSystemPrerequisites.framework/ Versions/A/DVTSystemPrerequisites
Reason: code signature in DVTSystemPrerequisites.framework not valid for use in process — mapping process is a platform binary, but mapped file is not.
zsh: abort xcodebuild -version
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CRASH REPORT DETAILS
Incident ID : 370D1162-4CA5-4FFE-9193-45EBD350BF85 Exception : EXC_BAD_ACCESS (SIGKILL — Code Signature Invalid) Termination : CODESIGNING, Code 2, Invalid Page Crash Date : 2026-05-14
Failing Frameworks:
- DVTSystemPrerequisites.framework
- MobileDevice.framework (/Library/Apple/System/Library/ PrivateFrameworks/MobileDevice.framework)
Crashed Thread 7 Stack:
- dyld3::MachOFile::trieWalk
- dyld4::Loader::hasExportedSymbol
- dyld4::JustInTimeLoader::applyFixups
- _CFBundleLoadExecutableAndReturnError
- -[NSBundle loadAndReturnError:]
- __watchForSims_block_invoke
- -[OSActivityStream setDeviceDelegate:]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
WHAT I HAVE ALREADY TRIED
- sudo xattr -cr /Applications/Xcode.app
- sudo codesign --force --deep --sign - /Applications/Xcode.app
- sudo codesign --force --deep --preserve-metadata=identifier,entitlements --sign - /Applications/Xcode.app
- Re-signed DVTSystemPrerequisites.framework individually
- Deleted DerivedData, Xcode caches, preferences
- Fresh reinstall of Xcode (multiple times)
- Tried installing Xcode 16 — same crash
- Raised Apple Support Ticket: 102889658162 — no resolution received
Nothing has worked.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
ROOT CAUSE ANALYSIS
macOS 26.5 introduced stricter platform binary validation in dyld. On Intel Mac (x86_64), this validation is rejecting Xcode's own frameworks at runtime — even after re-signing. This does not appear to be a user-fixable issue.
This seems to be a macOS 26.5 regression specifically affecting Intel Mac users.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
REQUEST
- Is anyone else experiencing this on Intel Mac?
- Has anyone found a working workaround?
- Can Apple Engineering please investigate this as a macOS 26.5 regression for Intel Macs?
My entire development workflow is blocked. Any help is greatly appreciated.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━