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.
The debugger will only connect if you allow MonoDevelop to launch the app. This is counter-intuitive since you are using the wifi debugger.
I believe this is more of a documentation issue than a bug in MonoTouch. I will change text in the dialog MonoDevelop puts up when trying to connect to make sure it's clear that the device needs to be plugged in, is there anything else that might help?
Why is it required to have the device plugged in via USB? The reason I am WIFI debugging it so I can test external accessories. So my dock connector is currently in use.
Once the app has started up you can disconnect the cable. It is only required to have the device plugged in to actually start the app. We pass command line arguments to the app at startup to tell it which ip:port it must connect to on the mac, and that's only possible to do when the device is plugged in.
Right now the ip:port is also in the settings for the app. Those can be manually changed to the port, but the default port has changed. It should use those variables if none are passed it. MT used to set those on deploy as well.
There is no ip:port setting in the app anymore (or shouldn't be in the latest version of MT/MD at least), there's a host setting where you can change the ip (but not the port), but that's it.
The port is selected automatically by MD when the app is started, so there is no default port anymore (it's only used with older versions of MT to be backwards compatible). This avoids a number of problems users had when other software was using the default port.
It is of course possible to fix this so that MD tries to establish a connection to the app in every conceivable way at startup, but it is quite a complex scenario for a fairly minor use case (using an external accessory at startup).
The debugger connecting dialog now says:
Waiting for debugger to connect...
The device must be connected with a usb cable for debugging to start. You can unplug the cable once this dialog disappears.