React-native-reanimated-bottom-sheet: Keyboard push BottomSheet to top (TextInput)

[mleister97]

Hey,

First, thank you! The Bottomsheet is really cool and I really like it.
I created 2 TextInputs inside the Bottomsheet. When I open the Keyboard the BottomSheet is pushed to the top. Any ideas how I can fix this? I couldn't find any solution and already tried wrapping with Scrollview / KeyBoardAvoidingView

Bottomsheet with Inputs:

When pressing inside a TextInput:

Thank you so much for your help!

[oferRounds]

Hey @mleister97 did you find any solution to this? Seeing it as well

[mleister97]

@oferRounds Unfortunately not.
There are many solutions like wrapping it with a KeyboardAvoidingView, replacing all flex:1 with height:100%, or using android:windowSoftInputMode="adjustPan" in Androidmanifest.xml.

As I am using expo and I cannot escape, the last solution is not an option for me. Also @ljmocic mentioned, that just resnapping should also work.
Sadly non of the solutions work for me. I would still be very happy if someone can provida an example.

You can also have a look at this one: #203
Please notify me when you found a working solution!

[oferRounds]

@mleister97 thank you for this detailed answer! I’ll have a look on the other issue, and will keep you posted if find any solution! Thank you again!

[karimcambridge]

Duplicate of #203

[mleister97]

You are right, but have you found any solution?

[karimcambridge]

Use heights instead of flex fixes it for me. Do not swap the bottom sheet in scrollviews either

[mleister97]

Please share an example, i can't fix this

[karimcambridge]

In your code, you have your bottom sheet in a parent view right

You have to use height there too and in the render content

[mleister97]

I already tried that. Did not work for me. You can also checkout the duplicate, there I posted my code. Maybe you can help me.

I will close this as its a duplicate of #203

[yzalvov]

Setting the device screen height to the BottomSheet's parent container worked for me. I posted an example code in the referred thread #203