Bug 3406 - Debugging stopped Working (Auto-launch of App)
Summary: Debugging stopped Working (Auto-launch of App)
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: 2.9.x
Hardware: Macintosh Mac OS
: High normal
Target Milestone: ---
Assignee: Rolf Bjarne Kvinge [MSFT]
URL:
Depends on:
Blocks:
 
Reported: 2012-02-11 01:36 UTC by Dermot
Modified: 2012-05-13 20:36 UTC (History)
3 users (show)

Tags:
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:
Status:
RESOLVED FIXED

Description Dermot 2012-02-11 01:36:47 UTC
The automatic launching of the app stopped working today. Here is what is displayed in the Application Output:


Please ensure your device is connected...
Connected to: Dermot's IPhone
error MT0000: Unexpected error - Please fill a bug report at http://bugzilla.xamarin.com
System.Xml.XmlException: Document element did not appear.  Line 1, position 1.
at Mono.Xml2.XmlTextReader.Read () <0x001ff>
at System.Xml.XmlTextReader.Read () <0x000b7>
at System.Xml.XmlDocument.ReadNodeCore (System.Xml.XmlReader) <0x00071>
at System.Xml.XmlDocument.ReadNode (System.Xml.XmlReader) <0x0009f>
at System.Xml.XmlDocument.Load (System.Xml.XmlReader) <0x0004f>
at System.Xml.XmlDocument.LoadXml (string) <0x000be>
at MonoTouch.Installation.Installer.KillApplication (MonoTouch.Installation.Device,string) <0x000b8>
at MonoTouch.Installation.Installer/<KillApplication>c__AnonStorey6.<>m__7 (MonoTouch.Installation.Device) <0x00017>
at MonoTouch.Installation.Installer/<ExecuteWithSession>c__AnonStorey3.<>m__2 (object,System.EventArgs) <0x000ef>
at MonoTouch.Installation.Device.NotificationCallback (MonoTouch.Installation.Device/am_device_notification_callback_info&) <0x0006e>
at (wrapper native-to-managed) MonoTouch.Installation.Device.NotificationCallback (MonoTouch.Installation.Device/am_device_notification_callback_info&) <0x0003f>
at (wrapper managed-to-native) MonoTouch.CoreFoundation.CFRunLoop.CFRunLoopRun () <0x00003>
at MonoTouch.CoreFoundation.CFRunLoop.Run () <0x0000b>
at MonoTouch.Installation.Installer.ExecuteWithSession (MonoTouch.Installation.Installer/Executor) <0x000d7>
at MonoTouch.Installation.Installer.KillApplication (string) <0x0005f>
at MTouch.Main2 (string[]) <0x03c0b>
at MTouch.Main (string[]) <0x0001f>
Comment 1 Jeffrey Stedfast 2012-02-11 10:30:10 UTC
Hi Dermot,

You probably want to use MonoDevelop 2.8.6.4. The 2.9.1 series is not caught up with the latest fixes in 2.8.x - it is mostly testing the new code-completion engine.

That said, I'll reassign to Rolf so he can double-check that this is fixed in 2.8.6.4

(2.9.x merges from 2.8.x every once in a while, so maybe it missed some patches)
Comment 2 Rolf Bjarne Kvinge [MSFT] 2012-02-13 18:22:18 UTC
Did you do anything in particular for this to happen (upgrade iOS device, upgrade Xcode / iOS SDK, etc)?

Which versions of Xcode and iOS SDK do you have installed?
Comment 3 Miguel de Icaza [MSFT] 2012-02-14 11:38:20 UTC
Setting bug to NEEDINFO. 

Please change the status when the provided information is added back.
Comment 4 Dermot 2012-05-13 20:36:15 UTC
This does not seem to occur any more with the latest release. Im marking it as closed, will reopen with more info if it occurs again.