Skip to content
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

Android: Wait for BridgeIdlingResource to become idle timed out #4279

Open
asafkorem opened this issue Nov 12, 2023 · 2 comments
Open

Android: Wait for BridgeIdlingResource to become idle timed out #4279

asafkorem opened this issue Nov 12, 2023 · 2 comments

Comments

@asafkorem
Copy link
Contributor

asafkorem commented Nov 12, 2023

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:

Test Failed: Wait for [com.wix.detox.reactnative.idlingresources.BridgeIdlingResource] to become idle timed out

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.

@asafkorem asafkorem changed the title Wait for BridgeIdlingResource to become idle timed out Android: Wait for BridgeIdlingResource to become idle timed out Nov 12, 2023
@d4vidi d4vidi pinned this issue Nov 12, 2023
@KaterinaUK
Copy link

any updates on this issue?

Also if anyone knows a workaround that would be very helpful, thank you!

@d4vidi
Copy link
Collaborator

d4vidi commented Apr 8, 2024

@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.

@d4vidi d4vidi removed the 📌 pinned label Apr 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants