-
Notifications
You must be signed in to change notification settings - Fork 1.1k
V3 Keyboard dismisses automatically #1289
Comments
Couldn't find version numbers for the following packages in the issue:
Can you update the issue to include version numbers for those packages? The version numbers must match the format 1.2.3. The versions mentioned in the issue for the following packages differ from the latest versions on npm:
Can you verify that the issue still exists after upgrading to the latest versions of these packages? |
The versions mentioned in the issue for the following packages differ from the latest versions on npm:
Can you verify that the issue still exists after upgrading to the latest versions of these packages? |
Related issue: |
"react-native-tab-view": "^2.15.2", using old version seems to fix the issue. but need fix in latest version |
Related |
This issue is fixed when trying the snack with `react-native-pager-view@5.4.25. Closing this |
Not Working even with react-native-pager-view@5.4.25 |
+1 still not working |
Thanks @kyrstencarlson, I'm reopening this. Can you open an issue in |
|
Current behavior
After upgrading from ^2.15.0 to ^3.1.1, TextInput on iOS loses focus immediately after pressing.
It works fine on Android. With the ^2.15.0 it worked fine on iOS too, but I need to update the library on its latest.
In my case, the moment an Animated View changes its height (e.g from 0 to 200 and vice versa) on TextInput focus, the keyboard appears and closes in an instant. The moment I remove the Animated View which changes its height, the TextInputs work just fine. Check out the reproduction of the bug on the link I attached from Snack.
Note: I'm using @react-navigation/material-top-tabs on this screen as well, the Animated View stays on top of tabs, and the first route of the Tabs has many TextInputs inside.
Expected behavior
Keyboard should display and TextInput should keep its focus when some content changes its height inside the same screen
Reproduction
https://snack.expo.dev/OsQWK-1Db
Platform
Environment
The text was updated successfully, but these errors were encountered: