Search Issue Tracker
Fixed
Fixed in 2021.3.28f1, 2022.2.18f1, 2023.1.2f1, 2023.2.0a13
Votes
0
Found in
2021.3.27f1
2022.2.17f1
2023.1.1f1
2023.2.0a12
Issue ID
UUM-41455
Regression
No
[iOS] Cutouts area is reported incorrectly on iPhones with a cutout/notch
How to reproduce:
1. Build And Run the user’s attached “Safe Area.zip” project on an iOS device that has a cutout/notch
2. Change the orientation of the device repeatedly
3. Observe the blue area
Expected result: Cutout area is not in the blue area
Actual result: Cutout area is in the blue area
Reproducible with: 2021.3.27f1, 2022.2.17f1, 2023.1.1f1, 2023.2.0a12
Not reproducible with: 2021.3.28f1, 2022.2.21f1, 2022.3.4f1, 2023.1.3f1, 2023.2.0a21
Fixed in: 2021.3.28f1, 2022.2.18f1, 2023.1.2f1, 2023.2.0a13
Reproduced on:
VLNQA00494 - iPhone 14 Pro Max, 16.3.1 iOS
VLNQA00358 - iPhone 12, 14.1 iOS
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
- Usage of Adaptive Probe Volumes throws a lot of IndexOutOfRangeException and Assertion Failed errors
- Prefab overrides don't recover missing managed references
- Trail Renderer visual doesn't match the positions of vertices when they have been offset
- [Mobile] The Material is not visible when using the Decal Renderer Feature
- Uncaught TypeError: Cannot read properties of undefined is thrown when the tab is inactive for several minutes
Resolution Note (fix version 2023.2.0a13):
Fixed in: 2023.2.0a13
Resolution Note (fix version 2023.1.2f1):
Fixed in: 2023.1.2f1
Resolution Note (fix version 2022.2.18f1):
Fixed in: 2022.2.18f1
Resolution Note (fix version 2021.3.28f1):
Fixed in: 2021.3.28f1