Bug 46396 - Unable to boot device in current state: Booted
Summary: Unable to boot device in current state: Booted
Alias: None
Product: iOS
Classification: Xamarin
Component: Tools ()
Version: XI 10.0 (iOS10)
Hardware: Macintosh Mac OS
: --- blocker
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2016-11-03 17:12 UTC by Dan Waters
Modified: 2017-01-17 19:36 UTC (History)
6 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Dan Waters 2016-11-03 17:12:33 UTC

Comment 1 Dan Waters 2016-11-03 17:13:09 UTC
Customer reports the following behavior: 

“Xamarin Studio and iOS Simulator issues: With the first release of Xamarin.iOS we were able to run the app in debug mode only one time, after we need to go to the process of closing the simulator and open it again as the build got stuck on "Waiting for the debugger to connect to the iOS simulator.". After trying to run the app, we got the message: "Unable to boot device in current state: Booted". Sometimes, Xamarin Studio needs to be restarted to make it work, other times it is fixed by only restarting the simulator."
Comment 2 Timothy Risi 2016-11-04 20:59:02 UTC
Hi Dan,

Does the customer have a repro case we can use for this?  I'm able to run an iOS project in the simulator multiple times without issue without having to close the simulator in between.  Environment information would be helpful as well.
Comment 3 Sebastien Pouliot 2016-11-09 19:34:41 UTC
This is not a general problem and not one we can reproduce. From past experience similar issues were fixed by one of the following actions:

1. If this happens for all type of simulators then it's often because there is one (or more) `sim*` process are left in memory. This can cause random connection issues.

   > Reboot computer

2. Another special case is that renaming Xcode.app, after it's first execution, can leave other process looking at the wrong code.

   > Reboot computer

3. If one (or more) types of simulators are affected then it might be because Xcode installation is corrupted. Common causes are: disk issue, 3rd party addins for Xcode (can cause issue with its integrity check)

   > Delete /Application/Xcode.app
   > Re-install Xcode (from download or from the app store)

4. When the simulator works for some apps but not others (or one in specific) it's often because the simulator and/or application *data* is corrupted.

   > From the simulator go to it's Simulator menu;
   > Select Reset Content and Settings...
   > Confirm the Reset (note that all data/apps inside the simulator instance will be deleted)

If all those fails then we'll need more information about the environment, including that Tim asked in comment #2 and the computer logs (from Console.app).
Comment 4 Manuel de la Peña [MSFT] 2016-12-13 12:08:34 UTC
Do we have any feedback from the customer based on @sebastiens comment?
Comment 5 Timothy Risi 2017-01-17 19:36:03 UTC
We have not received the requested information. If the customer is still experiencing this issue please provide all the requested information and re-open the bug report. Thanks!