React-native: Attempted to invoke `3` (method ID) on `UIManager` (NativeModule name) with an invalid bridge.

[nihp]

🐛 Bug Report

I am facing lot of warnings which not allowing me to make any event in the app.
Attempted to invoke 3 (method ID) on UIManager (NativeModule name) with an invalid bridge. Refer the attached image

To Reproduce

I am facing this issue in latest version of "react-navigation": "^3.2.3" (v3)

Expected Behavior

Need to remove all the warnings (Attempted to invoke 3 (method ID) on UIManager (NativeModule name) with an invalid bridge.)

Environment

npmPackages:
react: 16.8.1 => 16.8.1
react-native: ^0.58.4 => 0.58.6
npmGlobalPackages:
react-native-cli: 2.0.1

[react-native-bot]

Can you run react-native info and edit your issue to include these results under the Environment section?

If you believe this information is irrelevant to the reported issue, you may write [skip envinfo] alongside an explanation in your Environment: section.

[nihp]

I have added the environment details for react-native.

[kelset]

👋

This issue seems to be related to how you use react-navigation, so I'd recommend you open an issue there - also, it would help incredibly if you could add a repro to your code.

That said, this seems to be also only warnings, that suggest this being related to your code, and you are on an old RN version.

Because of all these reasons, I'll close this. Please LMK if this happens on a clean react-native project (without react-navigation) by submitting a repro - in that case we can reopen this and investigate further.

[rjruizes]

I found this issue while trying to debug an error message Unable to find module for UIManager. Randomly, I also got the multiple warning screen that @nihp posted, e.g.

Attempted to invoke `6` (method ID) on `UIManager` (NativeModule name) with an invalid bridge

I'm using RN 0.59.3. I'll try to undo some commits to see if I can get rid of it.

[RoderickJDunn]

I just upgraded to RN 0.59.5 and get the "Unable to find module for UIManager" error every time I reload the bundle. This was definitely not present in RN 0.57.7. FWIW the error is logged and then the code is reloaded anyway without any apparent issues other than this error log.

I will update if I find the cause.

[SwordElucidator]

@RoderickJDunn
Hey, did you find the cause?

[RoderickJDunn]

@SwordElucidator I never found out what was causing this specifically, but after I updated to RN 0.61 the error/warnings are gone.