-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Delay Screen Navigation when using TextInput #3601
Comments
Hey @saadi-ninjasCode, could you please extract the specific code to the separated snack? |
@lukewalczak , Here is the link of the separated Snack. |
I think the screen with TextInput's is overloaded and needs some optimization. Once I left there only eg 4 of them, there is no delay. Do you experience the similar issue in your project or just on the example snack? |
I experience a similar issue in my project. I have 6 inputs on my screen. Then I run the React Native Snack example and I face the same issue there. That's why I report this issue. When I use the Bare React Native TextInput I didn't face such an issue. |
The textinput is currently really slow indeed! |
Hey @saadi-ninjasCode, could you please check whether the delay is visible using the latest version 5.2.0? |
I didn't notice any improvement in delay. |
@praweshlamsal No, unfortunately. This was for a personal project so I just kept it as is 🤷♀️ |
I got this issue when I used |
Current behaviour
When navigating screen B from Screen A. Screen B has some text inputs (even single input). When pressing a button on Screen A, Screen A gets stuck for some seconds (e.g 2 sec). Screen navigation starts after some seconds(e.g 2 sec)
When I experiment with React Native text input, I didn't face such delays.
This behaviour can be seen in react-native-paper snack example
Expected behaviour
There will be no such delay in screen navigation.
How to reproduce?
This behaviour can be seen in react-native-paper snack example
Your Environment
Video Recording:
Screenrecorder-2023-01-20-11-02-19-934.mp4
The text was updated successfully, but these errors were encountered: