We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We're seeing this mysterious crash in our production app. It happens seemingly at random, when the user drags in the app. I don't have a clean stack trace, but the error happens in the React codebase, here: https://github.com/facebook/react/blob/v0.14.7/src/renderers/shared/event/eventPlugins/ResponderTouchHistoryStore.js#L123 Looking at the code, I'm not sure how this could be happening - I suspect it could be a bug in JSC. Possibly related: https://bugs.webkit.org/show_bug.cgi?id=138038
Last seen in React Native 0.22, React 0.14.7, and iOS 9.3
The text was updated successfully, but these errors were encountered:
we have seen this too (and at the EXACT location you pointed at).
using RN 0.22.2
Sorry, something went wrong.
That linked JSC bug sounds like it was fixed in time for iOS 9 so I don't think that's it.
We're seeing this as well, using RN 0.22.
Potentially related threads: facebook/react#6277, #5246
Good catch @drtangible - going to close this out since it's believed to be fixed in RN 0.24
No branches or pull requests
We're seeing this mysterious crash in our production app. It happens seemingly at random, when the user drags in the app. I don't have a clean stack trace, but the error happens in the React codebase, here: https://github.com/facebook/react/blob/v0.14.7/src/renderers/shared/event/eventPlugins/ResponderTouchHistoryStore.js#L123
Looking at the code, I'm not sure how this could be happening - I suspect it could be a bug in JSC. Possibly related: https://bugs.webkit.org/show_bug.cgi?id=138038
Last seen in React Native 0.22, React 0.14.7, and iOS 9.3
The text was updated successfully, but these errors were encountered: