Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
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."
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.
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).
Do we have any feedback from the customer based on @sebastiens comment?
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!