Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Submission thread : notch information as returned by Unity's API research

See original GitHub issue

I want to conduct a research what would Unity returns for Screen.safeArea (new in 2019.1) and Screen.cutouts (new in 2019.2). I have made an APK from Unity 2019.2 alpha that returns those information. Help appreciated!

Download the APK in the release page.
Then install on your Android with file manager or adb install -r (r = replace).
After it runs, rotate the device to both portrait and landscape and take 2 screenshots to remember information of landscape and portrait safe area & others as reported by Unity.
Paste those screenshots here! Thank you!

The experiment’s data will be used to make a new UI component in the future which could avoid the actual notch rectangle, not just pad according to the safe area like SafeAreaPadding.

Issue Analytics

State:
Created 5 years ago
Comments:13 (10 by maintainers)

Top GitHub Comments

4reactions

rjonaitiscommented, Feb 25, 2019

The cutout’s Y coordinate update and initialization until first orientation change has been fixed in Unity 2019.2.0a7

2reactions

AAulicinocommented, Feb 21, 2019

These are from my OnePlus 6t:

vertical_correct

horizontal

After coming back from landscape, my portrait breaks and displays the orange area on the right:

vertical

There is also this annoying issue that android’s getSafeInsetBottom() doesn’t consider the bottom rounded corners. Which ends up cropping the corners of the image.

croppedborders