-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
When i tap R on metro after reload it shows the error Exception in native call from js #5225
Comments
same here, out of the sudden, version 11.3.3, rn 0.63.4 logcat:
if it matters, killing the app fixes it. When i tap @osramesh06 please update the issue and follow the issue template otherwise this issue will be closed |
Well, a stack trace from logcat with the version gets bonus points, that helps us actually locate the issue. v11.3.x has a new high-performance task core that allows parallel execution but, it's new, and things that are hard to test (like hot reloads) are edge cases I'd expect to see some bugs in. ConcurrentModificationException issues are typically easy to fix though, let me see |
Reproduced locally, fixing |
Access to the collection of TaskExecutors wasn't correctly synchronized in all places Fixes #5225
This correctly identifies that #5225 can happen, where previously it passed CI with no problem. Tested by applying / removing the fix for 5225 and now CI will fail if a redbox ever happens again
next release will have it, just pending CI and I'll release a fix for this one In the meantime you may get moving locally if you grab the patch-package patch set from the artifacts list on this CI action https://github.com/invertase/react-native-firebase/actions/runs/794045768#artifacts |
This correctly identifies that #5225 can happen, where previously it passed CI with no problem. Tested by applying / removing the fix for 5225 and now CI will fail if a redbox ever happens again
@mikehardy it works as a charm now, thanks for your hard work! |
This correctly identifies that #5225 can happen, where previously it passed CI with no problem. Tested by applying / removing the fix for 5225 and now CI will fail if a redbox ever happens again
Access to the collection of TaskExecutors wasn't correctly synchronized in all places Fixes #5225
Release 11.4.1 just went out with the change related to this among other fixes + features. Enjoy! 🚀 |
Access to the collection of TaskExecutors wasn't correctly synchronized in all places Fixes invertase#5225
The text was updated successfully, but these errors were encountered: