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't be very specific with this, as I only get an error saying "Can't connect to debugger"
2.9.x does this with 5.1.1 (or whatever latest beta is)
2.8.x (latest) does it with 5.1.1, but not with 5.0.3, which works fine.
Happy to provide more info if you tell me how to get it! No stack trace comes with it.
So, with MonoDevelop 2.8.latest and MonoTouch 5.1.1 can you:
* Add "-v -v -v -nofastsim" to mtouch' additional arguments
* Run again (either device or simulator, wherever it happens), and get the output in the iOS device log (for device) and application log (for simulator)
* If it happens on device, switch between usb and wifi debugging to see if it makes a difference.
* Upload MonoDevelop's log file (~/Library/Logs/MonoDevelop-2.8/MonoDevelop.log)
Bother. I reinstalled 5.1.1 and it all works now. With and without the -v -v -v -nofastsim
Do you still want the dump? I swear it wasn't working before.... :)
It's a known bug with latest MD 2.8 + MT 5.0.*, so that's probably where you saw it.
It's a known bug which has been fixed, so I don't need the dump anymore unless you run into the bug again next time you update MD :)