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.
I can successfully deploy multiple times in a row if I let the deploy happen fully.
If I stop the deploy while it's happening, the next deploy will happen in a new Deploy to Device pad, "Deploy to Device (2)"
The initial deploy says that is is 'Removing Old Runtime' twice.
Not all cancellations result in the deploy to device pad being duplicated
After canceling the deploy, the status bar does not update with the cancelation
MD 188.8.131.52 a4a635018f425d71a253d39114d945c4d6f7cbdb-dirty
MFA 4.2.5 184.108.40.206693106
Saw this behavior when deploying to both a Nexus 7 (4.1) and a Samsung Galaxy Tab 2 10.1 (4.0.3)
Fixed in master. Need to figure out how to cleanly backport it.
The steps to reproduce the above issue are as follows:
1. Open any application or create a new MFA application.
2. Select the correct target framework as per the device and debug the application.
3. Now while the application is getting deployed to device; disconnect the device from the machine.
4. Again connect the device to the machine.
5. Debug the same application.
6. Observe that another Deploy to Device tabs is spawned. And this goes on for the multiple times as well and when we does not disconnect the device from the machine the application get deployed successfully.
Perhaps this is another case that will also be fixed with mhutch's patch. We'll have to check it when the fix is available to test.
Yes, my fix also improves error handling including disconnection.
Working on backporting the commits.
It's in monodevelop-3.0.4-branch
Getting an unhandled exception when cancelling deployment. I can no longer spawn multiple Deploy to Device tabs using this new MD.
Closing this bug. Filing 6534 for the unhandled exception.
Nischal - please check your reproduction steps with a new build of MD 220.127.116.11 and re-open or confirm the fix.
Available here: http://storage.bos.xamarin.com/monodevelop-lion-monodevelop-3.0.4-branch/5a/5acb9f90c53377563d27b7e47f95fc7a66bc9289/MonoDevelop-18.104.22.168.dmg