You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
asafkorem
changed the title
Wait for BridgeIdlingResource to become idle timed out
Android: Wait for BridgeIdlingResource to become idle timed out
Nov 12, 2023
@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.
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: