TextInput with keyboardType="numeric" on iPad switches to the default keyboard when tapped again while focused
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 127k
- Forks
- 25.3k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 4
Description
Description
On iPad, a TextInput configured with keyboardType="numeric" initially displays the numeric keyboard as expected.
However, if the keyboard remains open and the user taps the same TextInput again, iOS switches to the default keyboard instead of keeping the numeric keyboard.
This does not happen on iPhone.
Steps to reproduce
- Launch the app on an iPad IPad Pro 11-inch (either physical device or simulator).
- Tap a numerical TextInput.
- The numeric keyboard is displayed.
- Without dismissing the keyboard, tap the same TextInput again.
React Native Version
0.86.0
Affected Platforms
Runtime - iOS
Output of npx @react-native-community/cli info
System:
OS: macOS 26.2
CPU: (10) arm64 Apple M1 Max
Memory: 2.17 GB / 64.00 GB
Shell:
version: "5.9"
path: /bin/zsh
Binaries:
Node:
version: 22.23.1
path: /Users/xxx/.nvm/versions/node/v22.23.1/bin/node
Yarn:
version: 1.22.22
path: /opt/homebrew/bin/yarn
npm:
version: 10.9.8
path: /Users/xxx/.nvm/versions/node/v22.23.1/bin/npm
Watchman:
version: 2025.07.21.00
path: /opt/homebrew/bin/watchman
Managers:
CocoaPods:
version: 1.16.2
path: /opt/homebrew/lib/ruby/gems/3.1.0/bin/pod
SDKs:
iOS SDK:
Platforms:
- DriverKit 25.2
- iOS 26.2
- macOS 26.2
- tvOS 26.2
- visionOS 26.2
- watchOS 26.2
Android SDK:
API Levels:
- "31"
- "33"
- "35"
- "36"
Build Tools:
- 34.0.0
- 35.0.0
- 35.0.1
- 36.0.0
System Images:
- android-31 | Google APIs ARM 64 v8a
- android-31 | Google APIs Intel x86_64 Atom
- android-31 | Google Play ARM 64 v8a
- android-31 | Google Play Intel x86_64 Atom
- android-35 | Google APIs ARM 64 v8a
- android-35 | Google APIs Intel x86_64 Atom
- android-35 | Google Play ARM 64 v8a
- android-35 | Google Play Intel x86_64 Atom
- android-35 | Google APIs Tablet ARM 64 v8a
- android-36 | Google Play ARM 64 v8a
- android-36 | Google Play Intel x86_64 Atom
- android-36 | Pre-Release 16 KB Page Size Google APIs ARM 64 v8a
Android NDK: Not Found
IDEs:
Android Studio: 2024.3 AI-243.24978.46.2431.13363775
Xcode:
version: 26.2/17C52
path: /usr/bin/xcodebuild
Languages:
Java:
version: 17.0.15
path: /usr/bin/javac
Ruby:
version: 3.1.7
path: /opt/homebrew/opt/ruby@3.1/bin/ruby
npmPackages:
"@react-native-community/cli":
installed: 20.1.0
wanted: 20.1.0
react:
installed: 19.2.3
wanted: 19.2.3
react-native:
installed: 0.86.0
wanted: 0.86.0
react-native-macos: Not Found
npmGlobalPackages:
"*react-native*": Not Found
Android:
hermesEnabled: true
newArchEnabled: true
iOS:
hermesEnabled: true
newArchEnabled: true
Stacktrace or Logs
no logs
MANDATORY Reproducer
https://github.com/mBleichnerMagicPlan/DoubleTapInNumericTextInput
Screenshots and Videos
https://github.com/user-attachments/assets/e39cb596-7067-40c7-b87c-25c01d42fd3d
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 by running the mandatory reproducer on an iPad and confirm the second tap changes the numeric keyboard. Trace the React Native iOS TextInput keyboard handling involved in that interaction. Done means repeated taps retain the numeric keyboard on iPad without changing the behavior on iPhone.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, react-native
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100