Bug 12622 - MT0000: Unexpected error - device is not connected
Summary: MT0000: Unexpected error - device is not connected
Status: RESOLVED NOT_REPRODUCIBLE
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: 6.3.x
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-06-10 14:57 UTC by branislav
Modified: 2013-06-12 23:04 UTC (History)
2 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 NOT_REPRODUCIBLE

Description branislav 2013-06-10 14:57:03 UTC
After starting XamarinStudio > Start Debugging I received following output:

Please ensure your device is connected...
error MT0000: Unexpected error - Please file a bug report at http://bugzilla.xamarin.com
MonoTouch.MobileDevice.MobileDeviceException: Device is invalid (0xe8000084)
at MonoTouch.Installation.Device.Connect () <0x0007b>
at MonoTouch.Installation.Installer/<ExecuteWithSession>c__AnonStorey15.<>m__15 (object,System.EventArgs) <0x00017>
at MonoTouch.Installation.Device.NotificationCallback (MonoTouch.MobileDevice.am_device_notification_callback_info&) <0x00075>
at (wrapper native-to-managed) MonoTouch.Installation.Device.NotificationCallback (MonoTouch.MobileDevice.am_device_notification_callback_info&) <0x0005b>
at (wrapper managed-to-native) MonoMac.CoreFoundation.CFRunLoop.CFRunLoopRun () <0x00003>
at MonoMac.CoreFoundation.CFRunLoop.Run () <0x0000b>
at MonoTouch.Installation.Installer.ExecuteWithSession (string,MonoTouch.Installation.Installer/Executor) <0x000d7>
at MonoTouch.Installation.Installer.KillApplication (string,string) <0x00063>
at MTouch.Main2 (string[]) <0x028e3>
at MTouch.Main (string[]) <0x00017>

I did not manage to replicate bug and it happened only once.
Most probable reason: user connects device too late.

---
Apple Developer Tools
Xcode 4.6.2 (2067.2)
Build 4H1003

Xamarin.iOS
Version: 6.3.5.43 (Trial Edition)
Hash: 07cde46
Branch: 
Build date: 2013-13-05 14:44:13-0400
Comment 1 Rolf Bjarne Kvinge [MSFT] 2013-06-12 23:04:49 UTC
If it's not reproducible it's not much we can do until it shows up again (and I've never seen this particular error message before).

Most likely it is as you say: an intermittent connection problem between the mac and the device.