I hit the exact same crash on an M2 MacBook Pro running macOS 26.6.2 (25G83), Xcode 26.6 (24959). Reinstalling Xcode multiple times (both via App Store and direct .xip download from developer.apple.com) did not help — same crash every time, immediately on launch, before any window even appears. Running the binary directly from Terminal revealed the actual error (the GUI just shows "Xcode quit unexpectedly"): /Applications/Xcode.app/Contents/MacOS/Xcode Error loading required libraries. If there is an ongoing installation please wait for it to complete. Otherwise reinstall. (dlopen(@rpath/Frameworks/libIDEApplicationLoader.dylib, 0x0001): Symbol not found: _XPCTypeBool Referenced from: <...> /Library/Developer/PrivateFrameworks/CoreDevice.framework/Versions/A/CoreDevice Expected in: <...> /Library/Apple/System/Library/PrivateFrameworks/Mercury.framework/Versions/A/Mercury) zsh: abort /Applications/Xcode.app/Contents/MacOS/Xcode Root cause: /Library/Developer/PrivateFrameworks/CoreDevice.framework on my system was dated November 2024 — a stale leftover from a much older Xcode/CLT install. It was never touched by any of the normal cleanup steps (deleting Xcode.app, clearing ~/Library/Developer, pkgutil --forget, reinstalling Command Line Tools via xcode-select --install), because those all operate on ~/Library/Developer (user-level) or the app bundle itself — not on the system-level /Library/Developer/PrivateFrameworks directory. That old CoreDevice framework expects a symbol (_XPCTypeBool) from Mercury.framework that doesn't exist in the current macOS 26.6.2 build, so Xcode aborts on launch before it can even draw a window. Fix: sudo rm -rf /Library/Developer/PrivateFrameworks This directory gets correctly repopulated the next time Xcode launches / CLT reinstalls. After deleting it, Xcode launched immediately without any further issues. If you're seeing this exact crash (_XPCTypeBool symbol not found, CoreDevice vs Mercury), it's worth checking the date on /Library/Developer/PrivateFrameworks/CoreDevice.framework — if it predates your current Xcode version, this is almost certainly your fix. No need to fully wipe/reinstall Xcode or CLT.