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 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.
A customer has reported an oddity with rotating views when the App is built in Xamarin Studio instead of Visual Studio.
The developers are using Visual Studio 2012 with Xamarin.iOS 220.127.116.11. The project is making use of MvvmCross v3. The rotation problem only occurs in Xamarin Studio, not Visual Studio.
They have a video playback view controller that should also be allowed in landscape but the rest of the App is portrait only. They have enabled AllButUpsideDown in Info.plist and added overrides to their derived from UINavigationController orientation methods.
It all works well when the App is built from Visual Studio but not from Xamarin Studio. If the display is rotated while on the video playback screen the view does not rotate. When switching to full screen playback and watching the playback in landscape and leaving the video again the title bar clings to the side of the screen for all screens, regardless of orientation, although the screen content is in portrait mode.
The desk case was closed so I'm assuming this has been solved.
You guys asked for a for a small test case (don't think this was provided)
"It would be really useful if you could reproduce the issue in a new project, this would let us know that the issue with the build system rather than project.".
We're many Xcode versions (and msbuild changes) above what was used in 2013 I think it's safe to assume the generated Info.plist would be pretty different today.
I'm closing this issue because the desk case is closed and we don't have a test case but feel free to reopen this bug if it is still happening.