Bug 22426 - MT0000 / Device is invalid (0xe8000084)
Summary: MT0000 / Device is invalid (0xe8000084)
Alias: None
Product: iOS
Classification: Xamarin
Component: XI runtime ()
Version: master
Hardware: PC Mac OS
: Normal normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2014-08-27 15:42 UTC by Larry O'Brien
Modified: 2014-09-08 09:43 UTC (History)
3 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 Larry O'Brien 2014-08-27 15:42:35 UTC
Going through normal edit-and-debug cycle: app running on device fun. Made an edit, went to deploy, and got the attached stacktrace. Cleaned, recompiled, and deployed fine. 

I cannot reproduce, but the error message said "please," so I am filing a bug. :-) 


Please ensure your device is connected...
Connected to: Larry O'Brien’s iPhone
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__AnonStorey0.<>m__0 (object,System.EventArgs) <0x00017>
at MonoTouch.Installation.Device.NotificationCallback (MonoTouch.MobileDevice.am_device_notification_callback_info&) <0x00077>
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 () <0x00012>
at MonoMac.CoreFoundation.CFRunLoop.Run () <0x0000b>
at MonoTouch.Installation.Installer.ExecuteWithSession (string,MonoTouch.Installation.Installer/Executor) <0x0016b>
at MonoTouch.Installation.Installer.LaunchApplication (string,string,System.Collections.Generic.List`1<string>) <0x0027f>
at MTouch.Main2 (string[]) <0x03e73>
at MTouch.Main (string[]) <0x00017>
Comment 1 Rolf Bjarne Kvinge [MSFT] 2014-09-08 09:43:08 UTC
This is most likely a hiccup somewhere between the device and the mac.

I'm closing this bug report now, if it's reproducible we'll have a second look.