Search Issue Tracker

Won't Fix

Votes

0

Found in

2020.3.37f1

2021.3.8f1

2022.1.12f1

2022.2.0b4

2023.1.0a6

2023.2.0a1

Issue ID

UUM-11704

Regression

No

[ChromeOS] When allowed orientation or forced orientation is set to Portrait and set to fullscreen, app opens in a phone-sized screen on Android 9 Chrome Os devices

--

-

How to reproduce:
# Open orientations project, which link is in the comments
# When selected platform is Android, go to Player Settings -> Resolution and Presentation
# Make sure that Fullscreen Mode is set to Fullscreen Window, resizable Window is enabled
# Change Orientation to Autorotation and allow only Portrait. 
# 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 Laptop mode

*Actual result:* App starts in phone sized window

*Expected result:* App Starts in LandscapeLeft fullscreen (because we allow autorotation to Portrait, but laptop mode needs to force to LansdcapeLeft.)

*Note:* Same result is when user has all orientations enabled in Autorotation, but then changes it to default orientation Portrait. In the script Orientations.cs on Start() one needs to add Screen.orientation = ScreenOrientation.AutoRotation;

 

*Tested and reproduced:*

HP Chromebook 14a G5, ChromeOS version: 102.0.5005.75 (64 bit), Android version 9 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

*Tested and didn't reproduce:*

Google Pixelbook, ChromeOS version: 102.0.5005.75, Android version 11 Build number: R102-14695.85.0 <- *On this device on the most marked versions app opens Fullscreen as a Portrait, but reports Landscape. On Unity 2022.2.0b4 and 2023.1.0a6 when app is set to autorotate it always opens also as phone-sized window. Bug doesn't reproduce only after latest Chrome OS orientation bugfix PR and app opens as Landscape and reports Landscape Left.*

  1. Resolution Note:

    Thank you for your bug report.

    After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix". This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.

    The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.