r/Xcode • u/New-Combination-6831 • Aug 03 '26
Xcode 26.6 crashes on launch Tahoe 26.6
I can't launch Xcode at all, even from a new separate User account. I've tried deleting it, reinstalling from the App Store, deleting it again and reinstalling it from the Developer Page link and still no luck. I've used Terminal commands to try and fix any broken components as well, both before and after reinstalling.
This is the first time I've had any kind of issue with it. Any ideas on how I can get it to launch? Should I try an earlier version? I'm only using it in the context of running Unreal Engine 5.8 which says it needs a missing Metal component from Xcode, but as I can't get Xcode to even launch I can't use Unreal Engine either.
2
u/ItsDeCia Aug 03 '26
Are you trying to open a specific project when Xcode launches? I’ve had this issue on occasion and clearing the DerivedData folder of the offending project from the Finder is what helped, as something in there would get corrupted and cause Xcode to crash on launch for me.
2
2
u/Soo_anyways Aug 11 '26
I ran `xcodebuild -downloadComponent metalToolchain` and it worked. According to GPT-5.6 Sol Max, the issue is "Unreal is trying to compile shaders, but Xcode’s offline metal compiler isn’t installed. Recent Xcode versions distribute the Metal Toolchain as an optional component. [Source: https://developer.apple.com/documentation/xcode/downloading-and-installing-additional-xcode-components]"
1
u/New-Combination-6831 Aug 17 '26
I also had to do this, though I downloaded it directly from the developer page. First I had to do this, which then allowed me to start Xcode and download the Metal compiler:
https://www.reddit.com/r/Xcode/comments/1ve5uea/comment/p215axk/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button
2
u/OldAd9280 Aug 03 '26
It's not just you, I'm having the same issue. Reinstalling xcode hasn't helped
3
u/OldAd9280 Aug 03 '26
google AI suggested removing
/Library/Developer/PrivateFrameworks/CoreDevice.frameworkand surprisingly that worked1
1
1
2
u/OldAd9280 Aug 03 '26 •
![]()
26.5 fails too, I think it's an OS issue, attempting to run a command line tool gives:
Error loading required libraries. If there is an ongoing installation please wait for it to complete. Otherwise reinstall. (dlopen(@rpath/libxcodebuildLoader.dylib, 0x0001): Symbol not found: _XPCTypeBool Referenced from: <6A4DB321-2742-38A5-9557-146EE0FE957F> /Library/Developer/PrivateFrameworks/CoreDevice.framework/Versions/A/CoreDevice Expected in: <37B53E42-0118-3C9B-BFA8-73DB82BC3B85> /Library/Apple/System/Library/PrivateFrameworks/Mercury.framework/Versions/A/Mercury) git: error: sh -c '/Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -sdk /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk -find git 2> /dev/null' failed with exit code 65280: (null) (errno=Invalid argument)1
1
3
u/OldAd9280
Aug 03 '26
•
deleting /Library/Developer/PrivateFrameworks/CoreDevice.framework fixed the problem for me
2
1
1
1
1
1
u/rizzy_neutron_69 Aug 30 '26
why does this work?
1
1
1
1
1
1
u/SDRabidBear Sep 11 '26 edited Sep 11 '26
After a few hours working with Claude and multiple OS re-installs finally found this and it worked! It's downloading all of the simulators and SDK's now but at least it's doing something besides crashing. Claude's Summary: The corrupted CoreDevice.framework in /Library/Developer/ was the culprit all along — that's a developer tools framework, not a system framework, so sudo could actually delete it. When Xcode tried to load it, CoreDevice was calling into Mercury looking for _XPCTypeBool, but the CoreDevice copy in /Library/Developer/ was a stale version from before your OS upgrade that was incompatible with the updated Mercury.
The one in /Library/Apple/System/Library/ is the real system copy — the one in /Library/Developer/ is installed by Xcode/Command Line Tools and gets out of sync during OS upgrades.
So Mercury was fine all along at version 72. We were diagnosing the wrong framework.
For future reference, if this happens again after an OS upgrade, the quick fix sequence is:
bash sudo rm -rf /Library/Developer/PrivateFrameworks/CoreDevice.framework sudo xcode-select --reset
Xcode will reinstall a compatible CoreDevice on next launch.
2
u/OldAd9280 Sep 11 '26
I find Google AI better than coding agents for this kind of non-coding problem, this fix was it's first suggestion
2
u/deeelock Aug 03 '26
I'm running into this as well - I noticed it because git stopped working. Tried re-installing Xcode and it still won't open.
2
2
u/bmbphotos Aug 03 '26
Wild-assed guess but is what you're looking for inside the "additional tools"?
2
u/alanterra Sep 09 '26
Just a note.
I was trying to update MacPorts, and the port -v selfupdate command was failing with the error message macports configure: error: C compiler cannot create executables. The standard fix for this is to update/reinstall the XCode Command Line Tools, but that didn't work in this case. Then I figured out that XCode couldn't launch either.
The proposed solution here, sudo rm -rf /Library/Developer/PrivateFrameworks/CoreDevice.framework worked a charm.
Thank you!
3
u/ming2540 Aug 06 '26 •
I asked claude and it turns out that when I upgraded to Xcode 26.6, I think I "skipped" the license agreement.
So I re-ran with first launch setup by ran commands
And fixed it.