react-native-safe-area-context icon indicating copy to clipboard operation
react-native-safe-area-context copied to clipboard

Bottom inset on samsung galaxy S23 Ultra (physical device) is 0

Open brilliantinsane opened this issue 1 year ago • 7 comments

const insets = useSafeAreaInsets();
console.log('insets ????', insets);
result --> insets ???? {"bottom": 0, "left": 0, "right": 0, "top": 28.571428298950195}

Above log is from Samsung Galaxy S23 Ultra physical device using ExpoGo

package.json --> "react-native-safe-area-context": "4.6.3"

On iOS everything is fine and good, I am getting insets like normal, but on the S23 Ultra (physical device), the bottom inset is 0, also on the simulator Pixel 6 Pro API 33. What am I doing wrong here? Why is it 0?

I see that most of the issues about insets being 0 are related to the top inset and that the problem is usually caused somehow by <StatusBar /> but here I don't have this problem, my problem is with the system's bottom navigation where that "handle" is.

Any suggestions?

brilliantinsane avatar Jan 19 '24 12:01 brilliantinsane

Same for our app on samsung devices. We're using FLAG_LAYOUT_NO_LIMITS, so it is vital to receive correct insets.

We had to use a whole separate module to determine bottom inset. Which is, essentially a navigation bar. That is one way to solve it. The module is react-native-android-navbar-height

Orange9000 avatar Feb 14 '24 07:02 Orange9000

Hello! Having the same issue.

Not sure if helps but I am using

"react-native-safe-area-context": "^4.9.0"

and on the activity manifest files

android:windowSoftInputMode="adjustPan"

agusvazquez avatar Mar 14 '24 14:03 agusvazquez

There’s definitely some configuration that we’re missing the documentation for here. If you fancy taking a stab at documenting, PRs are happily accepted

jacobp100 avatar Mar 16 '24 14:03 jacobp100