Search Issue Tracker
By Design
Votes
0
Found in
2022.3.11f1
2023.3.0a14
Issue ID
UUM-56433
Regression
No
[iOS] Screen.safeArea isn't right for devices with Dynamic Island when in Portrait orientation
Steps to reproduce:
- Open attached project (test-cutouts.zip)
- Switch to iOS and make a build
- Deploy to a device with Dynamic Island (iPhone 14 Pro/ProMax or any iPhone 15 device, simulators work too)
- Make sure the device is in Portrait orientation
Expected result: Screen.safeArea should return the safe area of the device, grey rectangle is drawn on screen to show the safeArea on device. Rectangle shouldn't overlap with the notch/dynamic island.
Actual result: safeArea slightly overlaps with the notch/dynamic island.
!image-2023-11-16-13-48-48-923.png|width=425,height=253!
Note: landscape orientation seems to work fine and the safeArea rect is drawn correctly without overlapping.
Reproduced with: 2022.3.11f1, 2023.3.0a14
Tested with:
iPhone 15 Pro, iOS 17.0.2 - Reproduced
iPhone 14 Pro, iOS 16 - Reproduced
iPhone 13 Pro Max - Not reproduced
iPhone 12 Pro - Not reproduced
Comments (1)
-
monark
Jan 13, 2025 14:22
Would be really nice if this was documented in the API documentation instead of having to find out by trial and error
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
IMGUI coordinate system is top-left, screen coordinate system is bottom-left, which caused the confusion. SafeArea is indeed correctly calculated.