My development work is paused as Xcode is now non-functional on my Macs. Loading any project into Xcode soon leads to a hang and Force Quit. The SDKs are listed as "status unavailable". No Simulators are available.
I've tried previous versions of Xcode; removing everything and re-installing; installation from the Store and direct from the Apple Developer site.
I've created a Feedback issue.
This happens on both of my Mac minis.
I'm running Tahoe 26.4 (25E246) on both.
I've created a Feedback issue.
What's the FB number? If there isn't a sysdiagnose attached, please make sure to update your report with one so we have details on what's happening.
I filed a similar report yesterday...
Xcode 26.4 (17E192) Simulators Keep Showing As Unavailable After Successfully Intalling Them
FB22346008
... with sysdiagnose tarball and screen shots. Am also running Tahoe 26.4.
I spent the better part of this evening removing the following items:
/Applications/Xcode.app
/Library/Developer
~/Library/Developer
~/Caches/com.apple.dt.*
~/Preferences/com.apple.dt.*
/private/var/tmp/com.apple.CoreSimulator.SimDevice.*
rebooting my machine, and then reinstalling Xcode 26.4 (Apple Silicon) and the command line tools. I then used xcrun simctl to flush all of my devices and runtimes. I spent a lot of time fighting Xcode because after removing old simulators, Xcode automatically downloads them all again (SMH!). Once Xcode seemed to stabilize its downloads (using xcrun simctl list to monitor everything), I then added the iOS, watchOS, and tvOS simulators for 26.4. So far, things "seem" to be behaving. We'll see whether or not I wake up tomorrow to joy or despair.
I have a 2021 MacBook Pro (M1 Max) and have developed solidly on it ever since I got it. This is the first version of Xcode that has trainwrecked my world since the horrible days of Xcode 6. Ugh!
And today Xcode's simulators are all unavailable again!
I woke up my machine after it went to sleep overnight, and Xcode seemed happy and showed all the simulators. So then I decided to reboot the machine just to make sure, and now Xcode is showing everything as "Status unavailable" again, and all of the previously downloaded runtimes are gone. And xcrun simctl list just hangs, requiring a Ctrl-C to kill it.
To anyone from Apple who is listening ... stop cramming AI slop features into everything and focus on fixing the bugs! This is unacceptable.
I'm now wondering if this is a macOS 26.4 issue. I clean everything out again, reinstalled Xcode Xcode 26.3 (17C529), did the simulator updates (and waited for Xcode to stabilize its other downloads), rebooted, and all the simulators it had installed were in "status unavailable" state again.
How could anybody at Apple not have encountered this, and why was it released to the public?
Last post ... I promise ...
When I reinstalled Xcode 26.4 again after going through all of the above shenanigans, I chose to NOT install the 26.x line of simulators, nor the Predictive Code Completion Model. As before, Xcode downloaded and installed older simulators anyway, but left the 26.x options uninstalled with their "Get" buttons primed and ready. I closed down Xcode and did some other stuff. After an hour I launched Xcode to check on things, opened Settings and, lo and behold, the iOS 26.4 and watchOS 26.4 simulators were showing as installed under the Platform Support section of the Components.
What is going on? It's as if Xcode is hallucinating.
xcrun simctl list just hangs for me.
I found my Intel based Mac Pro still works with the same set-up. One of my Apple Silicon Mac minis sort of works, one does not no matter what I try.
Yes, when it's in the "bad" mode, xcrun simctl list will hang forever.
That's interesting that it still works on your Intel machine. I've been holding off upgrading my older Intel MBP to the 26.4 updates for fear that it would wreck that environment too.