Open RBrNx opened 2 years ago
@RBrNx have you tried to change android_keyboardInputMode
to your app android:windowSoftInputMode
? https://gorhom.github.io/react-native-bottom-sheet/props#android_keyboardinputmode
@RBrNx have you tried to change
android_keyboardInputMode
to your appandroid:windowSoftInputMode
? https://gorhom.github.io/react-native-bottom-sheet/props#android_keyboardinputmode
@gorhom I currently have the softwareKeyboardLayoutMode
set to pan
in my Expo app.json which matches the adjustPan
setting of android_keyboardInputMode
in the Snack
okay, i notice that you have the BottomSheetModalProvider
in the BottomSheetModal
, which will pick the wrong container height measurement.
I advice you to move BottomSheetModalProvider
to the root component , to wrap your app
i would consider this issue resolve π
Hey @gorhom, apologies for taking so long to get back to you!
Your suggestion absolutely makes sense, but unfortunately I am still able to replicate the issue. It seems as if the first input works ok, but the further you need to scroll down, the more the issue appears.
https://user-images.githubusercontent.com/1332314/133065110-8b5c8c0a-b04a-4488-9546-f21a2bdefdfa.mp4
I've also updated the Expo Snack I linked previously, which also still showcases the issue on Android
I will check it out later, thanks for the update
Even I am facing same issue when I used BottomSheetModal on ScrollView then I am getting extra paddingBottom appending to the Data so that I is moving above of the mobile screen.I am facing this issue from last 2 months but I thought it is my mistake and today I checked all the scenarios in my programming but I didn't find out any resolves in my code. So could you please suggest any solution for the problem I am facing?
@RBrNx i couldn't reproduce the issue on provided snack , could you please verify it, thanks
Hihi @gorhom ! Thanks for this amazing library.
I'm also experiencing the same issue. In my case I want to replicate tiktok's comments in which the textinput is always floating at the bottom. That's why I thought I could use the footerComponent prop to render a TextInput... but I'm getting the exact same behavior as the above comments describe .
EDIT: upon further debugging, it has nothing to do with where the TextInput is located. Also it doesn't matter if it's in the fotterComponent prop or not. It seems that the issue is the keyboard opening
Same issue here. Works great on ios, only happens on Android. ScrollView gets smaller when keyboard is open. The white space is equal to the keyboard size.
@mikealche @KingDoxik could you provide reproducible snacks i can investigate the issue on ? thanks
I was having the same problem. Fixed by removing this logic:
diff --git a/node_modules/@gorhom/bottom-sheet/src/components/bottomSheet/BottomSheet.tsx b/node_modules/@gorhom/bottom-sheet/src/components/bottomSheet/BottomSheet.tsx
index 3606001..faf6e76 100644
--- a/node_modules/@gorhom/bottom-sheet/src/components/bottomSheet/BottomSheet.tsx
+++ b/node_modules/@gorhom/bottom-sheet/src/components/bottomSheet/BottomSheet.tsx
@@ -304,10 +304,7 @@ const BottomSheetComponent = forwardRef<BottomSheet, BottomSheetProps>(
}
return $modal
- ? Math.abs(
- animatedKeyboardHeight.value -
- Math.abs(bottomInset - animatedContainerOffset.value.bottom)
- )
+ ? Math.abs(bottomInset - animatedContainerOffset.value.bottom)
: Math.abs(
animatedKeyboardHeight.value - animatedContainerOffset.value.bottom
);
Not sure if this will impact other parts of the package, still testing.
Hey guys,
Same happens for us.
Same issue for me, there is a random padding, is there any solution?
it worked for me when i changed KeyboardBehavior prop to "extend"
I have a similar issue on Android. I'm currently running the Example App and the list has 11 items that can be scrolled. However, it only shows 10 items when the keyboard is open:
https://user-images.githubusercontent.com/9752658/146922802-4615e0e8-147b-48b5-9068-25e3145019ed.mov
I actually got it working by setting keyboardBehavior="extend"
<RNBottomSheet
ref={ref}
snapPoints={animatedSnapPoints}
handleHeight={animatedHandleHeight}
contentHeight={animatedContentHeight}
animateOnMount={false}
onClose={onClose}
backdropComponent={renderBackdrop}
backgroundStyle={styles.backgroundStyle}
handleIndicatorStyle={styles.handleIndicator}
enablePanDownToClose
keyboardBehavior="extend"
keyboardBlurBehavior="restore"
>
Hello all, i kanda have a similar problem. It seams that keyboardBehavior isn't working correctly - at least for me. I have two snap points (aprox. 25% and 50%). My BottomSheetTextInput is within the 25% but as soon as tapping the TextInput in order to type something it straight goes to 50%. Although its the default I also did set keyboardBehavior="interactive".
Working on an iOS App - haven't tested it on Android at all.
I manage to resolve it by providing the correct android_keyboardInputMode
For the people who happen to stumble upon this thread: what worked for me was setting android:windowSoftInputMode
to adjustPan
in the AndroidManifest.xml
@gorhom many people including me seem to still encounter this problem of extra padding (around 32 pixels), any idea what could be causing it? It happens on both platforms and I already set keyboard window resize to adjustPan
.
Still happening. Has anyone found a solution?
π I'm facing the same problem on Android, I'm using the bottom sheet in version 4 and when focusing on my input, a very large padding is added just below the input and everything ends up being white.
π I'm facing the same problem on Android, I'm using the bottom sheet in version 4 and when focusing on my input, a very large padding is added just below the input and everything ends up being white.
I am using the same version 4, and facing same issue in Android. Have you somehow managed to make it work?
For the people who happen to stumble upon this thread: what worked for me was setting android:windowSoftInputMode to adjustPan in the AndroidManifest.xml
@InfiniteRain according to Android docs adjustResize
is preferable, so this is not the final solution. I think it works as a workaround but could potentially have side effects in UX depending on your use case of keyboard, adjustPan
might overlap the view with the keyboard.
I was having the same problem. Fixed by removing this logic:
diff --git a/node_modules/@gorhom/bottom-sheet/src/components/bottomSheet/BottomSheet.tsx b/node_modules/@gorhom/bottom-sheet/src/components/bottomSheet/BottomSheet.tsx index 3606001..faf6e76 100644 --- a/node_modules/@gorhom/bottom-sheet/src/components/bottomSheet/BottomSheet.tsx +++ b/node_modules/@gorhom/bottom-sheet/src/components/bottomSheet/BottomSheet.tsx @@ -304,10 +304,7 @@ const BottomSheetComponent = forwardRef<BottomSheet, BottomSheetProps>( } return $modal - ? Math.abs( - animatedKeyboardHeight.value - - Math.abs(bottomInset - animatedContainerOffset.value.bottom) - ) + ? Math.abs(bottomInset - animatedContainerOffset.value.bottom) : Math.abs( animatedKeyboardHeight.value - animatedContainerOffset.value.bottom );
Not sure if this will impact other parts of the package, still testing.
Having success with this so far.
this works well for android, but in my case ios stops working, so the following code works correctly for me: ` animatedKeyboardHeightInContainer.value = $modal
Adding android_keyboardInputMode='adjustResize'
property worked for me
I also added:
keyboardBehavior='interactive'
keyboardBlurBehavior='restore'
We're also having this issue. Our team opened https://github.com/gorhom/react-native-bottom-sheet/issues/1195 to try and document before we saw this. We were able to fix on our end by doing two things:
BottomSheetScrollView
android_keyboardInputMode='adjustResize'
i have tricky solution for this,
my problem was i had absolute view as my footer inside BottomSheetModal, and i had problem with adjustResize and adjustPan. if i set adjustResize the bottomsheet will going up like there is big margin with the keyboard. if i set adjustPan there will be a problem for smartphone with large screen only, the bottomsheet will sink to the back of the keyboard
adjustResize | adjustPan |
---|---|
![]() |
![]() |
my bottomsheet component FilterBottomSheet.js like this
<View key={index} style={{ flex: 1 }}>
< style={styles.filterBottomSheetContent}>
<View style={styles.filterSelectRadio}>
<FilterData data={filterFormTemp} />
</View>
</ScrollView>
<View style={styles.filterBottomSheetFooter}> // THIS IS ABSOLUTE VIEW AS FOOTER
<Button
style={[styles.filterBottomSheetButton, styles.filterBottomSheetReset]}
onPress={() => _onPressFilter(name, 'reset')}
>
<OpenSansSemiBold style={styles.filterBottomSheetButtonText}>Reset</OpenSansSemiBold>
</Button>
<Button
style={[styles.filterBottomSheetButton, styles.filterBottomSheetSimpan]}
onPress={() => _onPressFilter(name, 'simpan', filterFormTemp)}
>
<OpenSansSemiBold style={[styles.filterBottomSheetButtonText, { color: Colors.colorLevel1 }]}>Simpan</OpenSansSemiBold>
</Button>
</View>
</View>
i tried using BottomSheetView in my absolute View but the problem still occured. i tried BottomSheetScrollView as my ScrollView but the problem still occured, and other issue occured that it cannot be scrolled. (for this issue im using ScrollView from react-native-gesture-handler) i cannot used BottomSheetFooter because it's in diffferent component from the parent BottomSheetModal
i tried everything from event focus input, keyboard listener in the component, all make the keyboard dismissed because it would rerender the component.
finally i solved this with created a keyboard listener in the parent that contain BottomSheetModal like this:
useEffect(() => {
let unmounted = false; // FLAG TO CHECK COMPONENT UNMOUNT
// BUG FIXED BOTTOMSHEET FOR ABSOLUTE VIEW WHEN KEYBOARD SHOW
const showSubscription = Keyboard.addListener("keyboardDidShow", () => {
setKeyboardBottomInset(0.1);
});
const hideSubscription = Keyboard.addListener("keyboardDidHide", () => {
setKeyboardBottomInset(0);
});
if (!unmounted) {
...
}
// CLEAR FUNCTION COMPONENT UNMOUNT
return () => {
unmounted = true;
showSubscription.remove();
hideSubscription.remove();
}
}, []);
<BottomSheetModal
key="filterHarga"
ref={bottomSheetHargaRef}
index={0}
snapPoints={snapPoints}
onChange={(index) => _filterChange("price", index)}
backdropComponent={renderBackdrop}
keyboardBehavior="fillParent"
keyboardBlurBehavior="restore"
bottomInset={keyboardBottomInset}
>
please look setKeyboardBottomInset(0.1) and bottomInset={keyboardBottomInset} setKeyboardBottomInset(0.1) in the keyboardDidShow event listener would tricked the keyboard event to change the value bottomInset={keyboardBottomInset}
hope it helps!
My issue was eliminating lingering space created by the keyboard - keyboardBlurBehavior="restore"
did the trick for me
Did you find a solution?
This is still a problem. It's also happening on IOS now. I could not get this fixed so I changed from a bottom sheet to navigating to a different screen. In my case it seems to be linked to the react navigation material bottoms tabs library. The bottom padding is the same pixel height as the bottom tabs.
I was having the same problem. Fixed by removing this logic:
diff --git a/node_modules/@gorhom/bottom-sheet/src/components/bottomSheet/BottomSheet.tsx b/node_modules/@gorhom/bottom-sheet/src/components/bottomSheet/BottomSheet.tsx index 3606001..faf6e76 100644 --- a/node_modules/@gorhom/bottom-sheet/src/components/bottomSheet/BottomSheet.tsx +++ b/node_modules/@gorhom/bottom-sheet/src/components/bottomSheet/BottomSheet.tsx @@ -304,10 +304,7 @@ const BottomSheetComponent = forwardRef<BottomSheet, BottomSheetProps>( } return $modal - ? Math.abs( - animatedKeyboardHeight.value - - Math.abs(bottomInset - animatedContainerOffset.value.bottom) - ) + ? Math.abs(bottomInset - animatedContainerOffset.value.bottom) : Math.abs( animatedKeyboardHeight.value - animatedContainerOffset.value.bottom );
Not sure if this will impact other parts of the package, still testing.
A more accurate code will be this:
diff --git a/node_modules/@gorhom/bottom-sheet/src/components/bottomSheet/BottomSheet.tsx b/node_modules/@gorhom/bottom-sheet/src/components/bottomSheet/BottomSheet.tsx
index b166440..ff40823 100644
--- a/node_modules/@gorhom/bottom-sheet/src/components/bottomSheet/BottomSheet.tsx
+++ b/node_modules/@gorhom/bottom-sheet/src/components/bottomSheet/BottomSheet.tsx
@@ -1366,9 +1365,11 @@ const BottomSheetComponent = forwardRef<BottomSheet, BottomSheetProps>(
*/
animatedKeyboardHeightInContainer.value = $modal
? Math.abs(
- _keyboardHeight -
- Math.abs(bottomInset - animatedContainerOffset.value.bottom)
- )
+ Platform.OS === 'android' &&
+ android_keyboardInputMode === KEYBOARD_INPUT_MODE.adjustResize ?
+ 0 : _keyboardHeight
+ - Math.abs(bottomInset - animatedContainerOffset.value.bottom)
+ )
: Math.abs(_keyboardHeight - animatedContainerOffset.value.bottom);
const hasActiveGesture =
Since adjustResize will automatically adjust the screen size in android, there is no need to add the _keyboardHeight in the calculation.
I find a solution in this post.
Wich solution is the best to adress the issue? Should i use the StackOverflow solution or rather use the fix in the package?
Wich solution is the best to adress the issue? Should i use the StackOverflow solution or rather use the fix in the package?
I used the StackOverflow link and worked like a charm
I find a solution in this post.
I sadly can't use this, because its not working when switching from "portrait" to "landscape" mode.
I was having the same problem. Fixed by removing this logic:
diff --git a/node_modules/@gorhom/bottom-sheet/src/components/bottomSheet/BottomSheet.tsx b/node_modules/@gorhom/bottom-sheet/src/components/bottomSheet/BottomSheet.tsx index 3606001..faf6e76 100644 --- a/node_modules/@gorhom/bottom-sheet/src/components/bottomSheet/BottomSheet.tsx +++ b/node_modules/@gorhom/bottom-sheet/src/components/bottomSheet/BottomSheet.tsx @@ -304,10 +304,7 @@ const BottomSheetComponent = forwardRef<BottomSheet, BottomSheetProps>( } return $modal - ? Math.abs( - animatedKeyboardHeight.value - - Math.abs(bottomInset - animatedContainerOffset.value.bottom) - ) + ? Math.abs(bottomInset - animatedContainerOffset.value.bottom) : Math.abs( animatedKeyboardHeight.value - animatedContainerOffset.value.bottom );
Not sure if this will impact other parts of the package, still testing.
A more accurate code will be this:
diff --git a/node_modules/@gorhom/bottom-sheet/src/components/bottomSheet/BottomSheet.tsx b/node_modules/@gorhom/bottom-sheet/src/components/bottomSheet/BottomSheet.tsx index b166440..ff40823 100644 --- a/node_modules/@gorhom/bottom-sheet/src/components/bottomSheet/BottomSheet.tsx +++ b/node_modules/@gorhom/bottom-sheet/src/components/bottomSheet/BottomSheet.tsx @@ -1366,9 +1365,11 @@ const BottomSheetComponent = forwardRef<BottomSheet, BottomSheetProps>( */ animatedKeyboardHeightInContainer.value = $modal ? Math.abs( - _keyboardHeight - - Math.abs(bottomInset - animatedContainerOffset.value.bottom) - ) + Platform.OS === 'android' && + android_keyboardInputMode === KEYBOARD_INPUT_MODE.adjustResize ? + 0 : _keyboardHeight + - Math.abs(bottomInset - animatedContainerOffset.value.bottom) + ) : Math.abs(_keyboardHeight - animatedContainerOffset.value.bottom); const hasActiveGesture =
Since adjustResize will automatically adjust the screen size in android, there is no need to add the _keyboardHeight in the calculation.
This worked like a charm. Thank you.
For anyone wondering, this is using patch-package
and creating a patch of the source code.
android_keyboardInputMode="adjustResize"
add the above, and padding issure resolved
android_keyboardInputMode="adjustResize"
worked for meπ
Adding android_keyboardInputMode="adjustResize"
to BottomSheet or ModalBottomSheet components worked for me too.π
I was having the same problem. Fixed by removing this logic:
diff --git a/node_modules/@gorhom/bottom-sheet/src/components/bottomSheet/BottomSheet.tsx b/node_modules/@gorhom/bottom-sheet/src/components/bottomSheet/BottomSheet.tsx index 3606001..faf6e76 100644 --- a/node_modules/@gorhom/bottom-sheet/src/components/bottomSheet/BottomSheet.tsx +++ b/node_modules/@gorhom/bottom-sheet/src/components/bottomSheet/BottomSheet.tsx @@ -304,10 +304,7 @@ const BottomSheetComponent = forwardRef<BottomSheet, BottomSheetProps>( } return $modal - ? Math.abs( - animatedKeyboardHeight.value - - Math.abs(bottomInset - animatedContainerOffset.value.bottom) - ) + ? Math.abs(bottomInset - animatedContainerOffset.value.bottom) : Math.abs( animatedKeyboardHeight.value - animatedContainerOffset.value.bottom );
Not sure if this will impact other parts of the package, still testing.
A more accurate code will be this:
diff --git a/node_modules/@gorhom/bottom-sheet/src/components/bottomSheet/BottomSheet.tsx b/node_modules/@gorhom/bottom-sheet/src/components/bottomSheet/BottomSheet.tsx index b166440..ff40823 100644 --- a/node_modules/@gorhom/bottom-sheet/src/components/bottomSheet/BottomSheet.tsx +++ b/node_modules/@gorhom/bottom-sheet/src/components/bottomSheet/BottomSheet.tsx @@ -1366,9 +1365,11 @@ const BottomSheetComponent = forwardRef<BottomSheet, BottomSheetProps>( */ animatedKeyboardHeightInContainer.value = $modal ? Math.abs( - _keyboardHeight - - Math.abs(bottomInset - animatedContainerOffset.value.bottom) - ) + Platform.OS === 'android' && + android_keyboardInputMode === KEYBOARD_INPUT_MODE.adjustResize ? + 0 : _keyboardHeight + - Math.abs(bottomInset - animatedContainerOffset.value.bottom) + ) : Math.abs(_keyboardHeight - animatedContainerOffset.value.bottom); const hasActiveGesture =
Since adjustResize will automatically adjust the screen size in android, there is no need to add the _keyboardHeight in the calculation.
This solves the issue on Android but the issue persists on iOS.
If you don't use the bottomInset I did something like this to resolve the problem on iOS:
bottomInset={isKeyboardVisible ? -0.2 : 0}
-0.1 not working, -0.2 is the first low value working.
Bug
Using a combination of
BottomSheetModal
,BottomSheetScrollView
andBottomSheetTextInput
withkeyboardBehavior
set tointeractive
will result in extra padding/margin appearing when the keyboard is visible - this only applies to Android, on iOS it seems to work as expected.Environment info
Steps To Reproduce
BottomSheetModal
component that renders aBottomSheetScrollView
and a small number ofBottomSheetTextInputs
Describe what you expected to happen:
Reproducible sample code
Below is a Snack containing a reproducible sample https://snack.expo.dev/@conorw/v4-bottomsheetscrollview-keyboard-padding-issue
and here are two videos showcasing the issue, one using the above Snack, and the other in my own Production app
https://user-images.githubusercontent.com/1332314/131832648-a60148cc-2c99-4207-9248-83139fd48b70.mp4
https://user-images.githubusercontent.com/1332314/131833763-bc0114ca-eed5-42bf-b01b-840731347f78.mp4