Screen.safeArea rect not valid in Awake

I am using Screen.safeArea in Awake() to determine the available resolution on the device, but recently it stopped working. Instead of returning a valid rect, the rect's width and height are NaN.

Some information:

• The application has been in use in my company for years.
• I added Screen.safeArea last November.
• The application worked fine this February
• I have a build from late last November, after I added Screen.safeArea, that still works, but the next one, from early January, doesn't
  
• When I go back in our Version Control to when I added Screen.safeArea, it does not work (in the current Version of Unity).
• I have builds dating from early January till now, which all don't work, but I know for a fact that a build I made mid February did work back then

Has there been any changes to Unity and/or the Android API that broke this function? I can use it later and get useful values, but in Awake it returns NaN, which it didn't before.

 

What is current version? LTS? Or are you using 2019.3?

Screen safearea was broken in awake in the past, they then fixed it, but as most Unity issues do, it keeps coming back it seems.

 

Is there an ETA on a fix in 2019.3 or a stable 2020 release?

 

Thank you.

 

Is this fix backported to 2018.4 LTS? I think we also got this issue and we're using 2018.4.23f1 (latest LTS). Is there a workaround? Is reading safe areas outside of awake/start safer?

Currently we are reading it in Start of the first scene and it's causing problems. Should we read it later?

 

We are using 2018.4.23f1 and ran into this issue also. After some time debugging, we found that it seemed to be in some way related to the splash screen scaling setting.
https://docs.unity3d.com/Manual/AndroidMobileCustomizeSplashScreen.html

If either of "Center (only scale down)" or "Scale to fit (letter-boxed)" was used, the safe area rect would have NaN. If we changed to "Scale to fit (Cropped)", the safe area rect appears to be correct.

 

Thanks for the information. I will do some investigation of my own.

But you know what would be nice? If Unity had these things figured out so thousands of indie devs didn’t have to struggle with these issues and workarounds.

 

Hmm, I spoke too soon. After testing a couple other Android devices, it's only resolved on one of them. Back to the drawing board.

 

Hi rjonaitis, do you have a date for when this fix will be merged into 2018 LTS?

 

If that could still be a problem in the future, maybe a note about this in the docs could be prudent?

We now have a solution that calculates the safe areas (we convert the numbers to viewport coords), 1 second after the 1 1st scene loads, and we also check for float.IsNaN (and if that's the case, we inset slightly so we have something that would look reasonable with and without a notch), and it kinda took us a lot of guesswork and time to arrive at this conclusion.

Having something in the docs that it may be safer to read safeAreas a bit later would have insta solved our issues. (and I I mean that even after you fix the issue, because then Android again may change something that yet again makes it unsafe to read these values in Awake/Start, right?)

 

Just a heads up, this is still an issue in 2018.4.24

 

@rjonaitis What about 2019.4, has it been ported there? I can't see a specific item on the 2018.4.25 release notes that addresses this so don't know what to look for in 2019.4 release notes either.

 

I know you were probably writing short hand, but float.isNaN() is how to detect NaN. Comparing anything to float.NaN using == returns false always.

 

You are right, I just edited the original post so I don't spread wrong information.

 

This appears to still be an issue in 2019.4.9f1 LTS. Except, now it returns the full screen size, rather than the safe screen size.

 

This is still happening in 2020.1.12f1, it returns the full screen size

Side question, when can we expect the iphone 12 series to be added to the device generation enum? (also, Device.generation.ToString() still returns "iPhoneUnknown" at the moment).

 

Have you tried reading it a little later (not in awake in the first scene) and see if it returns correct stuff?

 

Still happens in Unity 2021.3.14f1. Safe area is the same as original resolution when called on Awake()

 

Just a little heads up: Unity 2022.3.4f1 LTS brought this back (it wasn't there in previous 2022 versions)

 

Welp, I guess this usually means it will be backported to 2021 soon as well.