-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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
TextInput Component crashing app when character count exceeds 490 (IOS versions 11.0 or higher only) #18815
Comments
Thanks for posting this! It looks like your issue may refer to an older version of React Native. Can you reproduce the issue on the latest release, v0.55? Thank you for your contributions. |
This is still an issue on the latest version of React Native |
I have the same issue on RN version 0.55.4 and React version 16.3.1. The stack trace is:
|
I'm experiencing the same as soon as the |
I have the same error for string like that qwertywertwQwertywertTy99,99?
|
I have the same error.
|
same issue on react native 0.54.2 Fatal Exception: NSInvalidArgumentException |
I am having the same issue here. Any one got an idea on a fix? |
I can't update my app because of this! Itunes is rejecting the app because it crashes on their test device iOS 11.4.1. Using react 16.3.2 and react native 0.55.3. Does anyone have a solution for this one?? |
Is this still an issue in 0.56? |
@ajfigueroa I made an update to RN 0.56 and have posted an update to iTunes. I will update when I know more! My build has always worked in simulator, on my device via xcode. The very same build that works in Testflight is crashing for the testers at iTunes. I really cant reproduce this but the crashlogs from iTunes leads me to this error. The testers say that the app crashes efter they fill in the username and password on start screen and hit return on the software keyboard. |
I had a similar issue, my app crashed when number of symbols exceeded the input width. In my case it was fontFamily style applied to TextInput with secureTextEntry={true}. Removing fontFamily solved it for me. |
@ConstantineDB Thanks, turns out that was the source of issue for me. This looks like an iOS 11 bug as per this Radar: http://www.openradar.me/35278732 |
Sorry, late response here. I got my app approved after update to RN 0.56. |
Still experiencing issues on RN 0.56 but the fontFamily workaround does work. Thanks for that @ConstantineDB |
We're exhibiting this issue as well. Still happens on iOS 12 |
We're seeing this on password fields in our react native 0.55 app, and in a version built with 0.57. |
Same here running on 0.55.4 on iOS 12. Is there any workaround? |
I think this is related: #19453 |
@taschik We worked around it by dropping the |
This fixed the issue for me, thank you! |
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. |
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information. |
The TextInput component on iOS versions of 11 or higher seems to be crashing the entire mobile application when I enter a long text consisting of 490 characters or more. There aren't any errors that pop up in the Javascript console but our QA engineer found this message below inside their crash log. Note: this is only happening on an actual iPhone device, not a simulator.
Environment
Environment:
OS: macOS High Sierra 10.13.2
Node: 8.9.3
Yarn: 1.3.2
npm: 5.5.1
Watchman: 4.9.0
Xcode: Xcode 9.3 Build version 9E145
Android Studio: 2.3 AI-162.4069837
Packages: (wanted => installed)
react: 16.0.0 => 16.0.0
react-native: ~0.55.0 => 0.55.0
Steps to Reproduce
Expected Behavior
The TextInput rendering logic should be completely independent from the character count.
Actual Behavior
The application crashes and we are sent to the home screen.
The text was updated successfully, but these errors were encountered: