Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
/Developer/MonoTouch/usr/bin/mtouch -sdkroot "/Applications/Xcode.app/Contents/Developer" -installdev "/Users/joe/Projects/Mono/ACR/SalesTALK/SalesTALK/SalesTALK/bin/iPhone/Debug/ACRSalesTALK.app"
Please ensure your device is connected...
error MT0000: Unexpected error - Please fill a bug report at http://bugzilla.xamarin.com
System.NullReferenceException: Object reference not set to an instance of an object
at Xamarin.FastInstaller.NotifyCallback (Xamarin.AMDeviceNotificationCallbackInfo& callback) [0x00000] in <filename unknown>:0
at (wrapper managed-to-native) MonoTouch.CoreFoundation.CFRunLoop:CFRunLoopRun ()
at MonoTouch.CoreFoundation.CFRunLoop.Run () [0x00000] in <filename unknown>:0
at Xamarin.FastInstaller.Run () [0x00000] in <filename unknown>:0
at Xamarin.FastInstaller.InstallApplication (System.String deviceName, System.String appPath) [0x00000] in <filename unknown>:0
at MTouch.Main2 (System.String args) [0x00000] in <filename unknown>:0
at MTouch.Main (System.String args) [0x00000] in <filename unknown>:0
The application was terminated by a signal: SIGHUP
Is this reproducible or does it just happen once in a while?
It only happened once, but the error told me to "Please fill a bug report at http://bugzilla.xamarin.com", so I did.
This case was fixed after 5.3.4 release. Bug #5776  describe a workaround (to use the older upload code).