If this issue is due to Apple no longer supporting Intel-based Macs, I'd be really pissed!

@MarcoDesmoM1200 I installed Xcode 15.1 beta 3 and ran my code in an iPhone 15 Pro simulator running iOS 17.2 beta 3. The first time it ran, it also took a long time, around 30 minutes. I made a trivial change to a string in the code, and hit Cmd-R. It took just around 1.5 minutes to update the simulator. Did a couple more trivial string changes. Still good. I then added a bit more code: foregroundStyle, fontWeight. This time, it again took 30+ minutes. Still spinning as we speak... This sucks!

@nicolas291 I just updated to Xcode 15.1 (15C65). Running a simple app from HackingWithSwift in the iPhone 15 Pro Simulator takes forever to display the app. I'd day at least 30 minutes. Then just simply changing the value of a string in the code and hitting Cmd-R to rerun the app in the simulator takes another 30 minutes. This is totally unusable! If it matters, my Mac is: Retina 5K, 27-inch, 2017, 3.4 GHz Quad-Core Intel Core i5, running Ventura 13.6.1 (22G313).

@pashlya I am running Xcode Version 15.1 (15C65). There is no /Applications/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Library/Developer/CoreSimulator/Profiles/Runtimes. Under ..../Profiles are folders: Chrome and DeviceTypes

OK, good to know. But the fact that there was an error during "Verifying iOS 17.2 simruntime" and yet iOS 17.2 appears in the Platforms list is a bit puzzling. Yes, I can run the code in the iPhone 15 Pro simulator. Let's see if it runs in the Preview window. I have not succeeded in seeing the app display in the Previews canvas ever since I upgraded to Xcode 15.

I am having the same issue when installing iOS 17.2 simruntime. Waiting it out ended with "iOS 17.2 Simulator (21C62) Failed — CoreSiimulator failed to respond." Any suggestions?

That works, but it is still not possible to insert a color literal as an argument in a function. Example: setGradientBackground(topColor: QQQ, bottomColor: YYY) You can't put a color literal in place of QQQ and YYY. It forces it to: setGradientBackground(topColor: colorLiteral(red: 0.4745098054, green: 0.8392156959, blue: 0.9764705896, alpha: 1), bottomColor: colorLiteral(red: 0.5546397567, green: 0.3071874082, blue: 0.007406672928, alpha: 1))

If they have fixed it, why isn't it available as an update via the usual Software Update in System Preferences?

@h725 How were you even able to create test containerS (plural) since you can't have more than one for a particular bundleID (com.yourCompanyName), and you can't rename or delete it? How was it possible to have more than one container?

@BrianA You posted that answer 6 years ago, and today in 2021, the iCloud container STILL cannot be renamed or deleted. I am stuck with a container name from a tutorial at https://www.hackingwithswift.com/read/33/overview called Project-33. So my iCloud container is cursed with that name forever. UGH!!!

@ajisaputrars I just updated to Big Sur 11.5.2 and Xcode 12.5.1 last night. The slowness issue remains unfixed.

@tramsdell Your post was 3 months ago. I just updated to Big Sur 11.5.2 and Xcode 12.5.1 and the problem remains the same! :-(

I skipped Big Sur 11.3 or 11.4 and updated directly to 11.5.2 last night. I then updated my Xcode to 12.5.1. The simulator (I chose iPhone 11) for an existing small project then took more than 10 minutes (!!!) to launch and run! (I have a 2017 iMac 27".) When will Apple fix this?!

@ajisaputrars I just updated to Big Sur 11.5.2. Problem remains the same.

@edford Can you answer my other question: [https://developer.apple.com/forums/thread/688469)