Search Issue Tracker
Fixed in 2022.2.18f1
Fixed in 2022.2.X, 2023.2.X, 2023.2.0a13
Votes
0
Found in
2022.2.16f1
2023.2.0a11
Issue ID
UUM-33690
Regression
Yes
[iOS] “Screen.orientation” returns wrong orientation when rotating a device
How to reproduce:
1. Build And Run the attached “ScreenOrientation.zip” project on an iOS device
2. Hold the device in portrait orientation, then turn the device to the right and back to portrait orientation
3. Observe the printed Screen Orientation
Expected result: Printed Screen Orientation is Portrait > LandscapeLeft > Portrait
Actual result: Printed Screen Orientation is Portrait > LandscapeLeft > PortraitUpsideDown
Reproducible with: 2022.2.13f1, 2022.2.16f1, 2023.2.0a6, 2023.2.0a11
Not reproducible with: 2020.3.47f1, 2021.3.23f1, 2022.2.0a17, 2022.2.12f1, 2023.1.0a1, 2023.1.0b13, 2023.2.0a5
Reproduced on:
VLNQA00494 - iPhone 14 Pro Max, 16.3.1 iOS
VLNQA00358 - iPhone 12, 14.1 iOS
VLNQA00392 - iPad (9th generation), 15.0 iOS
VLNQA00310 - iPad Pro 12.9", 13.4.1 iOS
Not reproduced on:
VLNQA00520 - Galaxy S22 USA (SM-S901U), CPU: Snapdragon 8 Gen 1 (SM8450), GPU: Adreno 730, OS: 12
Note: If repeating the 2nd step a few times screen orientations keeps changing (Portrait > LandscapeLeft > PortraitUpsideDown > LandscapeLeft > Portrait)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Web] VideoPlayer.frameReady event fires only once in a video when the Player Graphics API is set to WebGPU
- Hierarchy V2 Reset Columns leaves empty space and does not resize to fit when removing the columns
- Unexpected changes are made to the main asset when cloning and adding root objects with AddObjectToAsset in AssetPostprocessor
- [RenderGraph] Outputs from camera stack override each other when using OpenGLES3 with a custom renderer feature
- An "RefreshInternalV2 is called before InitialRefresh" error is thrown when opening a project where a build profile with Player settings added is selected
Resolution Note (fix version 2023.2):
Fixed in: 2023.2.0a13
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.18f1