Bug 1395 - USB debugging doesn't work on MonoDevelop 2.8 / No WiFi debugging available
Summary: USB debugging doesn't work on MonoDevelop 2.8 / No WiFi debugging available
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: 2.8
Hardware: Macintosh Mac OS
: Low normal
Target Milestone: ---
Assignee: Rolf Bjarne Kvinge [MSFT]
Depends on:
Reported: 2011-10-10 11:39 UTC by Matt Jones
Modified: 2012-03-23 20:24 UTC (History)
9 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description Matt Jones 2011-10-10 11:39:26 UTC
USB debugging doesn't work on MonoDevelop 2.8. Also, no WiFi debugging is available.

I have upgraded recently to MonoDevelop 2.8 - before this, my device debugging was working perfectly via WiFi.

It is really annoying having development tool features taken away when you are trying to ship a product.
Comment 1 Dermot 2011-10-10 18:05:39 UTC
I experience similar problems. It works for me, but only once per build. Each time I have to deploy to device again or the debugger >> device connection doesnt occur. Sometimes I have to do a full rebuild and physically connect and disconnect the device to get it working.
Comment 2 Rolf Bjarne Kvinge [MSFT] 2011-10-11 18:19:43 UTC
There is a way to disable usb debugging: add this line:

<Property key="MonoTouch.Debugger.UsbDebugging" value="False" />

to ~/Library/Preferences/MonoDevelop-2.8/MonoDevelopProperties.xml (make sure the key doesn't exist first, in which case you'll just have to switch it to "False" from "True").

I'm working on making it possible to disable usb debugging from within the UI somewhere.
Comment 3 Dimitris Tavlikos 2011-10-14 10:47:11 UTC
I made some tests with debugging, Jeff proposed I posted my remarks here, in case they are of any help:

After some tests with 3 different devices (iPad iOS 5, iPhone 3GS iOS 5 and
iPhone 4 iOS 4.3.5), I noticed that if iTunes is open and syncing with a
device (both on wifi and USB, but not at the same time) and *after* syncing,
my app could never connect to the debugger. Even if the particular device
was ejected from iTunes. Even after syncing of the other device was

But, when I close iTunes, it all works ok! Open iTunes again, once more,
everything ok! Sync a device and wait for it to complete... debugging breaks
Comment 4 Rolf Bjarne Kvinge [MSFT] 2011-10-18 05:24:35 UTC
*** Bug 1544 has been marked as a duplicate of this bug. ***
Comment 5 matt.m.jacobsen 2011-10-18 05:28:54 UTC
Haven't (can't) try USB debugging. It's the iOS Simulator that doesn't work for me.
Comment 6 Jeffrey Stedfast 2011-10-18 18:13:58 UTC
I've added a UI checkbox to MonoDevelop in git to enable WiFi debugging (thanks to Rolf's backend code) which will be included in MonoDevelop 2.8.2

Just need input from MonoDevelop hackers on whether I added it to the right place or not ;-)
Comment 7 Rolf Bjarne Kvinge [MSFT] 2012-03-23 20:17:44 UTC
WiFi debugging can now (for a long time actually) be selected in MonoDevelop's preferences. Marking as fixed.
Comment 8 Dermot 2012-03-23 20:24:00 UTC
I find WiFi debugging fixes the problems I have been having with debugging. Particularly in scenarios such as:

1. Build & Debug
2. Stop debug
3. Attempt to debug again (debugger stops before the first "Finalizer thread started" text appears.
Work -around is to ensure the project is rebuilt and reuploaded for each debugging session (slows things down a lot though.

another problem with USB debugging:

1. Debug on device (a)
2. Stop debugging
3. Disconnect device (a)
4. Build and deploy to device (b)
5. Attempt to debug. Fails. Debugger never connects.
Work around. Restart computer. (Resetting devices doesn't always work, restarting computer usually fixes it). As you can imagine, testing an app that utilizes networking between devices can take a LONG time with this work around.

Wifi debugging seems to get around both of the above issues.