Invalid device status - Xcode / iOS simulator error

Problem: I cannot simulate the interface of an Apple watch. Whenever I try to test the Apple Watch application on the iPhone 6 simulator, Xcode successfully terminates and creates the application, tries to open the simulator and crashes with an error message that says โ€œDevice status is incorrectโ€.

Screenshot added

I believe that the simulator has a clock simulator that opens with compatible iPhone models for simulators that can communicate with Apple watches (for example: iPhone 6). Although I have not seen it work. I built a universal interface for the iPad and iPhone, and the other for the watch, so this is not an application issue for the wrong device. Whenever I test my real iPhone, I can successfully test the universal interface.

I am using Xcode 6.2 for iMac OS X 10.10.3

I tried restarting Xcode / Computer. It seems that I can not find any other mention of the status "Invalid device" anywhere, I hope, due to the fact that this is an obvious thing to avoid / fix that I missed. Any help would be appreciated.

+54
ios xcode ios-simulator apple-watch
Apr 6 '15 at 21:48
source share
11 answers

Force Quit xCode and reboot will fix the problem.

+39
Apr 01 '16 at 9:25
source share

I ran into this problem after upgrading Xcode 6.4 to 7.1. The following are the fixes for this:

  • Clear the project (cmd + shift + k), as well as the clean build folder (CMD + Shift + K + option)

Screenshot for clean

  1. Exit the simulator and run again.
  2. Close Xcode and Simulator and run again
  3. Reboot the Mac .

Solution 3 worked for me!

+26
Jan 21 '16 at 7:09
source share

I had the same problem. This is usually because you are simply updating Xcode or changing your name in the Applications folder.

If you just restart your computer, it will work correctly.

Hope this helps!

+16
Apr 27 '15 at 12:19
source share

I noticed that this happens when more than one Xcode application is installed.

To fix this,

  • Launch Xcode and click the preference button ..,
  • Click the Location tab, select the correct options from the Command Prompt drop-down menu.
  • Close Xcode and restart it.
  • Launch the app.
+11
Aug 17 '16 at 10:56 on
source share

First of all, just clean the project.

  1. Exit your project .
  2. Exit your Xcode .
  3. Restart Xcode .

This happens to me when two different versions of Xcode work for me at the same time. Hope this helps you.

+8
Sep 30 '16 at 5:31
source share

No need to stop, restart, or even reinstall. Switch to another iOS Simulator device (6s if you used 6s plus) and voila!

+4
Jul 29 '16 at 22:11
source share

Nothing worked for me on Xcode 7.3.1.

You will have to reinstall it to make the simulator work.

  • Go to the application folder. Drag Xcode to Dustbin.
  • The contents of an empty trash can.
  • Go to the App Store and install Xcode.
  • Launch Xcode. Now the simulator should work.
+1
Jun 13 '16 at 7:45
source share

I have Xcode 7.3 and Xcode 8.0 installed.

If I work with Xcode7.3 and open Xcode8.0 to get the code from the Xcode8.0 project.

When I run my application on Xcode7.3, it will give me the same error.

The solution is a simple ForceQuit or closes all Xcode and opens the required file.

+1
Dec 30 '16 at 7:27
source share

In my case, the simulator will show an undefined black screen, whether to try to start the project or run the simulator directly (which should lead you to a simulated initial screen). This will happen even on a newly created simulated device.

After the existing sentences didn't work, the following worked for me:

  • Delete simulator
  • Remove Xcode
  • Delete Developer Folder
  • Reinstall Xcode from the app store. This requires a second attempt to start Xcode so that Mac OS realizes that it is no longer installed.
0
May 24 '16 at 17:20
source share

Jus will clear the project and restart Xcode. This happens to me when I have two versions of xcode working with different versions at the same time.

0
Sep 21 '16 at 9:25
source share

Reliable fix Just close your xcode and run it again, hope this helps you. That damn works for me.

0
Jun 02 '17 at 3:50
source share



All Articles