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 have an inproc Android service and when I hit a breakpoint VS2015 shows me a window saying:
No compatible code running
The selected debug engine does not support any code executing on the current thead (e.g. only native runtime code is executing).
The Threads window is empty as is the Call Stack window.
Debugging against Genymotion.
I reached out to you through our customer support system for additional information. You should see an email from Xamarin with the request very soon. Thank you!
Deleting my bin and obj directories cleared this up. I seem to have to do that a lot with Xamarin for some reason.
Marking this as answered as it was dealt with via customer support.
Don't mean to necro this or anything, but i'm not quite sure this is resolved. I deleted my bin and obj directories and haven't gotten anywhere. Other people have reported similar problems in the last year. https://forums.xamarin.com/discussion/80413/no-compatible-code-running
The existing description of this bug as of Comment 3 was fairly broad, the bug is fairly old, and the last comment (Comment 3) suggests that the issue was resolved for the original reporter of this particular bug over another support contact channel. Given those considerations, the best way forward for any other user seeing a similar behavior in recent versions would be to file a new bug report, including as many details as possible such as steps to reproduce, actual vs. expected results, and environment information. Thanks in advance!