Search Issue Tracker
Not Reproducible
Fixed in 2018.4.X
Votes
0
Found in
2018.4.8f1
2018.4.22f1
Issue ID
1246822
Regression
Yes
[2018.4][Android]Screen.currentResolution is incorrect when calling Screen.SetResolution() and changing the phone orientation
Steps to reproduce:
1. Open user-supplied project
2. Build and run
3. Press "Portrait", "1080X1920", "LandscapeLeft"
Expected: the "currentResolution.width:" shows "1920", the "currentResolution.Height:" shows "1080"
Actual: it's the other way around
Reproduced in: 2018.4.8f1, 2018.4.23f1,
Not reproduced in: 2018.4.7f1, 2019.3.14f1, 2020.1.0b9, 2020.2.0a11
Repro on:
VLNQA00277, Asus ROG Phone (ASUS_Z01QD), Android 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00121, Samsung Galaxy S9 (SM-G960F), Android 9, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00021, Samsung Galaxy S7 (SM-G930F), Android 8.0.0, CPU: Exynos 8 Octa 8890, GPU: Mali-T880
VLNQA00288, Samsung Galaxy J7 (SM-J730F), Android 8.1.0, CPU: Exynos 7 Octa 7870, GPU: Mali-T830
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment