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.
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.
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.
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.
I am facing this same issue. Why has this been marked fixed??
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.
Ok great. Thanks. When's the expected time for this to roll out?
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.
Allrite no worries. Atleast I can expect a bug fix soon :)