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 for Bug 35729 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Created attachment 13755 [details]
Steps to Reproduce
1. Open XAP Device Manager.
2. Select 'play\ button for required device.
Selected VM should launch.
VM does not launch.
Using Active Directory
Taking a look at the logs, it appears an exception is being thrown when trying to get the path to the running instance of adb. It's possible this is due to the process being owned by another user, and as the current user you don't have rights to access the process.
We have a fix in review for this at the moment. You may be able to get past this if there are no existing "adb" processes running at the time you launch a Xamarin Android Player device.