Bug 56655 - Debugging on a new device doesnt deploy
Summary: Debugging on a new device doesnt deploy
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: 7.3 (15.2)
Hardware: PC Mac OS
: High major
Target Milestone: 15.4
Assignee: dean.ellis
Depends on:
Reported: 2017-05-19 05:26 UTC by James Clancey
Modified: 2017-07-21 11:56 UTC (History)
8 users (show)

Tags: NotFixedIn15.3
Is this bug a regression?: ---
Last known good build:

Attached are the logs generated when observed that issue is fixed in Master build (6.97 KB, application/zip)
2017-06-23 10:42 UTC, Saurabh Paunikar
Attached are the logs generated when observed that issue is not fixed in 15.3 build (5.06 KB, application/zip)
2017-06-23 10:42 UTC, Saurabh Paunikar

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 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.

Related Links:

Description James Clancey 2017-05-19 05:26:20 UTC
If you debug on one android device, then you plug in a new device without changing any code, the app does not deploy. And you get an error about the activity not being found on that device.

=== Visual Studio Enterprise 2017 for Mac (Preview) ===

Version 7.1 Preview (7.1 build 583)
Installation UUID: bc6b1fbe-d3ff-45ec-a1ae-d8123578f97a
	Mono (2017-04/4a0006f) (64-bit)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 502000104

=== NuGet ===


=== .NET Core ===

Runtime: /usr/local/share/dotnet/dotnet
SDK: /usr/local/share/dotnet/sdk/1.0.1/Sdks
MSBuild SDKs: /Library/Frameworks/Mono.framework/Versions/5.2.0/lib/mono/msbuild/15.0/bin/Sdks

=== Xamarin.Profiler ===

Version: 1.5.4
Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler

=== Xamarin.Android ===

Version: (Visual Studio Enterprise)
Android SDK: /Users/clancey/Library/Developer/Xamarin/android-sdk-macosx
	Supported Android versions:
		2.3 (API level 10)
		5.1 (API level 22)
		6.0 (API level 23)
		7.0 (API level 24)
		7.1 (API level 25)

SDK Tools Version: 
SDK Platform Tools Version: 25.0.6
SDK Build Tools Version: 25.0.2

Java SDK: /usr
java version "1.8.0_101"
Java(TM) SE Runtime Environment (build 1.8.0_101-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.101-b13, mixed mode)

Android Designer EPL code available here:

=== Apple Developer Tools ===

Xcode 8.3.2 (12175)
Build 8E2002

=== Xamarin.iOS ===

Version: (Visual Studio Enterprise)
Hash: 7571635e
Branch: master
Build date: 2017-05-09 16:04:54-0400

=== Xamarin.Mac ===

Version: (Visual Studio Enterprise)

=== Xamarin Inspector ===

Version: 1.3.0-alpha1
Hash: 0855e01
Branch: master
Build date: Thu, 11 May 2017 04:16:13 GMT

=== Build Information ===

Release ID: 701000583
Git revision: 445a7f09feca58babb966e0c66a6b299d0bd450c
Build date: 2017-05-12 16:05:38-04
Xamarin addins: f9b72ca5f6ca5d9476d8f58353ada2afd56c549b
Build lane: monodevelop-lion-d15-3-preview

=== Operating System ===

Mac OS X 10.12.4
Darwin 16.5.0 Darwin Kernel Version 16.5.0
    Fri Mar  3 16:52:33 PST 2017
    root:xnu-3789.51.2~3/RELEASE_X86_64 x86_64
Comment 1 Greg Munn 2017-05-19 15:19:34 UTC
Changing to XA because they own the install target that's used.
Comment 2 dean.ellis 2017-05-24 08:59:35 UTC
Yup this is ours. This is part of the logic we used to stop the Install target from running all the time. 

In this case it thinks the device has the latest code already. We probably need to cache the device ID we deployed to I'll check
Comment 4 dean.ellis 2017-06-08 12:37:44 UTC
Fixed in monodroid/master/ed610af
Comment 8 dean.ellis 2017-07-05 14:20:59 UTC
Moving to d15.4 milestone
Comment 9 Luis Aguilera 2017-07-05 14:22:37 UTC
after discussing with Dean, and applying this criteria, we've agreed that it's best to move this bug to 15.4. Since it's already fixed and verified in master, this fix will then be released in the first 15.4 preview to ship in the next 2-3 weeks.

Criteria for including bug fixes post-freeze:

1) bug is severe and will have a widespread impact/affect lots of people
2) bug fix is well understood and our informed opinion is that fixing it does not carry an unreasonable amount of risk (i.e we're not likely going to break anything else by inserting this fix now, late in the release cycle)