Search Issue Tracker
Third Party Issue
Votes
0
Found in
2020.3.37f1
2021.3.8f1
2022.1.12f1
2022.2.0b4
2023.1.0a6
Issue ID
UUM-11705
Regression
No
[ChromeOS] Unity app can be autorotated when native autorotation is locked
How to reproduce:
# Open orientations project, which link is in the comments
# When selected platform is Android, make sure that x86 and x86-64 Target Architectures are enabled
# Go to Player Settings -> Resolution and Presentation
# Make sure that Orientation is set to Autorotation and all orientations are enabled
# In Orientations.cs script comment this line Screen.orientation = ScreenOrientation.Portrait; which is called from Start()
# Build and run on Chrome OS device, which is in Tablet mode
# Via device settings Lock the autorotation and try rotating the app
*Actual result:* App rotates to all orientations
*Expected result:* because autorotation is locked natively, Unity app shouldn't rotate to all orientations. Let's say if app has Horizontaly locked orienattions, it should allow LandscapeLeft and LandscapeRight, but not Portrait orienattions.
*Tested and reproduced:*
Google Pixelbook, ChromeOS version: 102.0.5005.75, Android version 11 Build number: R102-14695.85.0
Lenovo Chromebook Duet 2 in 1, ChromeOS version: 103.0.5060.64 (32 bit), Android version 9 Build number: R103-14816.82.0
On Android devices it works as expected
h4.
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
- Crash on RaiseException when terrain detail instancing is excessive
- Prefab variant reference is lost when assigned by click-and-drag in Prefab Editor mode
- Opening any dropdown in Shader Graph stops the Nodes preview but it still plays in the background
- GPU utilization increases when a GameObject is selected
- Motion Blur has sharp edges when object is moving in the foreground of another object
Resolution Note:
This is a third-party issue and I registered this issue on the Google Issue tracker. https://partnerissuetracker.corp.google.com/issues/261899400
After Google's work, we will take a look at it if there is something we need to do.