Bug 16317 - The supported device orientations panel is not populated correctly
Summary: The supported device orientations panel is not populated correctly
Status: CLOSED NORESPONSE
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 1.8.x
Hardware: PC Mac OS
: Low normal
Target Milestone: ---
Assignee: Vinicius Jarina
URL:
Depends on:
Blocks:
 
Reported: 2013-11-18 09:57 UTC by Alan McGovern
Modified: 2015-08-24 08:36 UTC (History)
6 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 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:
CLOSED NORESPONSE

Description Alan McGovern 2013-11-18 09:57:43 UTC
The ipad orientation panel is not populated correctly. As per screencast, it is ignoring the regular SupportedOrientations key and is only looking for the iPad specific one. This is incorrect. When reading the data it needs to look for the iPad one first and then it needs to look for the normal one.

Technically the iPhone/iPod one needs to look for the phone specific key first and then the normal one too, I believe XS does this.

http://screencast.com/t/8qqllZm1
Comment 2 Akhilesh kumar 2015-08-24 07:46:36 UTC
As we are not getting any response and this is a old bug, so I am closing this issue.

Please feel free to reopen it again if you have any concern or suggestion.

Thanks!