Search Issue Tracker
Won't Fix
Votes
1
Found in
2022.3.58f1
6000.0.39f1
6000.1.0b7
6000.2.0a4
Issue ID
UUM-98101
Regression
No
[Android] "Screen.safeArea.y" always returns values outside of the Safe Area when the device is in Portrait orientation
How to reproduce:
1. Open the “ScreenSafeAreaRepro.zip“ project
2. Open the “SampleScene“
3. Build for Android
4. Install the app on a device
5. Clean out the logcat “adb logcat -c“
6. Start the logcat “adb logcat > [Filename].txt.“
7. Open the application
Expected result: The white rectangle leaves a space where the notch is and a logged value of “MYDEBUG Screen.safeArea.y: “ is correct
Actual result: The white rectangle does not leave a space where the notch is and a logged value of “MYDEBUG Screen.safeArea.y: “ is incorrect
Reproducible with: 2022.3.58f1, 6000.0.39f1, 6000.1.0b7, 6000.2.0a4
Reproducible environment: macOS 15.2 (M4 Max), Windows 11 (Reporters)
Not reproducible environment: No other environment tested
Reproducible with these devices:
macOS 15.2 (M4 Max) (Simulator)
VLNQA00375, Samsung Galaxy S21+ 5G (SM-G996U), Android 11, CPU: Snapdragon 888, GPU: Adreno (TM) 660
VLNQA00335, Samsung Galaxy S20+ 5G (SM-G986B), Android 10, CPU: Exynos 990, GPU: Mali-G77
VLNQA00498, Google Pixel 7 (Pixel 7), Android 13, CPU: Google Tensor G2, GPU: Mali-G710
Not reproducible with these devices:
VLNQA00416, iPhone 13 Pro (MLVA3ET/A), CPU: Apple A15 Bionic, GPU: Apple designed, OS: 16.1.1
VLNQA00626, iPhone 16 (MYE73QN/A), CPU: Apple A18 Pro, GPU: Apple designed, OS: 18.0.1
Notes:
- To reproduce need a device with a notch
- Does not reproduce in Landscape orientation, only reproduces in Portrait orientation
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note:
Unfortunately this is due to the inconsistency of the co-ordinate system between platforms and UI elements. You can translate co-ordinates that work best for you (as the workaround suggests), but we cannot change the co-ordinate systems under the hood as this will be a breaking change for all projects that depend on it. We have added a ticket internally to propose a way of unifying the co-ordinate systems via an API.