react-navigation / react-navigation/react-navigation
Keyboard hides => shows => hides when navigating back (from ios gesture only) from a screen where keyboard is shown
Open
Nobody has claimed this yet.
bug
platform:ios
repro provided
- Dominant language
- TypeScript
- Stars
- 24.5k
- Forks
- 5.1k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 18
Description
Current behavior
As you can see, when i start the gesture, it dismiss keyboard as expected. But when the gesture ends, it pops back up the keyboard.
Expected behavior
I expect the keyboard to stay dismissed when the gesture finishes.
Reproduction
https://github.com/nikolasgioannou/react-navigation-bug
Platform
- Android
- iOS
- Web
- Windows
- MacOS
Packages
- @react-navigation/bottom-tabs
- @react-navigation/drawer
- @react-navigation/material-top-tabs
- @react-navigation/stack
- @react-navigation/native-stack
- react-native-tab-view
Environment
- [] I've removed the packages that I don't use
| package | version |
|---|---|
| @react-navigation/native | "^6.1.17", |
| @react-navigation/stack | "^6.3.29" |
| react-native-safe-area-context | "4.8.2", |
| react-native-screens | "~3.29.0" |
| react-native-gesture-handler | "~2.14.0", |
| react-native | "0.73.6", |
| expo | "~50.0.14", |
| node | 18.14.2 |
| npm or yarn | 1.22.19 |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked reproduction and the @react-navigation/stack iOS gesture behavior using the versions listed in the issue. Reproduce the back gesture from a screen with the keyboard open, then trace the stack navigation path; done means the keyboard remains dismissed after the gesture finishes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, react-native, typescript
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100