Bug 23462 - Fast deployment somehow enabled in Release mode
Summary: Fast deployment somehow enabled in Release mode
Status: RESOLVED NOT_REPRODUCIBLE
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android ()
Version: unspecified
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2014-09-29 14:53 UTC by Rogier van der Hee
Modified: 2015-12-04 15:36 UTC (History)
7 users (show)

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


Attachments
fast deployment checked (26.36 KB, image/png)
2014-09-29 14:53 UTC, Rogier van der Hee
Details
csproj file (3.46 KB, text/plain)
2015-12-04 11:00 UTC, Parmendra Kumar
Details


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:
Status:
RESOLVED NOT_REPRODUCIBLE

Description Rogier van der Hee 2014-09-29 14:53:13 UTC
See the screenshot. Somehow I managed to get in this state which AFAIK is illegal in release mode, and it produces empty binaries upon apk release.

Whenever I now uncheck/check the shared runtime manually, the fast deployment is also unchecked. So this seems to be a migration issue from older projects.

Please add a way to ALWAYS disable fast deployment not matter what in release mode. This costed me another few hours.
Comment 1 Rogier van der Hee 2014-09-29 14:53:39 UTC
Created attachment 8236 [details]
fast deployment checked
Comment 2 Rogier van der Hee 2014-09-29 15:17:10 UTC
Xamarin Studio
Version 5.4 (build 240)
Installation UUID: 726adbd8-4443-449d-9a02-c691b68ff379
Runtime:
	Microsoft .NET 4.0.30319.34014
	GTK+ 2.24.22 (MS-Windows theme)
	GTK# 2.12.26

Xamarin.Android
Version: 4.16.0 (Business Edition)
Android SDK: C:\Users\rogie_000\AppData\Local\Android\android-sdk
	Supported Android versions:
		2.1    (API level 7)
		2.2    (API level 8)
		2.3    (API level 10)
		3.1    (API level 12)
		4.0    (API level 14)
		4.0.3  (API level 15)
		4.2    (API level 17)
		4.3    (API level 18)
		4.4    (API level 19)
		4.4.87 (API level 20)
		4.5    (API level 21)
Java SDK: C:\Program Files\Java\jdk1.7.0_67
java version "1.7.0_67"
Java(TM) SE Runtime Environment (build 1.7.0_67-b01)
Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)

Build Information
Release ID: 504000240
Git revision: 01786bc67c7024ec33d327ed27e4416d7a846f4e
Build date: 2014-09-17 11:05:20-04
Xamarin addins: 7cd7dfcd6b7b7b53281508954ec080f1cd153ad3

Operating System
Windows 6.2.9200.0 (64-bit)
Comment 3 Parmendra Kumar 2014-09-30 06:33:33 UTC
I have checked this issue and able to reproduce this. To reproduce this issue I have followed steps mentioned in the bug description.
I also checked on alpha build and getting the same behavior. 

Screencast:http://www.screencast.com/t/D6OiEA50yqM
ZipXamLog: https://gist.github.com/Parmendrak/f9b8dc1d49f655ce655c

Environment Info:
Microsoft Visual Studio Professional 2013
Version 12.0.30723.00 Update 3
Microsoft .NET Framework
Version 4.5.51641

Xamarin   3.6.253.0 (d5d1e8ffa3e94204a5f1c498938b2c71c73cf50e)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.

Xamarin.Android   4.16.0.17 (2a7b68212b17c903160fbd8e0106babb299d1be3)
Visual Studio plugin to enable development for Xamarin.Android.

Xamarin.iOS   8.0.62.0 (8bd8158ae8c65c4fb50665dee520aa4ed86867ba)
Visual Studio extension to enable development for Xamarin.iOS.
Comment 4 Rogier van der Hee 2014-09-30 08:10:51 UTC
As a side note: this produces binaries that upload just fine to the Play Store. And even if you have deployed the Release version to a device (which I usually do before releasing), this just works fine.

The only way to get "notified" of the missing binaries is looking at the size, installing it from the Play Store or installing the APK manually to a device and then logcat it.

Fooled me!
Comment 5 dean.ellis 2015-12-03 18:55:48 UTC
@Parmendra can you attach the csproj for the project once you have replicate the problem please so we can look at the properties being set.
Comment 6 Parmendra Kumar 2015-12-04 11:00:32 UTC
Created attachment 14119 [details]
csproj file

I have checked this issue with latest build and I am not able to reproduce this issue with latest build.
Its working fine fine with latest build.

Screencast: http://www.screencast.com/t/H9yXfBvP

Environment info: 

Microsoft Visual Studio Professional 2013
Version 12.0.30723.00 Update 3
Microsoft .NET Framework
Version 4.6.01055

Installed Version: Professional

Xamarin   4.0.0.1708 (36f3cb2)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.

Xamarin.Android   6.0.0.35 (d300845)
Visual Studio plugin to enable development for Xamarin.Android.

Xamarin.iOS   9.2.1.55 (edf4e56)
Visual Studio extension to enable development for Xamarin.iOS.

Xamarin.iOS Unified Migration   1.0
Automated migration for Xamarin iOS Classic projects to Unified
Comment 7 dean.ellis 2015-12-04 11:53:05 UTC
@rogier are you able to share the .csproj for the project you are having issues with? So we can check out the property settings in the file to see what might have happened.
Comment 8 Rogier van der Hee 2015-12-04 13:34:27 UTC
@dean.ellis: I saw this issue in the 3.x release cycle many moons ago, and since then I have not witnessed it anymore with any of my projects.

So we could close it for now as unreproducible.
Comment 9 dean.ellis 2015-12-04 15:36:17 UTC
@Rogier

Ok thanks for letting us know, if you do see it again feel free to re-open the issue

Dean