Search Issue Tracker
Fixed in 2.2.4 - preview
Votes
0
Found in [Package]
2.2.2 - preview
Issue ID
1253362
Regression
No
Screen.SafeArea returns different values with the same device when maximizing and unmaximizing the Device Simulator window
How to reproduce:
1. Open the attached project (case-1253362.zip)
2. Open the Device Simulator window (Window -> General -> Device Simulator)
3. Enter the Play Mode to start printing Screen.safeArea results in the Console window
4. Select Apple iPhone XS device
5. Maximize the Device Simulator window
6. Unmaximize the Device Simulator window
Expected result: the same Screen.safeArea value gets printed to the Console as it was before maximizing the window
Actual result: a different Screen.safeArea value gets printed (height gets set to its maximum resolution while width does not change)
Reproducible with: 1.0.0-prevew (2019.4.0f1), 2.2.2-preview (2019.4.0f1, 2020.1.0b11, 2020.2.0a14)
Could not test with: 2018.4.23f1 (package compatible with 2019.3 and above)
Notes:
The issue doesn't occur with all devices. Issue found in: Apple iPhone XS, Xiaomi Redmi Note 7, Motorola Moto G7 Power, OnePlus 6T, Apple iPad Pro 11
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 ScheduleGenerateTilingShape when modifying PolygonCollider2D path count and setting path vertices
- Crash when a scene is created with LocalPhysicsMode::Physics3D
- [HDRP] Light doesn't bounce off terrains
- Unity Hub opens instead of the Unity Editor when launching a project from a Windows command line if a backslash is added to the end of the project path
- "ParseErrorException" is thrown when parsing a float with a very small value from JSON
hzn403
Mar 15, 2023 15:16
This problem is reproduced in 3.0.3-preview and 3.1.0-preview.