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.
Using two devices:
1. Build, upload and debug the app on device A.
2. Stop debugging.
3. Unplug A
4. Plug in device B
The app will not be uploaded to device B, so you will either be debugging an old or non-existant version.
MD sets a flag file to indicate that the app has been uploaded so that it does not get uploaded again until it is rebuilt, because uploading is quite slow. If MD could detect the ID of the attached device, then this flag could be per device, which would fix the problem.
A similar problem is when the user manually removes the app from the device. To fix this, MD would have to be able to detect the presence of the app on the device.
Yeah, the removed app thing is more understandable. However, it is a pretty common thing to do. Since so many apps have 'first run' code, I remove my app very frequently while debugging.
It looks like this has been fixed already with an mtouch -isappinstalled command that MD issues to determine if it needs uploading.