-
Notifications
You must be signed in to change notification settings - Fork 3.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
Manually handle keyboard to prevent Android crash #2707
Conversation
cc @Julesssss since I think you might be interested in this fix. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the on screen keyboard will NOT automatically dismiss when navigating to a new screen. Defaults to true.
This is working nicely. Given that we are adding the flag to the main nav stack I was worried that the soft keyboard would remain open when navigating to Screens with no input fields (this happens with native Android if you remove the auto-handling and don't manually close the soft keyboard) -- but this doesn't seem to be happening...
This is great, but I'm a bit confused as to why this is -- something must be telling the keyboard to hide and I would love to know what that is (behavior that we've declared elsewhere, or maybe default RN handling that occurs if the screen contains no input?). It's not important enough to block the merge and I don't have the time to investigate the RN/navigation code, but please let me know if you have any theories!
|
all yours @ctkochan22 |
🚀 Deployed to staging in version: 1.0.39-1🚀
|
🚀 Deployed to production in version: 1.0.39-5🚀
|
Details
Fix Android crash due to automatic handling of software keyboard
Fixed Issues
Fixes #2694
Tests
QA Steps
Repeat steps in linked issue...
Tested On
Screenshots
Web
Mobile Web
Desktop
iOS
Android