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.
With latest few releases of Xamarin Studio and Mono for Android I am having problems with debugger, which fails to connect to Android device. The application runs fine when deploying to device that was freshly booted, but after a few deploys the XS is stuck at "Terminating running application", and the application output looks something similar to this:
Forwarding debugger port 8821
Forwarding console port 8822
Detecting existing process
This happens when deploying app to Android devices with system version lower than 4.0. And I also found out that the bug mostly but not always happens when I am stepping through code, and then terminate application while I am still in debugging process. It also happens sometimes after exceptions are thrown and debugger automatically stops at the point of where the exception was thrown. If I try to deploy application after the described procedure XS is stuck at "Terminating running application". Application is then never deployed, restarting XS and disconnecting device does not help, the only thing that helps is restarting the phone and then deployment works fine, but usually not for long, which is very annoying.
Thank you for taking the time to submit this report. After reviewing the description of this bug, we believe it no longer affects the current version of Xamarin.Android. If you are still experiencing the issue after updating your packages, please reopen this report with an attached reproduction.