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.
Description of Problem:
Android debugger disconnects nearly every time after recent update
Steps to reproduce the problem:
1. Set breakpoint
2. Launch app
3. Hit breakpoint
4. Breakpoint is hit
5. Debugger disconnects after trying to do anything
Debugger stays connected
How often does this happen?
100% of the time
Sometimes, the debugger fails to connect at all
can you try this?
-Start XamarinStudio and try to reproduce.
If you can still reproduce problem can you do same with http://download.xamarin.com/XamarinforVisualStudio/Windows/Xamarin.VisualStudio_3.11.1594.msi
I would like to determine which side is problem here XS or Android SDK.
Can you also attach Ide.log? https://kb.xamarin.com/customer/portal/articles/1675684-where-can-i-find-my-version-information-and-logs-
I am on OS X :)
Sorry about that,
I mixed with another bug...
Same problem. In fact, now I'm not even getting a "debugger disconnected" message box. The app just dies and the debugger disconnects
1) What Android simulator/emulator are you using?
2) Can you please attach log files?
3) Can you try with device or maybe Google Android Emulator?
Seems like it might be related to my device. I seem to most consistently be able to reproduce the problem when I'm connected to my Nexus 6P which is running Marshmallow. I'll try and get you some logs. Which logs specifically were you looking for?
@Dario adb logcat would be useful for this failure scenario.
Out of curiosity, are you using the shared runtime for your debug builds? Does your apk include support for arm64-v8a? We're looking at an issue that's possibly related in Bug #35798, but from what I've seen it's only reproducible when the app _only_ supports armeabi-v7a.
I'll mark this as a duplicate of that issue, please provide any additional information on Bug #35798.
*** This bug has been marked as a duplicate of bug 35798 ***