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
First of all thank you for creating this library! I have the below issue:
When headerLargeTitle is set to true and/or there is a header search bar, the content of the app renders below the header. This is when the SafeAreaView of this library (react-native-safe-area-context) is being used. When I use the component from react-native it self, this issue doesn't occur. I'd still like to use this library to have the ability to disable some insets/edges in some specific cases.
I guess in this library something is missing on the native side, which results in this bug?
The text was updated successfully, but these errors were encountered:
JustJoostNL
changed the title
No insets for when headerLargeTitle/headerSearchBar is enabled, the SafeAreaView does handle this correct but this library not
No insets when headerLargeTitle/headerSearchBar are enabled, the SafeAreaView from react-native does handle this correctly but this library not
Dec 22, 2024
JustJoostNL
changed the title
No insets when headerLargeTitle/headerSearchBar are enabled, the SafeAreaView from react-native does handle this correctly but this library not
Content Overlaps with Header When Using headerLargeTitle/headerSearchBar with SafeAreaView from react-native-safe-area-context
Dec 22, 2024
Hey!
First of all thank you for creating this library! I have the below issue:
When
headerLargeTitle
is set totrue
and/or there is a header search bar, the content of the app renders below the header. This is when the SafeAreaView of this library (react-native-safe-area-context
) is being used. When I use the component fromreact-native
it self, this issue doesn't occur. I'd still like to use this library to have the ability to disable some insets/edges in some specific cases.I guess in this library something is missing on the native side, which results in this bug?
The text was updated successfully, but these errors were encountered: