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 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.
In "Supported Device Orientations" under "iPad Deployment Info" in the "iOS Application" tab in the project properties, the buttons seem to deselect themselves whenever I close the project properties. The iPhone device orientations, however, remain unchanged.
I'm currently using both landscape options, although I don't think that has anything to do with it.
More info: running VS2012 in administrator mode does not solve the problem. The problem only occurs whenever the project properties tab is closed, not when you switch to another tab and back.
Today we have tried to reproduce this issue. But we are unable to reproduce it.
We have followed the steps mention in screencast : http://screencast.com/t/g2iqUPrjA
Please have a look and let us know if we have to follow some other steps to reproduce this issue.
Those are the exact steps I take, but with you the bug doesn't occur.
I've checked the Info.plist file, which is properly updated when modifying the values inside the menu then saving. It writes properly, and other values are properly read. Only the iPad orientation values are ignored when reading. The order of the key/values in Info.plist does not seem to matter.
In Info.plist, this part is ignored:
Is there any other information I can give to help?
I have checked this issue with following builds and I am not able to reproduce the reported behavior.
Microsoft Visual Studio Professional 2013
Version 12.0.31101.00 Update 4
Microsoft .NET Framework
Installed Version: Professional
Xamarin 3.11.666.0 (ebae43a)
Xamarin.Android 188.8.131.52 (5f55a9ef61c11b6ce0890bc91e4c71b1b92be214)
Xamarin.iOS 184.108.40.206 (67b390d0d1bd741582cf7b7fd3ffea08583a3f83)
For now, I am closing this issue. Could please check the reported behavior with latest stable Xamarin build of Visual Studio? If you get this issue again with the latest XVS, please feel free to reopen the issue.