Bug 7184 - Crash uploading to device
Summary: Crash uploading to device
Status: RESOLVED NOT_REPRODUCIBLE
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: 5.99.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-09-14 17:58 UTC by ric3kg
Modified: 2013-01-28 13:34 UTC (History)
5 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 ric3kg 2012-09-14 17:58:39 UTC
Please ensure your device is connected...
error MT0000: Unexpected error - Please fill a bug report at http://bugzilla.xamarin.com
System.Exception: AMDeviceConnect returned: 0xe8000065
at MonoTouch.Installation.Device.Connect () <0x0008f>
at MonoTouch.Installation.Installer/<ExecuteWithSession>c__AnonStorey3.<>m__2 (object,System.EventArgs) <0x00017>
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.InstallApplication (string) <0x0006f>
at MTouch.Main2 (string[]) <0x03b53>
at MTouch.Main (string[]) <0x0001f>

The application was terminated by a signal: SIGHUP
Comment 1 Rolf Bjarne Kvinge [MSFT] 2012-09-14 18:40:21 UTC
0xe8000065 = kAMDMuxConnectError

Which MonoTouch version are you using?
Comment 2 ric3kg 2012-09-14 18:41:07 UTC
MonoDevelop 3.0.3.5
Installation UUID: 60b46495-90e8-4d86-8cb5-33f6efcb8fec
Runtime:
	Mono 2.10.9 (tarball)
	GTK 2.24.10
	GTK# (2.12.0.0)
	Package version: 210090011
Apple Developer Tools:
	 Xcode 4.3.2 (1177)
	 Build 4E2002
Monotouch: 5.2.13
Mono for Android not installed
Build information:
	Release ID: 30003005
	Git revision: 3d53e1366933298a3fe0cdc6d0f7d00c9916564c-dirty
	Build date: 2012-07-27 19:06:34+0000
	Xamarin addins: 73ecde7c48d943adb6e33d511d3cf0661d006801
Operating System:
	Mac OS X 10.7.4
	Darwin Pro-Book 11.4.0 Darwin Kernel Version 11.4.0
	    Mon Apr  9 19:32:15 PDT 2012
	    root:xnu-1699.26.8~1/RELEASE_X86_64 x86_64
Comment 3 Rolf Bjarne Kvinge [MSFT] 2012-09-14 18:52:41 UTC
Can you try MonoTouch 5.4?

This particular area of MonoTouch has many improvements in the latest release.
Comment 4 Chris Jurney 2012-10-01 18:29:55 UTC
I'm seeing the same thing in 6.0.1:

Please ensure your device is connected...
Connected to: Device Name
Initializing file service...
Transferring application
Finalizing file service...
error MT0000: Unexpected error - Please file a bug report at http://bugzilla.xamarin.com
MonoTouch.MobileDevice.MobileDeviceException: AMDeviceConnect returned: 0xe8000065 (kAMDMuxConnectError)
at MonoTouch.Installation.Device.Connect () <0x0007b>
at MonoTouch.Installation.Installer/<ExecuteWithSession>c__AnonStorey4.<>m__3 (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&) <0x0003f>
at (wrapper managed-to-native) MonoTouch.CoreFoundation.CFRunLoop.CFRunLoopRun () <0x00003>
at MonoTouch.CoreFoundation.CFRunLoop.Run () <0x0000b>
at MonoTouch.Installation.Installer.ExecuteWithSession (string,MonoTouch.Installation.Installer/Executor) <0x000d7>
at MonoTouch.Installation.Installer.InstallApplication (string,string) <0x000b3>
at MTouch.Main2 (string[]) <0x0431b>
at MTouch.Main (string[]) <0x00017>

MonoDevelop 3.0.4.7
Installation UUID: d1876297-f5a9-4ff7-a4e7-9eefdf0826d8
Runtime:
	Mono 2.10.9 (tarball)
	GTK 2.24.10
	GTK# (2.12.0.0)
	Package version: 210090011
Apple Developer Tools:
	 Xcode 4.5 (1839)
	 Build 4G182
Monotouch: 6.0.1
Mono for Android: Not Installed

Build information:
	Release ID: 30004007
	Git revision: ea0108260c6a376ecaeffcdb7d03387bd51edda3
	Build date: 2012-09-17 14:09:17+0000
	Xamarin addins: ec43fd5cb223ead4234a9858d1b56eef03dad53a-dirty
Operating System:
	Mac OS X 10.7.5
	Darwin noblehat.polaris.net 11.4.2 Darwin Kernel Version 11.4.2
	    Thu Aug 23 16:25:48 PDT 2012
	    root:xnu-1699.32.7~1/RELEASE_X86_64 x86_64
Comment 5 Rolf Bjarne Kvinge [MSFT] 2012-10-01 19:18:09 UTC
Chris, is the error reproducible, or random? Does it help to restart the device and/or your mac?
Comment 6 Chris Jurney 2012-10-01 21:19:17 UTC
It was all devices every time until I restarted, then no issue.  Killing all apps and relaunching them didn't resolve it.
Comment 7 Rolf Bjarne Kvinge [MSFT] 2012-10-02 05:54:12 UTC
It's likely that the Mac got into a broken state then, some existing process was probably holding onto a device-related resource causing this to happen. Unfortunately since it's not reproducible it's close to impossible to track down (and it may very well not be a problem with MonoTouch at all).

I will close this bug report for now, if it happens in a reproducible way, please reopen and we'll have a second look at it.
Comment 8 Erik Kerber 2013-01-28 13:34:33 UTC
A few months old, but I will add that I get this from time to time as well.

It can (usually) be remedied by killing the usbmuxd process, and retrying the deploy.