Xcode 27 No iOS 27 Simulators

Huge mess still going on. I uninstalled Xcode 27.0 and installed Xcode 27.1 beta instead. Upon initial launch, it downloaded bother the 27.1 and 27.0 runtimes. But alas, same issue in Device Hub. Cannot add any simulators even after a reboot.

When I list contents of com_apple_MobileAsset_iOSSimulatorRuntime, it now shows 4 folders. Two for iOS 27.0 and two for iOS 27.1 whith one having a status of "Ready" and the other Unusable - Cryptex Mount Preferred".

xcrun simctl runtime verify of the iOS 27.0 "Ready" one gives an error: "-67054 a sealed resource is is missing or invalid". And a verify of of the iOS 27.0 "Unusable" is the same error message with a code though of -67068.

Anyone know why this is happening?

I'm now going to uninstall Xcode 27.1 beta and try out Xcode 27.2 beta 2 in hopes that some version will work.

Ok, before uninstalling Xcode 27.1 beta 1, tried one more time.

Launched Xcode, and in Settings | Components, clicked on info icon next to the iOS 27.1 beta item under Platform Support and removed it. It's status then showed a red "Cryptex" message and button along the right-hand side became "Update".

After clicking on Update, it still shows the error. Brining up info shows "There was a problem identified with the iOS 27.1 beta platform that was downloaded. Redownload iOS 27.1 beta and try again".

Clicked on "Delete..." via the info dialog, but noticed the same error along with "Update", so tried "Delete..." a second time and that cleared the error and gave me the "Get" button again.

Clicked on "Get" which showed it downloading 2 items again (27.1 and 27.0 simulators).

Back to Terminal, and now when I list the contents of com_apple_MobileAsset_iOSSimulatorRuntime, it shows only two entries, both ready. One for 27.0 and the other for 27.1. Great! However, xcrun simctl list runtimes shows nothing.

I'm going to reboot now and see if that changes anything. If not, I'll attempt to use xcrun simctl runtime add.

No luck. Even Xcode 27.2 beta 2. Restarted multiple times, purged that iOSSimulatorRuntime folder.

Re-downloaded the various runtimes to include iOS 26.0 and 26.5. No matter what I try, I cannot get anything to work.

I'm really regretting updating to macOS 27.0 since I'm now forced to use Xcode 27.x

I cannot explain, but I can now run iOS 26.0 simulators in Xcode 27.2 beta.

Prior to my last reboot, "xcrun simctl list runtimes" was empty. and "xcrun simctl runtime list" showed two entries:

• iOS 27.0 (24A434) - <uuid> (Ready)
• iOS 27.2 (24B5089g) - <uuid> (Ready)

After reboot, the lattter command then showed three entries (same two as above) with a third "unknown" entry. Then a few moments later, the same command showed five!

• iOS 27.2 (24B4089g) - <uuid> (Unusable Cryptex)
• iOS 27.0 (24A434) - <uuid> (Ready)
• iOS 27.0 (24A434) - <uuid> (Unusable Cryptex)
• iOS 27.2 (24B4089g) - <uuid> (Ready)
• iOS 26.0 (23A343) - <uuid> (Ready)

Where did that iOS 26.0 entry come from? I hadn't downloaed it.

However, "xcrun simctl list runtimes" is now showing:

• iOS 26.0 (26.0 - 23A343) ...

Is this because around 30 minutes ago, I had downloaded that runtime? And even though I since deleted it, it decided to come back somehow?

In summary, I can once again create simulators, though just 26.0 which is a-ok for now.

I'll try to file a bug later.

Fix this first

1. Remove the simulator's arm64 exclusion

• Select your project → app target → Build Settings.
• Search for Excluded Architectures.
• Check both Debug and Release configurations.
• If Any iOS Simulator SDK has arm64, remove that value or set it to empty.

1. Check Architectures

Search for Architectures and select Standard Architectures ($(ARCHS_STANDARD)). Also check any .xcconfig files and CocoaPods post_install scripts for settings that exclude arm64.

Fix this first

1. Remove the simulator's arm64 exclusion

• Select your project → app target → Build Settings.
• Search for Excluded Architectures.
• Check both Debug and Release configurations.
• If Any iOS Simulator SDK has arm64, remove that value or set it to empty.

1. Check Architectures

Search for Architectures and select Standard Architectures ($(ARCHS_STANDARD)). Also check any .xcconfig files and CocoaPods post_install scripts for settings that exclude arm64.

Thanks for the ideas, but all my projects didn't have any Excluded Architectures. And, all our using Standard Architectures.

I'm still running into this issue on macOS 27.0.1 with Xcode 27.2 RC (also with 27.1 and 27 Xcode versions): Device Hub keeps saying no runtime available even though I have 3 runtimes installed right now! See attached screenshots.

I'm also having this issue on my M1 iMac, but my M5 MB Air works fine.

I found a fix, for me at least. Run this command to see the level of boot security on your mac:

 system_profiler SPiBridgeDataType | grep -i 'Secure Boot'

If it says anything other than Full Security then you need to re-enable Full Security. Mine said Reduced Security.

I changed it following this procedure:

1. Shut down your mac completely.
2. Press and hold the power button until you see Loading startup options.
3. Select Options → Continue.
4. Authenticate with an administrator account if prompted.
5. From the menu bar, select Utilities → Startup Security Utility.
6. Select your Macintosh HD and click Security Policy.

It seems Reduced Security configuration was interfering with Apple’s cryptex personalisation process.

That seemed to be a one off fix as the problem came back and my 27.2 sims disappeared again. However I think I have found the fix now.

Apples cryptex directory has the permissions

drwx---r-x root daemon

If your account belongs to daemon, macOS denies it access to the directory.

View your user account groups with the command:

id

or check if your user account belongs to daemon with this command:

dscl . -read /Groups/daemon GroupMembership

If you see your account, remove it from the daemon group with:

sudo dseditgroup -o edit -d <your_username> -t user daemon

Then reboot.

@dazboj Man! Thanks! It solved the issue on my side.

To fix it:

1. I removed the group
2. Deleted old SDK using xcrun simctl runtime list + xcrun simctl runtime delete <id>
3. Rebooted system
4. Installed the new SDK via Xcode

The reboot step was crucial. This is the same problem as in my thread: https://developer.apple.com/forums/thread/853154

Also, I think it's worth mentioning what is the impact of deleting daemon group. Based on AI:

The daemon group (GID 1) is a system group used by background processes (daemons). A regular user normally shouldn’t be a member. If your account ended up there, it could be because of:

• a manual change (e.g. following a tutorial or running a script),
• software that modified group memberships during installation,
• an attempt to work around file permission problems.

After removal, your account loses the access that membership provided, namely access to files and directories whose group is set to daemon with group permissions enabled. This restores the standard, more secure state.

Is it safe?

Usually yes, if your account isn’t supposed to be in that group. Still:

The command requires sudo, so make sure you understand where it came from.
Replace <your_username> with your actual username (you can check it with whoami).
Logging out and back in is usually needed for the change to fully take effect.

@dazboj Thank you so much! The issue you outlined is what was causing me grief on my Mac. I now have 27.0, 27.1 and 27.2 simulators.

I specifically followed the steps that @maxik outlined (first following your steps to remove the group), then the addtional steps to remove, reboot and re-install the SDKs.

Also, I recently started at a new company and didn't have any of these issues on the company Mac. Checking group membership there just showed "root". Further proof that this was something different about how my personal Mac was configured.