Bug 18667 - Cannot deploy to device
Summary: Cannot deploy to device
Status: RESOLVED NORESPONSE
Alias: None
Product: iOS
Classification: Xamarin
Component: Tools ()
Version: 7.2.0
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2014-03-31 11:33 UTC by Nik
Modified: 2015-04-20 10:56 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 Nik 2014-03-31 11:33:32 UTC
After the most recent update, I have this error happening when trying to deploy to my device.

-----------

Please ensure your device is connected...
Connected to: iPhone 5s MyPhone
error MT0000: Unexpected error - Please file a bug report at http://bugzilla.xamarin.com
MonoTouch.MobileDevice.MobileDeviceException: Invalid Host ID Error (error: 0xe800001c)
at MonoTouch.Installation.Device.ValidatePairing () <0x0007b>
at MonoTouch.Installation.Installer/<ExecuteWithSession>c__AnonStorey17.<>m__22 (object,System.EventArgs) <0x000c7>
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) <0x0017f>
at MonoTouch.Installation.Installer.InstallApplicationWithoutSymbols (string,string) <0x000d3>
at MonoTouch.Installation.Installer.InstallApplication (string,string,bool) <0x0002f>
at MTouch.Main2 (string[]) <0x038c7>
at MTouch.Main (string[]) <0x00017>
Comment 1 PJ 2014-03-31 13:07:15 UTC
Hi Nik - any chance you remember which update was the one that seemed to break this for you? 

Either way  if you could provide the full version information from the about window in Xamarin Studio it would be very helpful.

Moving this to the iOS Add-in for now (was in iOS Designer), but it's likely to be an issue with monotouch itself.
Comment 2 Nik 2014-03-31 13:25:08 UTC
Hi PJ,
Below is the info from Xamarin Studio's about window. Thank you :)

-----------------

Xamarin Studio
Version 4.2.3 (build 60)
Installation UUID: c5b6afc1-a07b-4081-a554-a8a7010208e9
Runtime:
	Mono 3.2.6 ((no/9b58377)
	GTK+ 2.24.23 theme: Raleigh
	GTK# (2.12.0.0)
	Package version: 302060000

Apple Developer Tools
Xcode 5.1 (5084)
Build 5B130a

Xamarin.iOS
Version: 7.2.0.2 (Indie Edition)
Hash: 58c3efa
Branch: 
Build date: 2014-10-03 18:02:26-0400

Xamarin.Android
Version: 4.12.1 (Starter Edition)
Android SDK: /Users/niaher/Library/Developer/Xamarin/android-sdk-mac_x86
	Supported Android versions:
		2.1   (API level 7)
		2.2   (API level 8)
		2.3   (API level 10)
		3.1   (API level 12)
		4.0   (API level 14)
		4.0.3 (API level 15)
Java SDK: /usr
java version "1.6.0_65"
Java(TM) SE Runtime Environment (build 1.6.0_65-b14-462-11M4609)
Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-462, mixed mode)

Xamarin.Mac
Xamarin.Mac: Not Installed

Build Information
Release ID: 402030060
Git revision: 30c4afc300c2a39ec5300851357ce02e49dd217e
Build date: 2014-03-05 22:09:33+0000
Xamarin addins: f8a9589b57c2bfab2ccd73c880e7ad81e3ecf044

Operating System
Mac OS X 10.9.1
Comment 3 PJ 2014-03-31 14:04:47 UTC
Hrm, so the versions you're using don't have any similar reports coming through, it may be a state your device is currently in.

One user saw that this goes away after doing a rebuild all cycle, see https://bugzilla.xamarin.com/show_bug.cgi?id=12651#c6

It could also help to clean and/or restart your device. 

I'll reset this one to NEW to see if our MonoTouch devs can investigate, let us know if the above helps get you running again.
Comment 4 Jeffrey Stedfast 2014-03-31 14:43:30 UTC
guessing this was meant to be filed under iOS and not Xamarin Studio...
Comment 5 Sebastien Pouliot 2014-03-31 20:11:13 UTC
@Nik the pairing is a process done between the Mac and your device. Checking for this is a pre-requisite to continue talking to the device. It's very uncommon to see this error and, generally, it's the device state that's "confused".

Can you:

a) close Xcode (if open) then use iTunes to sync your device. If there are error(s) please paste it/them into the bug report;

b) reboot your device and try again. The device state should be back to "normal" (and so should be the communication with the Mac host).

and let us know if this solve the issue ? Thanks!
Comment 6 Sebastien Pouliot 2015-04-20 10:56:36 UTC
I'll assume everything when fine with either (a) or (b). If not please re-open the bug and provide additional information. Thanks!