Bug 5583 - Upload to Device failure
Summary: Upload to Device failure
Status: RESOLVED DUPLICATE of bug 5449
Alias: None
Product: iOS
Classification: Xamarin
Component: Tools ()
Version: 5.2
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-06-08 12:46 UTC by Bart
Modified: 2012-06-19 09:39 UTC (History)
3 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 DUPLICATE of bug 5449

Description Bart 2012-06-08 12:46:34 UTC
MonoDevelop 3.0.2
Installation UUID: 7148167c-7960-4ff1-ba07-662a4795a4ca
Runtime:
	Mono 2.10.9 (tarball Mon May  7 20:25:51 EDT 2012)
	GTK 2.24.10
	GTK# (2.12.0.0)
	Package version: 210090011
Apple Developer Tools:
	 Xcode 4.3.2 (1177)
	 Build 4E2002
Mono for Android: 4.2.2.134493563
Android SDK: /Users/bartsipes/Library/Developer/Xamarin/android-sdk-mac_x86
Supported Android versions:
	Version: 1.6	ApiLevel: 4
	Version: 2.1	ApiLevel: 7
	Version: 2.2	ApiLevel: 8
	Version: 2.3	ApiLevel: 10
	Version: 3.1	ApiLevel: 12
	Version: 4.0	ApiLevel: 14
	Version: 4.0.3	ApiLevel: 15
Java SDK: /usr/bin

Monotouch: 5.2.12
Build information:
	Release ID: 30002000
	Git revision: 046db1bb0d9d438aa4d3468d66c6f963bc44c51a-dirty
	Build date: 2012-05-23 21:39:54+0000
	Xamarin addins: d99a1741642a336943d5607bdc1a09efa2ac3b86
Operating System:
	Mac OS X 10.7.4
	Darwin macbook-pro-3.chrobinson.com 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


Please ensure your device is connected...
Connected to: Bart’s iPhone
Initializing file service...
Uploading application
error MT0000: Unexpected error - Please fill a bug report at http://bugzilla.xamarin.com
System.Exception: AFCFileRefOpen returned: 8
at MonoTouch.Installation.AFCService.UploadDirectory (string,string) <0x002ef>
at MonoTouch.Installation.Installer.UploadApplication (MonoTouch.Installation.Device,string) <0x0038b>
at MonoTouch.Installation.Installer/<InstallApplication>c__AnonStorey4.<>m__3 (MonoTouch.Installation.Device) <0x00017>
at MonoTouch.Installation.Installer/<ExecuteWithSession>c__AnonStorey3.<>m__2 (object,System.EventArgs) <0x000ef>
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-06-19 09:36:14 UTC
Does this still happen if you replug and/or reboot your device/mac?

In any case it's a duplicate of bug #5449.

*** This bug has been marked as a duplicate of bug 5449 ***
Comment 2 Bart 2012-06-19 09:39:00 UTC
No, the problem did not occur again. I believe I replugged the device and restarted MonoDevelop.