`TextInput` emits `onChange` event with invalid `selection` on Android browser autofill
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 127k
- Forks
- 25.3k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 4
Description
Description
On Android, filling a TextInput via browser/system autofill emits an onChange event whose nativeEvent.selection is {start: 0, end: 0} instead of pointing to the end of the inserted text.
The text is correct, but the selection is wrong — the cursor is reported at the start of the field rather than after the autofilled value. The same input entered by pasting (from clipboard) reports the correct selection, and iOS reports the correct selection for both paste and autofill.
<TextInput
autoComplete="tel"
onChange={console.log}
/>
Expected vs. actual
iPhone 17 (iOS 26.5) — correct in both cases
✅ Paste +1 (555) 123-4567:
nativeEvent: {
text: '+1 (555) 123-4567',
selection: { start: 17, end: 17 }
}
✅ Browser autofill +1 (555) 123-4567:
nativeEvent: {
text: '+1 (555) 123-4567',
selection: { start: 17, end: 17 }
}
Pixel 10 Pro XL (Android 17.0) — autofill is broken
✅ Paste +15551234567:
nativeEvent: {
text: '+15551234567',
selection: { start: 12, end: 12 }
}
❌ Browser autofill +15551234567:
nativeEvent: {
text: '+15551234567',
selection: { start: 0, end: 0 }
// ~~~~~~~~~~~~~~~~~~~~
}
On Android, autofill reports selection: { start: 0, end: 0 } while the text length is 12.
Steps to reproduce
- Clone https://github.com/nsbarsukov/react-native-android-autofill-bug
- Run
npm ci - Run
npm start - Focus the input and trigger the browser/system autofill suggestion for a phone number.
React Native Version
0.86.0
Affected Platforms
Runtime - Android
Output of npx @react-native-community/cli info
System:
OS: macOS 26.4.1
CPU: (8) arm64 Apple M2
Memory: 166.00 MB / 8.00 GB
Shell:
version: "5.9"
path: /bin/zsh
Binaries:
Node:
version: 26.4.0
path: /Users/nsbarsukov/.nvm/versions/node/v26.4.0/bin/node
Yarn: Not Found
npm:
version: 11.17.0
path: /Users/nsbarsukov/.nvm/versions/node/v26.4.0/bin/npm
Watchman:
version: 2026.06.08.00
path: /opt/homebrew/bin/watchman
Managers:
CocoaPods: Not Found
SDKs:
iOS SDK:
Platforms:
- DriverKit 25.5
- iOS 26.5
- macOS 26.5
- tvOS 26.5
- visionOS 26.5
- watchOS 26.5
Android SDK: Not Found
IDEs:
Android Studio: 2026.1 AI-261.23567.138.2611.15646644
Xcode:
version: 26.6/17F113
path: /usr/bin/xcodebuild
Languages:
Java: Not Found
Ruby:
version: 2.6.10
path: /usr/bin/ruby
npmPackages:
"@react-native-community/cli": Not Found
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: Not found
newArchEnabled: Not found
iOS:
hermesEnabled: Not found
newArchEnabled: Not found
Stacktrace or Logs
nativeEvent: {
text: '+15551234567',
selection: { start: 0, end: 0 }
}
MANDATORY Reproducer
https://github.com/nsbarsukov/react-native-android-autofill-bug
Screenshots and Videos
https://github.com/user-attachments/assets/866d4fd3-3852-4ca3-8408-7c0d1b4c17f8
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 with npm ci and npm start, then focus on the TextInput onChange event path for Android browser/system autofill. Done means autofilled text reports a selection at the end of the inserted value, while pasted input and iOS behavior remain unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, react-native
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100