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.
"Installation failed: The 'MinimumOSVersion' inside Info.plist does not include the device version (error: 0xe800007e)
The minimum supported version of iOS is set to , which the device does not support.
Either update the device to iOS or newer, or set the Deployment Target in your
project settings to a version your device supports."
MonoDevelop 2.8 beta 3
Mono framework 2.10.5
iOS 5 beta 6
1) Create a new blank MonoTouch project.
2) Set configuration to Release|iPhone.
3) Deploy to device
4) Get the following error message: https://gist.github.com/d23dff3283b07e502cff
This is probably due to MonoDevelop adding a space in their rather than an empty value so it's not auto populated with a default.
*** This bug has been marked as a duplicate of bug 951 ***
This isn't a dupe of the 951. In this case the minimum version is set to a non-empty string, probably a single space character. This is causing the automatic version swizzling to fail and this error to pop up. I'll look into what's causing this in the morning and get it sorted.
We need to figure out where MD puts an empty value into the plist and fix it, then make the plist merge step check for an empty value and either use the default value or fail the build with an error.
Working on this now
*** Bug 1281 has been marked as a duplicate of this bug. ***
Just a FYI, there was no minimum os version key at all. The 'bug' was simply that MD correctly used 5.0 as the MinimumOSVersion and the device being deployed to had iOS 4.3. We now detect this mismatch and display a proper error which the user can understand rather than the rather cryptic error the deployment step used to pop up.