Bug 5449 - error MT0000: System.Exception: AFCFileRefOpen returned: 8
Summary: error MT0000: System.Exception: AFCFileRefOpen returned: 8
Alias: None
Product: iOS
Classification: Xamarin
Component: XI runtime ()
Version: 5.2
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
: 5583 ()
Depends on:
Reported: 2012-06-01 03:46 UTC by uwantfries
Modified: 2012-06-19 09:36 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 uwantfries 2012-06-01 03:46:39 UTC
/Developer/MonoTouch/usr/bin/mtouch -sdkroot "/Developer" -installdev "/Users/solvdltd/Projects/Spray/Spray/bin/iPhone/Debug/Spray.app"
Please ensure your device is connected...
Connected to: stevek’s iPod Touch
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


MonoDevelop 3.0.2
Installation UUID: d0ba8002-fc02-4783-8821-6eb824eeec26
	Mono 2.10.9 (tarball Mon May  7 20:25:51 EDT 2012)
	GTK 2.24.10
	GTK# (
	Package version: 210090011
Apple Developer Tools:
	 Xcode 4.2 (828)
	 Build 4C199
Monotouch: 5.2.12
Mono for Android: (Evaluation)
Android SDK: /opt/android/sdk/
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

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.6.8
	Darwin Solvd-Ltds-Mac-mini.local 10.8.0 Darwin Kernel Version 10.8.0
	    Tue Jun  7 16:33:36 PDT 2011
	    root:xnu-1504.15.3~1/RELEASE_I386 i386
Comment 1 Rolf Bjarne Kvinge [MSFT] 2012-06-01 04:33:50 UTC
Does this still happen if you replug and/or reboot your device/mac?
Comment 2 uwantfries 2012-06-03 17:10:21 UTC
Not sure. Its quite transitory (seen it about 3 times in the last month?) Not really repeatable. I normally do a clean build and try again if it happens and it goes away.

I will try USB reconnect next time to see what happens.

Comment 3 Rolf Bjarne Kvinge [MSFT] 2012-06-04 17:19:22 UTC
It is likely a hiccup somewhere between the mac and the device, and unless it becomes a bit more frequent than a few times a month it will be very hard to track down.

I'll close this bug report for now, if the problem starts becoming more frequent/annoying feel free to reopen and we'll look deeper into it.
Comment 4 Rolf Bjarne Kvinge [MSFT] 2012-06-19 09:36:14 UTC
*** Bug 5583 has been marked as a duplicate of this bug. ***