Success! Xcode 26.5 Release Candidate (17F42) running on macOS Tahoe 26.5 Release Candidate (25F71) appears to have fixed the problem for me. I first updated to macOS 26.5 RC, and then to Xcode 26.5 RC. I didn't need to clean out my previous installation data (e.g., /Library/Developer, etc.) ... I just deleted my 26.4.1 Xcode and replaced it with the new. My simulators showed up as expected. I did several reboots of my computer, and each time, the simulators briefly show as "status unavailable" but then they eventually show up and stay there. Hopefully, others have the same the same success.

FWIW, my Intel MacBook Pro is still at macOS 26.3 and Xcode 26.3, and everything is running correctly with regard to the simulators always being available.

I'm wondering if this is actually as much of a macOS 26.4.x issue as well as an Xcode issue. I've tried Xcode 26.4, Xcode 26.4.1, Xcode 26.5 beta 3, cleaning out my installation and data directories each time as suggested in the above posts, and still no joy. Sometimes the simulators go "status unavailable" after a few hours, other times it happens after a reboot of the computer. I've even gone back to installing Xcode 26.3, but a reboot still causes the problem. I'm leery about installing the beta of macOS 26.5 because this is my production machine. Apple informed me they are aware of this bug, but nothing seems to fix it for me. Has anyone had luck with the macOS 26.5 beta along with the Xcode 26.5 beta regarding this bug? How are people getting their work done with this?

@diniska , does your remedy survive a reboot of the machine? When I tried my cleaning (I did the whole CoreSimulator directory, but now I see that I probably only needed to do the images.plist file), my simulators downloaded fine, but then they disappeared again after I rebooted my machine.

File a bug report. I think Apple's bug algorithms won't flag anything unless there are multiple reports on the same bug. Although their Music app still can't properly handle gapless song lists reliably (e.g., Pink Floyd) and yet multiple people have been yelling about this over the years, so I may be off base as to how they prioritize their work. I don't think they have anyone to put the fear of God into them any more like Steve Jobs did when the engineers generated bad code.

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.

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.

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?

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 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!

Correction: Using \mid does export correctly to PDF. But | and \vert do not.

Just verified that this still happens on iOS 17 RC.

I've also encountered the problem with newly generated AAC files that are of iTunes Plus (256 kbps) quality. They play correctly on my MacBook Pro (Ventura 13.5.2) Music app. They do not play correctly on my iPhone 14 Pro Max (iOS 16.6.1) Music app; they exibit the gap between the songs. However, putting the device into Airplane mode allows the music to play without gaps. So I believe it's a threading priority issue where Apple is communicating back to its servers while I'm playing MY OWN music, and they interrupt the playback to send data. So, first and foremost, they're degrading the user experience in favor of what I suspect to be data mining. Secondly ... it appears they're data mining! I really hope I'm wrong about this, and I wish someone at Apple would at least fess up to the issue. I'm really tempted to start sniffing the Wi-Fi traffic from my phone during playback to see what they're doing. Very aggravating!

I'm having the same problem. Can't use the Safari inspector because it's broken [again], and can't download the tech preview because it's "coming soon." But why can't Apple post the existing build until they actually get the "coming soon" build posted? So aggravating!