Unable to determine simulator boot device. - Xcode

I just downloaded Xcode 6 and played a little with it.

After upgrading to a previous version of Xcode and running in the simulator, I continue to get this error.

Unable to determine simulator boot device.

How do we resolve this?

Thanks in advance.

+63
ios xcode ios8 xcode6
Jun 03 '14 at 9:47
source share
8 answers

Make sure that there is only one instance of iOS Simulator in the dock.

+168
Jun 03 '14 at 11:00
source share

For me there was a simple answer:

  • Open the simulator using Xcode -> Open Developer Tool -> iOS simulator (even if it cannot be started, the application will open).
  • Having opened the simulator application, open "Hardware โ†’ Device โ†’" Device Management ".
  • Add the missing simulators with the plus button (for some reason Iโ€™ve been missing).
+54
Jun 17 '14 at 3:39 on
source share

I ran into the same problem and decided to follow these steps:

1) Move xcode6-beta to the application folder

2) Restart mac and open xcode6-beta from the application folder.

+2
Jun 05 '14 at 7:15
source share

I had the same issue when starting with Xcode 6 beta by selecting iPhone 5s. If I choose iPhone 5 or โ€œresizable iPhoneโ€, then my application will start perfectly.

+1
Jun 04 '14 at 3:55
source share

You will not see the simulator profiles without rebooting OS X. I added the simulator many times when the reboot is over, it is displayed in the list of devices under the simulator panel. I think this is an Xcode 6 Beta bug p>

+1
Jun 08 '14 at 11:51 on
source share

I think you have 2 simulators working in the dock. Close another simulator and run the project again. This may be helpful for you.

+1
Nov 14 '14 at 3:52
source share

In my case, I had such a message only because the simulated device was still loading (longer than usual, I think). Xcode 7.2. (Actually, this is not the answer to this specific question, but I came here by clicking on the link in the title, so I write my note here if someone else gets the same case as me)

0
Feb 23 '16 at 10:50
source share

I just fixed the same problem by uninstalling the beta and restarting the computer.

-2
Jun 03 '14 at 12:34
source share



All Articles