Bug 16925 - "Deploy to Device" crash
Summary: "Deploy to Device" crash
Status: RESOLVED NORESPONSE
Alias: None
Product: iOS
Classification: Xamarin
Component: Tools ()
Version: 7.0.4.x
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-12-20 22:33 UTC by Steve Swaringen
Modified: 2016-05-24 21:01 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 NORESPONSE

Description Steve Swaringen 2013-12-20 22:33:18 UTC
/Developer/MonoTouch/usr/bin/mtouch -sdkroot "/Applications/Xcode.app/Contents/Developer" -installdev "/Users/Steve/Projects/AlternateLayoutsSample/AlternateLayoutsSample/bin/iPhone/Debug/AlternateLayoutsSample.app" "--devname=Steve's iPad"
Please ensure your device is connected...

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__AnonStorey17.<>m__22 (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.InstallApplicationWithoutSymbols (string,string) <0x00067>
at MonoTouch.Installation.Installer.InstallApplication (string,string,bool) <0x0002f>
at MTouch.Main2 (string[]) <0x027db>
at MTouch.Main (string[]) <0x00017>

The application was terminated by a signal: SIGHUP
Comment 1 Nischal 2013-12-23 02:03:06 UTC
@Steve: Could you please provide us the testcase/sample that you have used along with the Steps that you followed. So that we also check at our end what exactly causing the error?
Comment 2 Rolf Bjarne Kvinge [MSFT] 2013-12-23 18:34:05 UTC
kAMDMuxConnectError usually happens when there is a physical problem with the connection to the device. It's usually solved by replugging the cable or rebooting the device.
Comment 3 Sebastien Pouliot 2016-05-24 21:01:01 UTC
We have not received the requested information. If you are still experiencing this issue please provide all the requested information and re-open the bug report. Thanks!