Bug 5061 - Document element did not appear.
Summary: Document element did not appear.
Status: RESOLVED DUPLICATE of bug 3470
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: 5.3.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2012-05-14 06:25 UTC by Liddle Fang
Modified: 2012-05-14 08:29 UTC (History)
2 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 Liddle Fang 2012-05-14 06:25:55 UTC
Please ensure your device is connected...
Connected to: Fang Huai-An 的 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) <0x000cf>
at MonoTouch.Installation.Installer.KillApplication (string) <0x0005f>
at MTouch.Main2 (string[]) <0x03c1f>
at MTouch.Main (string[]) <0x0001f>
Comment 1 Rolf Bjarne Kvinge [MSFT] 2012-05-14 08:29:04 UTC
This has been fixed in the latest 5.3.3 beta.

*** This bug has been marked as a duplicate of bug 3470 ***