@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.

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

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) - (Ready) iOS 27.2 (24B5089g) - (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) - (Unusable Cryptex) iOS 27.0 (24A434) - (Ready) iOS 27.0 (24A434) - (Unusable Cryptex) iOS 27.2 (24B4089g) - (Ready) iOS 26.0 (23A343) - (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.

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

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.

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.

I don't see the iPhone Duo Simulator at all. Fresh install of Xcode 27.1 beta (27A9269), verified I have Device Hub 27.1. Also clicked Update in Xcode's Settings (Components) to get iOS 27.1 beta. Restarted both applications. Also, deleted iOS 27.1 beta in Components, then clicked on "Get". When manually adding a device in Device Hub, the newest devices are only the iPhone 17 family.

I'm now lamenting ever supporting the iPad. It seems that device is just not playing nice. In SwiftUI you're supposed to be able to use .windowResizability(.contentSize). On macOS, I use that along with modifying my main view with .frame(idealWidth: 1024, idealHeight: 768) and this forces the window to have a content area of that size. tvOS is a non-issue since you're always dealing with 1920 pt x 1080 pt screens. iPhone also a non-issue at least for my games. But with iPad and iOS 26, even if attempting something similar as for macOS, you really don't have ultimate control. I was able to at least set a min of 360 and max of around 500 for the iPad window. But attempting say 720 x 720 will fail since a user and/or system can resize the window. And even when using Canvas, content will now be offscreen. Example (see attached). The actual window height is around 560 pt. So querying the size parameter to Canvas seems to be useless if wanted to use to drive how big to render things. Apple made a huge mistake in not allowing full screen apps on iPad for iOS 26.

swiftlang/swift issue: https://github.com/swiftlang/swift/issues/83610 Swift Forum: https://forums.swift.org/t/insight-needed-for-equatable-with-default-mainactor-isolation/81675

Agreed that moving away from awakeFromNib would be best here. Thank you both!

Bug also exists in Xcode 14.1 Beta

Interesting. Apple's system here is auto-generating a hyperlink for the Feedback identifier. Yet it is excluding the last digit in the link. Guess I'll file another bug. Putting the identifier in quotes was an experiement to see if the link would get fixed.

Also filed: "FB11508814" with attached minimal sample project.

This happens in a brand new project. I created a basic iOS app. In the storyboard, added a navigation bar controller, set that as the initial view controller, and set its root to the original view controller. Log is spammed once with that warning. Seems Apple needs to clean something up; especially if newly created projects will exhibit the same issue.

Calling makeKeyAndVisible does nothing in my apps to silence this. There must be another reason for it. Could it be apps where the interface files were created a long time ago?