`SystemChrome.setPreferredOrientations` landscape right or left doesn't work in some conditions about flutter

[mossmana]

FYI team-ios: I'm already working on an issue that relates to orientation changes for Android - #144307. So, I can investigate this area of code as it relates to Android. However, there seems to be a cross-platform issue with SystemChrome.setPreferredOrientations. As noted above, there have also been a couple other issues reported in the past for iOS. In response to #147460 (comment), we may want to clarify the expected iOS behavior in regards to Xcode.

[darshankawar]

Thanks for the report @Tom3652
Is this specific to iOS or Android ?
Also, please check below issues and see if they help in your case or not.

#34230
#73651

[Tom3652]

Since you showed me older issues, i have tested them and i have also tested everything using the latest flutter version 3.19.6.

The below tests are made using my sample code in the issue.

1. IOS :

• Every rotation (or combination of rotation) is working fine except portraitDown with the error : Failed to change device orientation: Error Domain=UISceneErrorDomain Code=101 "None of the requested orientations are supported by the view controller. Requested: portraitUpsideDown; Supported: landscapeRight" UserInfo={NSLocalizedDescription=None of the requested orientations are supported by the view controller. Requested: portraitUpsideDown; Supported: landscapeRight}

Note : Rotations are blocked if you uncheck the rotation directly in Xcode (in that case, SystemChrome can't do anything)

2. Android :

• Use portraitUp && landscapeRight or portraitUp && landscapeLeft, only portraitUp is working
• Use portraitUp && landscapeRight && landscapeLeft it works fine
• Use landscapeRight || landscapeLeft alone, it starts in the correct orientations but doesn't rotate to the other

This follows my initial issue comment.

For now it's all the tests i have made, i have not tried portraitDown on Android but will update the comment once i do it of course

[mossmana]

The solution to this issue will warrant additional discussion (see #148136).

So, I am unassigning myself for now.