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.
Created attachment 153 [details]
I'm trying to deploy a new untouched MonoTouch Single View application - iPhone
it deploys correctly to iPhone simulator but when I try to deploy to device I get
Installation failed: AMDeviceInstallApplication returned: 0xe800007e
The application was terminated by a signal: SIGHUP
the funny thing here is that I'm able to deploy without any problems old projects made on older versions of MonoDevelop migrated by MonoDevelop 2.8, but any new projects created by MD 2.8 are getting this issue
i've attached the project and 2 pics of the error
Created attachment 154 [details]
Debug Error pic
Created attachment 155 [details]
Release Error Pic
Check (compare to working projects):
* the "Minimum Version" of your application is set for;
* the signing / provisioning profiles are correct;
Yes all of the settings are the same that on my working projects, also I don't have this issue on MD 2.6 RC2's new projects the build and deploy ok
Deploying to the simulator is very different than deploying to the device. The error comes from a code path that is executed only for devices. Many additional validations are made, on the device, during installation.
From your project attachment I can see that the compiled* Info.plist has a MinimumOSVersion set to "5.0" - are your other projects 5.0-based too ?
* the version inside "/bin/iPhone/Debug/HolaMDNew.app/"
Can you compare (or attach) the compiled Info.plist from a working project you built/deployed with 2.8a1 ?
I can duplicate the same error if I edit my Info.plist to require "5.0" (MinimumOSVersion) and try to install the app into my (4.3) iPad.
I'll change the error message to be a bit more useful - but I do want to know if the same (or a similar) condition is happening to you ? (I will tweak the error message to cover both case if needed ;-)
Yikes, you are sooooo Right Sebastien (as always hehe) that was it, the minimum version so yeah a more detailed error would be really useful ;)
Thanks for the confirmation! Newer MT release will have a specific error message for 0xe800007e.
Sebastien one more thing why im unable to use lower version than 5.0 on MD 2.8a1 as minimum sdk? I just get defaul and 5.0 as options, is that a bug?
afaik the MD addin checks what's available on your system and adjust its UI automagically. i.e. you'll have a single OS SDK and several simulator SDK available (that's how Apple ship their SDK).
In my case I get, from the add-in UI, the same choices as what was installed for the 4.3 iOS SDK, e.g.
$ l /Developer/Platforms/iPhoneOS.platform/Developer/SDKs/
drwxr-xr-x 8 root wheel 272 18 Jul 11:37 iPhoneOS4.3.sdk
$ l /Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/
drwxr-xr-x 8 root wheel 272 18 Jul 11:37 iPhoneSimulator3.2.sdk
drwxr-xr-x 9 root wheel 306 18 Jul 11:37 iPhoneSimulator4.0.sdk
drwxr-xr-x 8 root wheel 272 18 Jul 11:38 iPhoneSimulator4.1.sdk
drwxr-xr-x 8 root wheel 272 18 Jul 11:38 iPhoneSimulator4.2.sdk
drwxr-xr-x 8 root wheel 272 18 Jul 11:38 iPhoneSimulator4.3.sdk
p.s. I _think_ the "Default" is only useful for the simulator build (or I just don't know how it can help ;-)
Ok, so a solution its to manually override that value of the plist? if so, would that be ok on distribution release? I mean just overriding that setting
Generally, you should always build with the latest SDK. That's why the value defaults to "Default", which will always use the latest SDK installed, so you don't have to manually update it.
However, the minimum OS can be lower than the SDK version. You can code to the API that was only available in the older OS, and the app will run fine on the older OS. What's more interesting is that you can check the OS at runtime and use newer features on newer OSes.
Thanks a lot Michael and Sebastien for the explanation :)