Bug 42963 - Deployment is done to newly connected device, even if a different target was defined when build started.
Summary: Deployment is done to newly connected device, even if a different target was ...
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android ()
Version: 4.3.0 (C9)
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2016-08-01 19:04 UTC by Flash3001
Modified: 2016-12-23 02:54 UTC (History)
6 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description Flash3001 2016-08-01 19:04:04 UTC
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.
Comment 1 Ben Beckley 2016-08-04 19:57:24 UTC

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 (cycle8/87bdf0c).

I would like to confirm this issue - could you please provide the XVS version you are experiencing this with?
Comment 2 Flash3001 2016-08-05 12:08:12 UTC
Xamarin (fcbe082)
Xamarin.Android (1cf254d)
Comment 3 Flash3001 2016-08-05 13:06:00 UTC
Steps in a video:

Comment 4 Jose Gallardo 2016-12-23 02:54:51 UTC
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.