-
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
ConcurrentModificationException #20272
Comments
Seeing this in our bugsnag as well. Same stacktrace. Obviously seems to be related to rendering a Switch, based on the stacktrace. |
I am closing this issue because it does not appear to have been verified on the latest release, and there has been no followup in a while. If you found this thread after encountering the same issue in the latest release, please feel free to create a new issue with up-to-date information by clicking here. |
A nice way to get rid of bugs without fixing them. As nobody has mentioned a fix in the next RN version, it probably does not exist. Testing with the new RN is not currently possible as it has compatibility issues with my dependencies (or for some other reason does not work at all). |
We're seeing this occasionally in our app's production crash reports as well. So far it has only shown up on 3 devices, all running Android 6.0.x. Unable to find deterministic repro steps.
|
Getting this on android only:
All bugs related to this end up getting closed with no without a solution!!! |
Environment
Environment:
OS: macOS High Sierra 10.13.5
Node: 8.11.3
Yarn: 1.7.0
npm: 5.6.0
Watchman: 4.9.0
Xcode: Xcode 9.4.1 Build version 9F2000
Android Studio: 3.1 AI-173.4697961
Packages: (wanted => installed)
react: 16.4.1 => 16.4.1
react-native: 0.55.4 => 0.55.4
Description
Reproducible Demo
No idea how to reproduce as occurs randomly in release builds. The stack trace is from Crashlytics. Seems to be related on how React Native updates the UI. Our code does not have much control over the native screen updating and as JavaScript is single threaded, there isn't much we can do about concurrency.
The text was updated successfully, but these errors were encountered: