Description
Xcode 26.4.1 crashes immediately on launch with a code signature error. The issue exists on macOS 26.4.1 and persists after upgrading to macOS 26.5 (25F5058e) and attempting 26.6 beta.
Crash Details:
- Exception Type: EXC_BAD_ACCESS (SIGKILL (Code Signature Invalid))
- Termination Reason: Namespace CODESIGNING, Code 2, Invalid Page
- Key symbols: dyld3::MachOFile::trieWalk, dyld4::JustInTimeLoader::applyFixups, dyld4::Loader::forEachBindTarget
All Steps Tried (All Failed):
- Fresh reinstall from Mac App Store and .xip from Developer website
- Multiple
sudo xattr -cr+sudo codesign --force --deep --strict --options=runtime --sign - - Deleted all Xcode caches, DerivedData, and preferences
- Tested in a brand new user account (same crash)
- Downgraded Xcode to older versions
- macOS remains on 26.4.1 (issue existed here) and upgraded to 26.5 / attempted 26.6 beta — still same crash
- Refreshed Apple Worldwide Developer Relations certificates
- Multiple restarts
The crash report is identical every time.
System Information
- Model: MacBook Pro (M1 Pro, MacBookPro18,1)
- macOS: 26.5 (25F5058e) — issue started after upgrade from 26.4.1
- Xcode: 26.4.1 (24909.0.3)
- SIP: Enabled
- Developer Mode: Enabled
Additional Notes
- Other applications launch normally.
- This appears to be a system-level compatibility issue introduced in macOS 26.5's stricter code signing validation on mapped files / chained fixups.
Request
- Is there a known workaround?
- Is Apple preparing a fix in a future macOS 26.5 patch or Xcode update?
- What additional information would help?
Thank you!