Post

Replies

Boosts

Views

Activity

xcode 26.4.1 crash
Translated Report (Full Report Below) Process: Xcode [3078] Path: /Applications/Xcode.app/Contents/MacOS/Xcode Identifier: com.apple.dt.Xcode Version: 26.4.1 (24909.0.3) Build Info: IDEApplication-24909000003000000~2 (17E202) Code Type: ARM-64 (Native) Role: Default Parent Process: launchd [1] Coalition: com.apple.dt.Xcode [1424] User ID: 501 Date/Time: 2026-04-24 17:26:21.8348 +0800 Launch Time: 2026-04-24 17:26:21.7161 +0800 Hardware Model: MacBookPro18,1 OS Version: macOS 26.5 (25F5058e) Release Type: User Crash Reporter Key: 7A149229-7AEE-0654-7878-1A66190C590A Incident Identifier: AC932530-5FCF-45B1-90F3-D26B40150344 Time Awake Since Boot: 3400 seconds System Integrity Protection: enabled Triggered by Thread: 0, Dispatch Queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGKILL (Code Signature Invalid)) Exception Subtype: UNKNOWN_0x32 at 0x0000000112948000 Exception Codes: 0x0000000000000032, 0x0000000112948000 Termination Reason: Namespace CODESIGNING, Code 2, Invalid Page
1
0
118
3d
Xcode 26.4.1 Crashes on Launch with Code Signature Invalid on macOS 26.4.1 and All Higher Versions (26.5 / 26.6 beta)
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!
1
0
60
15h
xcode 26.4.1 crash
Translated Report (Full Report Below) Process: Xcode [3078] Path: /Applications/Xcode.app/Contents/MacOS/Xcode Identifier: com.apple.dt.Xcode Version: 26.4.1 (24909.0.3) Build Info: IDEApplication-24909000003000000~2 (17E202) Code Type: ARM-64 (Native) Role: Default Parent Process: launchd [1] Coalition: com.apple.dt.Xcode [1424] User ID: 501 Date/Time: 2026-04-24 17:26:21.8348 +0800 Launch Time: 2026-04-24 17:26:21.7161 +0800 Hardware Model: MacBookPro18,1 OS Version: macOS 26.5 (25F5058e) Release Type: User Crash Reporter Key: 7A149229-7AEE-0654-7878-1A66190C590A Incident Identifier: AC932530-5FCF-45B1-90F3-D26B40150344 Time Awake Since Boot: 3400 seconds System Integrity Protection: enabled Triggered by Thread: 0, Dispatch Queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGKILL (Code Signature Invalid)) Exception Subtype: UNKNOWN_0x32 at 0x0000000112948000 Exception Codes: 0x0000000000000032, 0x0000000112948000 Termination Reason: Namespace CODESIGNING, Code 2, Invalid Page
Replies
1
Boosts
0
Views
118
Activity
3d
Xcode 26.4.1 Crashes on Launch with Code Signature Invalid on macOS 26.4.1 and All Higher Versions (26.5 / 26.6 beta)
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!
Replies
1
Boosts
0
Views
60
Activity
15h