Bug 14534 - Simulator is restarts every time app is deployed
Summary: Simulator is restarts every time app is deployed
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: 4.1.10
Hardware: PC Mac OS
: --- normal
Target Milestone: master
Assignee: Jeffrey Stedfast
Depends on:
Reported: 2013-09-08 13:47 UTC by Frank A. Krueger
Modified: 2013-09-10 10:05 UTC (History)
5 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 Frank A. Krueger 2013-09-08 13:47:12 UTC
4.1.10 With Xcode5 DP5.

Every time I run an app (debug or release), the current simulator is forcibly shut down and a new one brought up.

This has many negative side effects:

0. SLOW. I have to wait for iOS 7 to boot every time I want to run my app.

1. The simulator never remembers its state so you can't control where it appears on the desktop, nor its orientation.

2. Causes a lot of screen flicker - simulator comes to foreground, is closed, new simulator appears behind XS, then new simulator comes to front.

3. There are bugs, I keep getting multiple simulators running.
Comment 1 Jeffrey Stedfast 2013-09-08 14:27:16 UTC
mtouch needs to cache which simulator type/version it launched the last time and just re-use the running simulator if they match.

There's no way for Xamarin Studio to do this with any level of accuracy (XS doesn't know the pid of the Simulator process so can't even know if the last Simulator launched is even the same one that is running now).

I suggest mtouch create a file with the pid and simulator type that it can check the next time it goes to launch a simulator and check that info to decide if it needs to launch a new one or not.
Comment 2 Frank A. Krueger 2013-09-08 15:54:32 UTC
Sounds reasonable Jeffrey.

Really confused why you guys changed this behavior at all. I know the last system was a little dodgy, but this policy of always restarting the simulator seems like an over reaction.

I'm quite content with you just reverting to old XS behavior.
Comment 7 Mohib Sheth 2013-09-10 01:39:12 UTC
I am facing this same issue. Why has this been marked fixed??
Comment 8 Jeffrey Stedfast 2013-09-10 07:17:54 UTC
I've implemented a workaround in Xamarin Studio to remember the type of device it launched the previous time so that it tells mtouch to launch the generic simulator for that type (iphone / ipad) so that mtouch doesn't kill & restart using the exact device type.

mtouch only kills the running simulator if an exact type was requested.
Comment 9 Mohib Sheth 2013-09-10 08:18:39 UTC
Ok great. Thanks. When's the expected time for this to roll out?
Comment 10 Jeffrey Stedfast 2013-09-10 08:39:56 UTC
I'm not sure, QA needs some time to test a bunch of new features that I just landed for Apple's upcoming Xcode5/iOS7 release, so probably ~a week or so.

A new Alpha may come out before then, with a few cherry-picked patches but I'm not sure.
Comment 11 Mohib Sheth 2013-09-10 10:05:51 UTC
Allrite no worries. Atleast I can expect a bug fix soon :)