Bug 850 - iPad orentations are not matched pairs warning
Summary: iPad orentations are not matched pairs warning
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: 2.8 Beta 2
Hardware: PC Mac OS
: --- minor
Target Milestone: ---
Assignee: Alan McGovern
Depends on:
Reported: 2011-09-16 05:09 UTC by Rolf Bjarne Kvinge [MSFT]
Modified: 2012-11-13 19:05 UTC (History)
3 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 Rolf Bjarne Kvinge [MSFT] 2011-09-16 05:09:22 UTC
This happens when the Info.plist does not have an entry for ipad orientations (the UISupportedInterfaceOrientations~ipad key does not exist). Yet the MonoDevelop plist editor shows that all ipad orentations are selected.

To reproduce:
Create a new project (single view application - iphone)
Open Info.plist, select all iPhone orientations
Build (no orientation warnings)
Open Info.plist, change Devices to Universal. See that all the iPad orentiations are selected.
Build => "iPad orientations are not matched pairs" shows up
Comment 1 Alan McGovern 2011-09-19 07:57:35 UTC
This error is caused by Orientation.None being returned when the dictionary is queried for the supported orientations. There are two bugs:

1) We should be checkeding for SupportedOrientations~ipad and falling back to SupportedOrientations.

2) We should have a better error message when there are no supported orientations detected. Alternatively we can ignore this case as the iphone/ipad will default to Portrait.
Comment 2 Rolf Bjarne Kvinge [MSFT] 2011-09-19 08:13:38 UTC
3) When changing Devices to Universal, it should probably copy the orientations from the previous Devices settings to the iPad orientations.
Comment 3 Alan McGovern 2011-09-19 08:51:52 UTC
1, 2 and 3 should all be working fine now.

For point 3 we don't create a specific UISupportedInterfaceOrientations~ipad key until the user explicitly clicks on one of the ipad orientation panes. Once they do that, we copy the existing UISupportedInterfaceOrientations values into the UISupportedInterfaceOrientations~ipad and update that from then on. When the ~ipad key does not exist, the iPad panes display exactly what the iphone ones do.