IPhone Simulator Cannot Be Launched?

Question

When I click Run on Xcode with other tasks running, the following message appears:

Used simulator. The simulator cannot be started because it is already in use.

I checked with some friends, and when they press the start button, Xcode automatically stops the tasks that are running and launches the desired application. How can I customize this here?

Thanks in advance,

Answer 1

Close the simulator and try again. if it doesn’t work, exit Xcode and try again.

Answer 2

If you have two projects in Xcode and one is running on a simulator , you cannot run the other . Go through each project window and see if they will work, and if they are, click the Stop button in the upper left corner:

Answer 3

In most cases, Josh's answer solves this problem. But just now, only one project in Xcode happened to me and an attempt to clean and build it did nothing. For me (this time), the solution was:

• Right-click the simulator from the dock and click "Exit."
• I did the same for Xcode (right-click on Xcode in the Dock and click "Exit").
• After that, just reopen Xcode and voila!

He works!!!

Answer 4

If the problem is that you have several projects open and running in Simulator conflicts, someone created a small Automator script that closes the current simulator and launches the next one. Kind of work, but may work for you.

See the detailed answer here.

Answer 5

Debugger Syndrome Too Complex

This happens to me when I switch the simulator type (ios version or device type) without pressing the stop button (the application is still running on it). To fix this, go back to the old one (if you remember what it was: P), then start, stop the application, switch to the desired simulator configuration, start, tadaaaa: the error has disappeared.

This can also happen if you have two projects and one is running and you are trying to start the other. The solution is to stop the other before starting the desired one.

This also happens if you have some kind of crazy mistake and the simulator does not respond, in this case the debugger remains attached, crying over your favorite simulator. You need to close the xcode simulator and restart it for this.

I currently have the latest version of xcode, and I got some time. Now I am free from restarting the simulator, xcode, coputer, router, sleep and wake up the next morning ...: D

Hope this helps you, apple guys have a lot of weird exceptions that are not classified in xcode. They could at least say that the debugger is still attached to something in memory, we are programmers, not ordinary users, the more errors you give us, the better we understand how to avoid them.

My personal favorite is si, when xcode sets the absolute paths to your recently added article that goes crazy to find out why it doesn’t work on another computer (project in miracle syndrome).

(and piercing ranting of irony) you get the idea)

Answer 6

Your Mac may automatically open iPhone Simulator. To stop this, you can start Terminal, the OSX command line version, by going to ~/Applications/Terminal.app from there you can run these commands.

• top -u This command shows mac processes and some information about them, from there you can see if iPhone Simulator can be open.
• sudo killall iPhone\ Simulator By deconstructing this command for you, sudo puts you in superuser mode by entering your login password, killall : this command kills all processes by the specified name. iPhone\ Simulator : This is the name of the application, and in order to have a space, \ (space) is required before the second word. Running this command will kill all processes called iPhone Simulator .
• If this does not help, try rebooting.
• If rebooting does not help to reinstall Xcode .
• If reinstalling Xcode does not help, try installing your operating system completely .

Good luck

Answer 7

Close the simulator and try again.

Answer 8

Close xcode and simulator and try restarting mac

Answer 9

There are three solutions to this problem:

• Right-click the sim in Doc, close and re-launch the application from Xcode.

If that didn't work, then -

2. Save your code, right-click Xcode, restart Xcode with your project and run it again. Remember to select a simulator instead of a device in the target.

If this also did not work, then

3. Force Close - Simulator / Xcode - restart your Mac and run Xcode again.

Most likely, the first step would be enough!

Answer 10

To make the simulator stop all that is needed, uncheck the box "Do not show this message again."

Example:

And then click on the box.

And then you can run the simulator, even if the program is already running.

Answer 11

I had this problem too, but for me the problem is not related to Xcode or Simulator.

The problem was in my code. The process started the CPU 100%, and fixing the error in my code fixed the simulator problem.

Answer 12

Force exit and , iOS Simulator and Xcode, then reopen Xcode and start the project.

Answer 13

Two possibilities. 1) just exit the simulator and run the application that you want to run 2) just stop the application using the simulator and run the application that you want to run

Answer 14

Try these steps in order of increasing problem:

• Close the simulator.
• Clean project, Reset Simulator, Delete Derived Data.
• If nothing works, Force Quit Xcode and Simulator from the Mac menu.

Force Quitting Xcode seems to always work for me.

This was one sticky Xcode bug. Now he decided a happy encoding!