Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
simply hitting stop and start without changing any code rebuilds the package. This kills us when it comes to deploying and debugging.
Can you share a screencast of when this happens and your Output/Build log?
I've been working with jonp and tracking some of this stuff down. One fix is in that shaved off anywhere from 40 seconds to a minute. After that we'll look at the next thing.
@stephen, is this still an issue? Our fast-build check would mitigate the stop>run scenario and I'm pretty sure that we don't deploy the .APK again if it was not changed.
Closing. No response and I'm sure this is no longer an issue - I've never seen it.