You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My main app screen, let's call it screen A, has a view that renders a SafeAreaView. I have some ui calculationst that depends on the size of that view. The issue is that when a user is being deep linked into the app into another screen, let's call it screen B, then the SafeAreaView on screen A has incorrect, value of 0, safe area insets and only get correct when the user swipes back to screen A, but then my calculations are wrong.
However the useSafeAreaInsets return the correct result
My main app screen, let's call it screen A, has a view that renders a SafeAreaView. I have some ui calculationst that depends on the size of that view. The issue is that when a user is being deep linked into the app into another screen, let's call it screen B, then the SafeAreaView on screen A has incorrect, value of 0, safe area insets and only get correct when the user swipes back to screen A, but then my calculations are wrong.
However the
useSafeAreaInsets
return the correct resultIn this example I am focusing on the top inset
Here is a sample app:
And here is a recording of how it goes:
Screen.Recording.2024-08-13.at.12.51.19.PM.mov
Repo: https://github.com/itsramiel/safe-area-wrong-inset
The text was updated successfully, but these errors were encountered: