Fix (Workaround) for Xcode playground stuck in Launching Simulator or Running Pl...
source link: https://www.tuicool.com/articles/hit/vyuMB3n
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Jump to the solution if TL;DR
Ever stuck in ' Launching Simulator ' or ' Running Playground ' when you fire up Playground to write some code? Despite restarting Xcode or even Mac multiple times, the problem still persists? I have seen many beginners give up on learning Swift because of this issue and this really sadden me, Apple should do better on this. Apple recommends beginner to use Playground and yet Playground is full of issues like this ♂️.
I ran into this issue last week while trying out NSPredicate examples in Playground, it happened after an error during execution of code.
After the error appeared, no big deal, I changed the code and run it again, then the Playground got stuck in Running ... :scream:. Then I quit Xcode and open the Playground again, and the same issue persist :sob:.
I tried restarting Xcode, Mac to no avail and almost attempt to reinstall Xcode. Then I noticed it stuck on "Launching Simulator" and thought it might have something to do with the iOS Simulator since restarting Xcode doesn't help .
When you create a Playground in Xcode, it will use iOS platform to run the code by default. To run it on iOS platform, the Playground will spin up an iOS Simulator in the background.
And it is this iOS Simulator thing that causes the stuck issues! Restarting Xcode doesn't work because the simulator process doesn't get restarted when you restart Xcode as it is a separate process.
Somehow the CoreSimulator process become unstable after an error got raised in the Playground. It will get stuck after the error and remain stuck until you kill this process. That's the reason why you keep stuck on "Launching Simulator" or "Running.." even after restarting Xcode.
The solution for this is to switch to macOS platform in the Playground, let the playground code run in your macOS environment directly instead of spinning up an iOS simulator process to run it.
First, ensure your Playground doesn't use any UIKit function (eg: UIView etc), and remove the top
import UIKit line if it is there.
Then in the right pane of the Playground window, select ' macOS ' in Playground Settings -> Platform .
I also suggest switching to manually run instead of automatic run in the playground to reduce the CPU usage.
Now you should be able to run the Playground successfully, cheers! :beers:
The caveat of this solution is that you have to remove
import UIKit and all UIKit related functions as macOS doesn't support UIKit.
No idea on how to start learning iOS Development?Get the Roadmap of learning iOS Development and learn iOS knowledge by hands-on coding of projects.
Workaround Solution if you need to use UIKit
If you are using UIKit functions in Playground, you have to use iOS Platform as UIKit is iOS-exclusive.
The solution for solving the stuck issue then will be to quit Xcode, open ' Activity Monitor ' (In Spotlight, type 'Activity Monitor'), search for ' simulator ' ,highlight com.apple.CoreSimulator , and force quit it.
Then open Xcode again , it should work fine now. If you got any error during code execution in Playground, you will need to repeat these steps. I recommend switching to manually run in Playground so that the Playground won't auto run the incomplete code while you are typing to prevent occurrence of error.
Aggregate valuable and interesting links.
Joyk means Joy of geeK