Bug 4387 - iPad automatic ARMv7 must also set minimum iOS to 3.1
Summary: iPad automatic ARMv7 must also set minimum iOS to 3.1
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: unspecified
Hardware: PC Mac OS
: High normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
Depends on: 3561
  Show dependency tree
Reported: 2012-04-10 20:11 UTC by Sebastien Pouliot
Modified: 2012-04-11 19:44 UTC (History)
2 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 Sebastien Pouliot 2012-04-10 20:11:33 UTC
Fixing bug #3561 added an automatic ARMv7 code generation for iPad-only projects. That's fine except that it's not complete because default project templates do not provide a minimum iOS version and a later check (by the addin) will break the customer build. E.g.

---------------------- Done ----------------------

Project does not have bundle identifier specified. Generated 'myinstrument' to match an installed provisioning profile.
Apps with a minimum OS older than 3.1 cannot be ARMv7 only
Build: 1 error, 1 warning

The solution is to set the minimum, if none, to 3.1 (or maybe 3.2 since that was, IIRC, the first iOS version available for iPad).
Comment 2 Miguel de Icaza [MSFT] 2012-04-10 21:04:15 UTC
Sebastien, is this something that would require an urgent fix, or can it wait for the next MD in May 14th?
Comment 3 Sebastien Pouliot 2012-04-10 21:30:21 UTC
The workaround is simple (just set the "Deployment Target" option in MD). I'd say that, unless some other urgent fixes are (or become) required that it can wait - as long as support is notified.
Comment 4 Jeffrey Stedfast 2012-04-11 19:44:14 UTC
fixed in git master.