Screen.safeArea not correct for Pixel 4, Unity 2018.4

Unity 2018.4.23, Screen.safeArea is returning a zero offset, but the phone has rounded corners. Tested this in an update loop, so it's not an Awake/Start issue.

Are there known problems with Screen.safeArea and Android in 2018.4?

Note: Pixel 4 runs Android 10.

 

Tested with latest 2018.4 available (2018.3.26f1) and same results. Safe area is the full screen.

 

In case API level is a factor:

Minimum API level is 19, Target API level is highest available (which is shown as level 28).

Are other people using Screen.safearea OK on Android? Maybe it's just best to assume a worst case, and move all UI away from the edges.

 

Bump... anyone out there using Screen.safearea successfully on Android for 2018.8.4?

 

Is this the wrong forum to ask this question?

 

Someone will find this thread in 2025 and wish someone had followed up.

 

It's not 2025, but I do wish someone responded to this. Have the same issue. Did you ever find a solution? I am on 2019.4.4

 

I was never able to find a way to get a non-zero safe area. The work-around was to just assume a worst-case safe area, which really sucks.

 

That's unfortunate. I tried 2020x, 2019x, SDK 28. Doesnt work on Android, fine on iOS

 

2019.4.23LTS in android. Same Problem. Safe area is the full screen, and Screen.Cutouts is empty.

 

Experiencing the same issue - anyone have a fix for this? Without a way to detect rounded corners, UI elements in my game end up getting cut off.

 

Is it a Unity issue or is the phone not reporting any safe areas? If it's the latter, there isn't much Unity can do.

 

Using the device simulator, the iPhone X has a correct safe area like this:

On the other hand, the Pixel 4's safe area goes outside of the corners:

This is strange because the device simulator clearly recognizes that the Pixel 4 has rounded corners, yet the safe area ignores them.

 

The safe areas are something that the phone itself reports, there are iOS APIs and Android APIs that Unity then takes and maps to Screen.safeArea.

If the phone itself doesn't report any insets / safe areas, then there's not much for Unity to do.

 

If this is the case, I'm wondering how other developers handle this? Especially if phones as prominent as the Google Pixel don't report this.

 

Never place anything too close to the corners?



But if you really wanted to, you could have code that detects the pixel phone and override safeArea with your own values.

But it generally seems like all Androids don't really inset because of rounded corners.

Even Apple don't think does it because of rounded corners, they just do it so there's symmetry. (I'm fairly sure if they got rid of the notch but kept the rounded corners, the safeArea would be full screen).

 

Well the point is I'd like the UI to be consistent between Android and iOS. If a button is pushed away from the screen edge on iOS due to a rounded corner, it would look strange to have that same button against the edge on Android.

I am aware that Screen.safeArea is reported by the device and that Android handles corners differently; regardless, Android also has an additional RoundedCorner API that I want to access in Unity to compute my own custom safe area. So the question is, how to access it in Unity?

 

It’s not due to a rounded corner, Apple did it this way to keep it symmetrical, which you could do by calculated the side offsets and applying the highest one for both sides.

Also about the rounded corners API is something you could probably write a plugin for. Don’t expect Unity to do it for you.

 

That's definitely not true. If you go to the safe area visualizer for the iPhone X, you'll see that the border is significantly larger than the notch in order to fully exclude the rounded corners:

The safe area shape exactly matches the rounded corners. If it was only to match the notch size, you'd expect the safe area to partially cut into the rounded corners.

As a matter of fact, if you simulate the iPad Pro 11, which doesn't have any notches but does have rounded corners, you'll see that the safe area cuts out the corners:

This same cut does not happen on the iPad Pro 10, which has all regular corners.

For an issue so common that someone started an entire thread about it with multiple people commenting wondering why the corners aren't considered, I'd want to at least make sure that Unity didn't already implement it before going out of my way to write a plugin. If I have to write a plugin, I'll do it, but it seems strange that a common issue doesn't have any built-in support.

 

Welcome to Unity.

 

I’m pretty sure that is not space for the rounded corners, just for the virtual home button. (Otherwise why is there no safe area on the top side as well?)

(also has a physical button, so no need to leave space for the virtual home button)

 

Safe area really is bugged for these devices.
The problem is also dependent on the System Navigation on the device.

If you use 3-button navigation, the safe area is wrong.

If you use Gesture navigation the safe area is correct.

 

Are you talking on an actual device, or Unity's device simulator?

 

I was using a emulator from android Studio.

But I was wrong, when you set the navigation to gesture navigation, it appears the OS itself cuts the app area.
With the 3 button it doesn't, but the safearea value is returned correctly (it was my app that was wrong, a piece of canvas was missing the safe area script). Sorry about that, it was my mistake.

Weird though that android cuts the app area when set to gesture navigation, it's either android or unity doing this automatically, the game gets a black bar under the camera.