Search Issue Tracker
Fixed
Votes
0
Found in
2021.3.37f1
Issue ID
UUM-69533
Regression
No
Safe Area incorrect on iPads with virtual home button running iOS 14
How to reproduce:
1. Download and open the attached "NativeSafeArea" project
2. Deploy the Xcode project to iPad with a virtual home button
3. Observe Safe area output in the Xcode console
4. Download and open the "1785086_Safe_Area" project
5. Repeat steps 2-3
Expected outcome: The Safe Area values match
Actual outcome: The Safe Area values differ
Reproducible with: 2021.3.37f1, 2022.3.24f1, 2023.3.0b10, 6000.0.0b15
Reproduced on: iPad Air (4th generation) (iOS 14.6), iPad Air (4th generation) (iOS 15.2.1)
Note: Error is caused by the Unity generated ComputeSafeArea method (lines 246-273) in 1785086_Safe_Area/Build/Classes/UI/UnityView.mm lines. This code assumes status bar height is always 20, but iPads with a virtual home button have a status bar height of 24.
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-51667