Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2020.3.X, 2021.1.X, 2021.2.X
Votes
1
Found in
2020.1.0a2
2020.3.4f1
Issue ID
1330535
Regression
Yes
[Android] Switching to Portrait from Landscape by script doesn't work when device is in landscape
Repro steps:
1. Open the attached project "Unity Screen Orientation Android"
2. Build and Run on Android
3. After the app launches rotate the device to landscape
4. Press "Button Portrait 2" on the screen
Expected: Orientation switches to portrait
Actual: Orientation stays in landscape
Reproducible with: 2020.1.0a2, 2020.3.7f1, 2021.1.6f1, 2021.2.0a17
Not reproducible with: 019.4.24f1, 2020.1.0a1
Tested and reproduced on these devices:
N/A, Google Pixel 3 XL (Pixel 3 XL), Android 11, CPU: NOT FOUND, GPU: Adreno (TM) 630
N/A, Huawei - (NOH-NX9), Android 10, CPU: NOT FOUND, GPU: Mali-G78
VLNQA00001, Google Pixel 2 (Pixel 2), Android 11, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00316, Samsung Galaxy Note10 (SM-N970F), Android 9, CPU: Exynos 9 Series 9825, GPU: Mali-G76
Doesn't reproduce on
iPhone 11 (iOS 13.5)
Notes:
- Couldn't test 2018.4
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (fix version 2021.1):
Fixed in 2021.1.17f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.16f1