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 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.
Steps to reproduce:
1 - Select an Android target device - I used an emulator.
2 - Press 'Start Debugging'
3 - Build starts and the target device selector gets gray.
4 - Connect a physical device to an USB port.
5 - The grayed target device selector changes to the newly connected device.
6 - Application gets deployed to the newly connected device.
I was able to reproduce some of this bug up to the last step. The target device selector did change to the newly connected device, but I the application did not deploy to the device. I have attempted this using Android Emulator for Visual Studio and an AVD emulator.
This was using XVS 188.8.131.521 (cycle8/87bdf0c).
I would like to confirm this issue - could you please provide the XVS version you are experiencing this with?
Xamarin 184.108.40.206 (fcbe082)
Xamarin.Android 220.127.116.11 (1cf254d)
Steps in a video:
As we've added several improvements to our build system and deploying/debugging mechanism since the bug was reported, I'm resolving it tentatively as Fixed.
That said, if you're still facing this issue with current bits, please feel free to reopen the bug.