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
henrymoulton
changed the title
[v5] Popping keyboard sometimes causes snappoints to go to -1 and never re-opne
[v5] Popping keyboard sometimes causes snappoints to go to -1 and never re-open
Dec 4, 2023
henrymoulton
changed the title
[v5] Popping keyboard sometimes causes snappoints to go to -1 and never re-open
[v5] Popping keyboard sometimes causes bottom sheet to close and never re-open
Dec 4, 2023
henrymoulton
changed the title
[v5] Popping keyboard sometimes causes bottom sheet to close and never re-open
[v5] (Race Condition?) Popping keyboard sometimes causes bottom sheet to close and never re-open
Dec 4, 2023
Bug
This might be related to the bug we've been dealing with since upgrading to REA3. I don't yet have a reproducible code sample but I do have some logs.
Note that the way I reproduced this was by using the Keyboard events, but I have user bug reports from just opening the screen.
Environment info
Steps To Reproduce
Note that we'd always want this BottomSheet to be visible, if it is hidden due to Keyboard it should show again.
Watch logs, it doesn't always happen but eventually I got a log:
I'm maybe surprised there's no keyboard event for when the keyboard is hidden?
Describe what you expected to happen:
-1
and even if it did it would recover to0
Reproducible sample code
None yet, and it's particularly difficult to reproduce.
Workaround
I've added a patch to the props
isNeverClosed
which checks if the animatedIndex is every -1 and early returns.Similar solutions exist in #1359 and #1320
The text was updated successfully, but these errors were encountered: