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:
After iOS update 126.96.36.199 Debugger only connects about 1 out of every 4 attempts when attempting to debug on my iPad
I have to cancel, launch, cancel, launch over and over until it finally works. This happened right after I applied the iOS 7.0.5 update.
Steps to reproduce the problem:
1. Start debugging on a device
App launches on device but debugger is not connected and eventually errors out with a message that the debugger cannot connect.
Debugger is attached
How often does this happen?
Seems to be about 4-5 times in a row before the debugger will actually attach, then I can usually attach again once before it is back to this state.
Do you get an MT1107 (or whatever it is) error in the output window?
I was having this problem last week and a reboot of my iPad solved it. Maybe rebooting your device will help?
Yeah, I rebooted everything, a few times. I uninstalled 7.0.5, installed 7.0.4 and then re-installed 7.0.5 and so far debugger has only failed once. Will see how it does over the next few days and might just chalk it up to jacked up installed the first time.
since you didn't post new comments. I'm assuming this is not happening anymore, or is it?
I forgot I opened a bug.
It doesn't seem to be happening as often now, only once in a while. When it does happen I reboot the device and that appears to correct it.