Tried to access a JS module before the React instance was fully set up. Calls to ReactContext#getJSModule should only happen once initialize() has been called on your native module. #3586
Description
If you see the exception, come from visioncamera.
com.mrousavy.camera.react.CameraDevicesManager
AndroidRuntime: at com.mrousavy.camera.react.CameraDevicesManager.sendAvailableDevicesChangedEvent(CameraDevicesManager.kt:102) 07-21 11:53:22.790 19288 19373 E AndroidRuntime: at com.mrousavy.camera.react.CameraDevicesManager1.invokeSuspend(CameraDevicesManager.kt:74) 07-21 11:53:22.790 19288 19373 E AndroidRuntime: at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) 07-21 11:53:22.790 19288 19373 E AndroidRuntime: at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:101) 07-21 11:53:22.790 19288 19373ecc ecc
Originally posted by @Master-Antonio in #3585
Its vision camera, not webrtc.
In my app navigator there is a screen that use vision camera, that mean when you open the app there is the initialization of vision camera too, and it crash with that error.
I tried also to load this screen in lazy mod but dont work too, same error.
const CallScreen= lazy(() => import('../screens/screen'));
<Stack.Screen
name="Call"
>
{() => (
<Suspense fallback={<CallScreenFallback />}>
<CallScreen />
</Suspense>
)}
</Stack.Screen>
webrtc have camera control too, so i think they go in conflict.