Bug 37064 - ViewWillTransitionToSize API cannot return correctly value every time
Summary: ViewWillTransitionToSize API cannot return correctly value every time
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: XI 9.2
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2015-12-16 04:44 UTC by Jesse Jiang
Modified: 2016-04-12 15:48 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 Jesse Jiang 2015-12-16 04:44:26 UTC
Hi Xamarin,

I'm working on a project, which need to support iOS Multi Tasking. This project need to change the UI layout when user into Slide Over or Split View Mode. I try to get the screen size from  ViewWillTransitionToSize API, but this API sometime return the correct value, but sometimes not.

I'm not sure if this is the Xamarin bug or iOS bug.

Comment 1 Sebastien Pouliot 2015-12-16 13:15:47 UTC
Please attach a test case that show the issue. We need to see how and when this happens to see if it's an issue in either XI or iOS itself. Thanks!
Comment 2 Sebastien Pouliot 2016-04-12 15:48:18 UTC
We have not received further information and will assume this is not an issue anymore. If you can still affected by this please re-open the bug and include the requested information. Thanks.