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.
Can not debug any of my apps anymore either with Xamarin Studio or Visual Studio. The app deploys and the debugger starts for a second and then fails with "the connection with the debugger has been lost"
More details at: http://forums.xamarin.com/discussion/4111
We're still investigating. What we know so far is some "what", but not the "why".
What we know is that how Mono implements breakpoints doesn't work reliably on the Samsung Galaxy S4 for all API levels.
There are two workarounds:
1. Use a $(TargetFrameworkVersion) of Android v3.1. (Why? No idea.)
2. Use soft breakpoints instead of the normal breakpoints:
adb shell setprop debug.mono.env MONO_DEBUG=soft-breakpoints
*** Bug 12266 has been marked as a duplicate of this bug. ***
The bug also doesn't happen when S4 software is updated. Mine started working after update to http://www.screencast.com/users/RadekDoulik/folders/Default/media/92aed69e-3ca3-468b-8345-99e7079dd955
Same here. It works at the moment with Android 4.2.2, but not sure whether the S4 update fixed it.
Adding to this, Verizon S4 works great, but T-Mobile S4 crashes randomly when targeting API 17
I think this should be now fixed with uptodate firmware on S4.