Detox Android incompatible with RN >= 50

[guyca]

Detox idling resources are not compatible with changes made in RN 50:

onMessage: {"messageId":3,"type":"error","params":{"error":"Wait for [com.wix.detox.espresso.ReactNativeUIModuleIdlingResource] to become idle timed out"}}

Encountered this while testing uses cases in RNN involving reload (By pressing R R)

[rotemmiz]

Detox Android idling resources are not compatible with changes made in RN 50, we are working on finding a solution for that. In the meantime, Detox Android does not support RN >=50 !

[aricgemco]

Just to confirm.

• Detox for Android is not compatible with RN>=51

• react-native-navigation is only compatible with RN>=51

So currently we cannot use RNN and Detox for Android?

[ksmahesh]

Hey @guyca @rotemmiz
I was using detox for react native 50.3 and it worked really well. So thanks!

I do have some questions regarding whats mentioned here on this issue:

1. When support is added for RN >=51 will it support RN 54? Or is the support added only to 51?
2. Is there any ETA on when this support for higher version will be available? Even if its a alpha/beta release?

[rotemmiz]

I went over 0.49-stable - 0.50-stable diff, and found a few possible culprits.

Implement lazy discovery for ViewManagers.
facebook/react-native@da30b04

Move destroy threads in catalystinstance off the UI thread
facebook/react-native@cf2ef84 (Espresso syncs with AsyncTasks by default)

[simonracz]

FYI, I can work on this full time from Tuesday.

[ericketts]

I seem to be experiencing 2 separate issues on my app using RN 0.54.2 (and react-native-navigation 1.1.0), where neither are the issue from the OP (I can make this a different ticket if that's more helpful):

• The app installs, the isReady event fires, and the app never responds with a ready event, leading to the detox client hanging
• The app installs, isReady fires, ready fires, but the view hierarchy doesn't load correctly before the tests run, leading to erroneously failed tests with a No views in the hirarchy found matching.

If those two issues are avoided, the tests run and pass without a hitch (and the iOS side of things works perfectly).

Edit: In the first failure case, I see ReactNativeSupport failing to get the reactContext after a minute of waiting.