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
When using a BottomSheetTextInput inside a bottomsheet (not a modal), it has many issue in latest version on RN0.73+
=> if using autofocus, it will "blink" open the sheet / display keyboard / and close itself right away (randomly, 8 times out of 10)
=> when it "works" and open, it won't respect the sheet height (snapPoint) I wanted, 9 times out of 10 and will just open full height
In the first attached video, we can see the second case, first time autofocus open the sheet at its expected height, second it opens it full screen height without caring about my snapPoint
bottomsheetinput_issue.webm
On the other hand, if I remove the autofocus: snapPoints is initially respected, but as soon as I tap the input then the keyboard expanding will blink and close the sheet right away (second video)
Bug
When using a BottomSheetTextInput inside a bottomsheet (not a modal), it has many issue in latest version on RN0.73+
=> if using autofocus, it will "blink" open the sheet / display keyboard / and close itself right away (randomly, 8 times out of 10)
=> when it "works" and open, it won't respect the sheet height (snapPoint) I wanted, 9 times out of 10 and will just open full height
In the first attached video, we can see the second case, first time autofocus open the sheet at its expected height, second it opens it full screen height without caring about my snapPoint
bottomsheetinput_issue.webm
On the other hand, if I remove the autofocus: snapPoints is initially respected, but as soon as I tap the input then the keyboard expanding will blink and close the sheet right away (second video)
bfdee7c0-73bd-4c14-9c8a-87c014295e2c.mp4
My code is very basic:
<BottomSheetTextInput
value={newName}
onChangeText={setNewName}
isDisabled={isLoading}
autoFocus
...
Environment info
The text was updated successfully, but these errors were encountered: