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.
Currently using XAP v0.3.7(1), and in previous versions, I was able to run multiple instances of different device images at the same time. Now when I try to start another device, while another was running, I get a message box saying "Cannot Launch [DeviceName]. Please close the Xamarin Android Device that is currently running before launching [DeviceName]."
This limit kills my productivity because I was able to easily deploy to different XAP devices quickly. For example, I would have a JellyBean, KitKat, and Lollipop device all running at the same time. I would deploy to each using Xamarin Studio, and test out relatively quickly. Now I have to close and launch each individual device one at a time, and this is not good for productivity. I was able to do this in past versions, so I'm not sure why this was changed.
I would love for the ability to launch multiple device to be included back into XAP.
This isn't something that was removed, XAP has never supported multiple simultaneous devices.
I'm going to change this from a bug report to a feature request.
Closed as a feature request.
Error in closure.