Bug 1281 - Migrating old Info.plist files should set MinimumOSVersion
Summary: Migrating old Info.plist files should set MinimumOSVersion
Status: RESOLVED DUPLICATE of bug 1040
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: Trunk
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Alan McGovern
URL:
Depends on:
Blocks:
 
Reported: 2011-10-05 18:22 UTC by Jeffrey Stedfast
Modified: 2011-10-05 18:36 UTC (History)
2 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 1040

Description Jeffrey Stedfast 2011-10-05 18:22:14 UTC
I guess older MD2.4(?) projects didn't need a MinimumOSVersion key/value in the Info.plist, but trying to deploy to a device in MD 2.8 seems to require that key/value in the Info.plist so we should make to sure to set that (based on the minimum MtouchMinimumOS in the .mdp configurations?)
Comment 1 Mikayla Hutchinson [MSFT] 2011-10-05 18:36:07 UTC
No, we don't need a MinimumOSVersion.

If the MinimumOSVersion has no value, MD sets the value in the compiled app equal to the SDK version. That hasn't changed. What seems to have gone wrong is that the MD 2.8 importer or plist editor sets the key, but with a blank but non-null value. The build code interprets that as a value, and write it out to the compiled app's plist.

*** This bug has been marked as a duplicate of bug 1040 ***