Bug 34362 - MonoDroid Previous Version
Summary: MonoDroid Previous Version
Status: RESOLVED FIXED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Joaquin Jares
URL:
Depends on:
Blocks:
 
Reported: 2015-09-28 16:38 UTC by Joe Mellin
Modified: 2015-09-29 11:06 UTC (History)
4 users (show)

Tags:
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 FIXED

Description Joe Mellin 2015-09-28 16:38:32 UTC
This error / notification comes up for a lot of reasons and is not helpful to users.  

http://stackoverflow.com/questions/21581863/build-failed-monodroid-does-not-support-running-the-previous-version/32827555#32827555

One reason this error message comes up is when someone starts deploying to the android emulator and before the app is deployed, the user closes the emulator.

There should be a different error message for this workflow.
Comment 1 Nina 2015-09-28 17:30:06 UTC
It looks like the monodroid notification no longer come up in C6 alpha. QA should verify this.

However, deployment fails silently.

Can we add a string somewhere explaining what happened - for example, stating that no emulator was available? Thoughts?
Comment 2 Joaquin Jares 2015-09-29 11:06:26 UTC
The behavior is identical to WinPhone behavior, so it's perfectly ok in my book. If we wanted to change it, that's all android targets, so not on our domain. Again, I wouldn't :)

Closing as Resolved-Fixed in C6.