Bug 36098 - F5 does not always deploy the APK on device/emulator
Summary: F5 does not always deploy the APK on device/emulator
Status: RESOLVED ANSWERED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-11-20 09:27 UTC by Jerome Laban
Modified: 2016-12-22 23:13 UTC (History)
9 users (show)

Tags: BZCU
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:
Status:
RESOLVED ANSWERED

Description Jerome Laban 2015-11-20 09:27:27 UTC
When using non-fast deployment, the F5 action does not always deploy the APK on the device/emulator, which makes the debugging session silently use the previously deployed APK.

Deleting the APK in the output directory might deploy it, sometimes. Some other times, manually uninstalling the app might fix it temporarily.

This is a new issue to 4.0.
Comment 1 Boris Spinner 2015-12-07 18:51:48 UTC
Happened to me, too.
Comment 2 Jose Gallardo 2016-05-18 14:51:58 UTC
We've seen such behavior if the device date time is ahead of the development machine. Can you guys please confirm if that was causing the issue in this case?

Thanks
Comment 3 Jose Gallardo 2016-12-22 23:13:07 UTC
Resolving as Answered.
If you're still facing this issue with current bits, please feel free to reopen the bug.
Thanks