-
Notifications
You must be signed in to change notification settings - Fork 24.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
android num-pad keyboard extreme lag after typing #22283
Comments
No update for this? |
No, still facing this issue. Also, I was able to reproduce it on 0.48.0 when using styled textinput (with color, brackgroundColor, fontSize and width). When not using styled textInput, it doesn't happen in 0.48.0 My next solution is to make a native TextInput component myself, or maybe someone has done it already? |
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions. |
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information. |
Environment
Run
react-native info
in your terminal and paste its contents here.Description
I believe that RN's TextInput has some kind of bug related to "num-pad" or "numeric" keyboard on Android. This bug makes the Android keyboard pretty much unusable after a few minutes of typing straight. Closing the app doesn't help, restarting device does.
Reproducible Demo
Both the snack.expo and the repo are a simple TextInput with autoFocus and keyboardType='num-pad'. I had to type about ~800 characters before keyboard started to lag. At ~2000 it was pretty much unusable.
I tested on a Xiaomi Redmi Note 5, Android 8.1.0 and Gboard (default) as device keyboard
I also believe this could be related to #20119, as I discovered this one while trying to solve #20119
The text was updated successfully, but these errors were encountered: