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.
I have three droid devices connected to my USB hub. When I click on the build and deploy icon, the option as to which device I build and deploy to is shown.
I select the device I want (not the one at the top of the options). The app builds and runs on that device.
Subsequent builds though do not go to that device, but to the device displayed at the top of the Run->Run With list. To build for the target I want, I have to go to the Run->Run With menu option
Which device is shown checked in the "android device target" list?
Whatever is at the top, irrespective of what had been selected previously. If you alter from the menu and build, on the next build it reverts to whatever is at the top.
I cannot reproduce this from your description. Could you screencast it?
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?
If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.
Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.