-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Android: Wait for BridgeIdlingResource to become idle timed out #4279
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
Comments
any updates on this issue? Also if anyone knows a workaround that would be very helpful, thank you! |
@KaterinaUK as explained, the problem seems to have been resolved in RN 72, when used alongside up to date reanimated releases. Upgrading both solves the issue. |
This fixed my issue: gradle 7.2.2 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions! For more information on bots in this repository, read this discussion. |
This issue has been fixed indirectly will the official release of support for RN's new architecture, in Detox 20.34.0 - in apps that have fully migrated, including bridge-less mode being enabled. |
What happened?
A bug report from an older version of React Native Navigation describes an issue encountered after upgrading from RN0.69 to RN0.71. The tests, specifically on Android, began failing intermittently with the error:
This problem may be linked to a combination of factors, notably observed in projects using react-native-navigation and reanimated libraries. It appears that the issue has subsided following upgrades to Reanimated (version 3) and React Native (version 0.72). With these updates, the error has not been reproducible in the latest navigation tests.
Despite the apparent resolution, I am keeping this issue open for monitoring purposes. This is to ensure that if anyone experiences this error under different conditions, it can be further investigated.
Of course, if you encounter this issue or a similar synchronization problem, try to investigate it before reporting. There's a high chance it occurs uniquely in your project, and investigating will also help you and us understand the problem better. For guidance, read our troubleshooting guide.
The text was updated successfully, but these errors were encountered: