Repository navigation
Changing TextInput selection after setting text crash #25265
Description
When TextInput selection is updated after changing the text (using InteractionManager.runAfterInteractions to wait for the change to apply) RN crashes. You get error like "setSpan(4 ... 4) ends beyond length" which indicates that the text field text has not changed like you would expect when using runAfterInteractions.
React Native version:
info
React Native Environment Info:
System:
OS: macOS 10.14.4
CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
Memory: 34.23 MB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 10.16.0 - ~/.nvm/versions/node/v10.16.0/bin/node
Yarn: 1.12.3 - /usr/local/bin/yarn
npm: 6.9.0 - ~/.nvm/versions/node/v10.16.0/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
Android SDK:
API Levels: 24, 25, 26, 27, 28
Build Tools: 23.0.1, 25.0.0, 25.0.2, 26.0.1, 26.0.2, 26.0.3, 27.0.3, 28.0.3
System Images: android-25 | Google Play Intel x86 Atom, android-26 | Google APIs Intel x86 Atom
IDEs:
Android Studio: 3.4 AI-183.6156.11.34.5522156
Xcode: 10.1/10B61 - /usr/bin/xcodebuild
npmPackages:
react: 16.8.3 => 16.8.3
react-native: 0.59.9 => 0.59.9
Steps To Reproduce
- Change controlled TextInput value in code
- Change TextInput selection to be after the inserted text using InteractionManager.runAfterInteractions
or just run the example in repo I linked and press the button.
Describe what you expected to happen:
Selection changes to place after inserted text
Snack, code example, or link to a repository:
https://github.com/Vaintti/RNTextInputBug
Activity
blohamen commentedon Aug 13, 2019
Have similar issue on RN 0.60.4
Fix Chat Input Crashes on Android
Fix Chat Input Crashes on Android
Fix Chat Input Crashes on Android (#20058)
blohamen commentedon Oct 4, 2019
Issue still reproduced in React Native 0.61.2
callcter commentedon Oct 16, 2019
same issue in 0.61.2
Cap selection indices when text changes (#26680)
cayodonatti commentedon Nov 26, 2019
I also still got the issue in React Native 0.61.1, seems to only happen on Android
anilios commentedon Nov 28, 2019
I am also having same issue.. don't know how to fix..
stale commentedon Feb 27, 2020
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.
jsamr commentedon Feb 27, 2020
This issue has not been fixed.
7 remaining items
jsamr commentedon Aug 29, 2020
Someone has been able to reproduce on latest versions?
stale commentedon Dec 25, 2020
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.
jsamr commentedon Dec 26, 2020
I believe this is still relevant.
SonuToor commentedon Jan 26, 2021
Still having this on
0.63.3jsamr commentedon Feb 26, 2021
I just reproduced this bug on
0.63.4fabOnReact commentedon Mar 16, 2021
To answer the question of when the pr #29070 which fixes this issue will be released in the next version of React Native, I suggest you to follow the discussions at https://github.com/react-native-community/releases/issues by subscribing to those threads. The process of releasing a new version with a bug fix is the following:
React Native sync for revisions 54f297a...ab075a2
github-actions commentedon Mar 12, 2023
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days.
github-actions commentedon Mar 19, 2023
This issue was closed because it has been stalled for 7 days with no activity.