Tried to access a JS module before the React instance was fully set up

[abdullahizzuddiin]

Description:

Caused by java.lang.RuntimeException
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.

Environment
Version: 3.3.0
Install using: yarn

Steps to Reproduce Issue:
Actually, I cannot reproduce this issue. But, thousand users of my app get this error

Anything else:

Caused by java.lang.RuntimeException: 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.
       at com.facebook.react.bridge.ReactContext.getJSModule(ReactContext.java:107)
       at com.geektime.rnonesignalandroid.RNOneSignal.sendEvent(RNOneSignal.java:102)
       at com.geektime.rnonesignalandroid.RNOneSignal.notificationReceived(RNOneSignal.java:413)
       at com.onesignal.OneSignal.handleNotificationReceived(OneSignal.java:2025)
       at com.onesignal.NotificationExtenderService.processJsonObject(NotificationExtenderService.java:194)
     (crash stacktraces, as well as any other information here)  at com.onesignal.NotificationExtenderService.processIntent(NotificationExtenderService.java:155)
       at com.onesignal.NotificationExtenderService.onHandleWork(NotificationExtenderService.java:123)
       at com.onesignal.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:439)
       at com.onesignal.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:430)
       at android.os.AsyncTask$2.call(AsyncTask.java:295)
       at java.util.concurrent.FutureTask.run(FutureTask.java:237)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
       at java.lang.Thread.run(Thread.java:818)

[rgomezp]

Howdy,
Unfortunately, it's hard to know what may be happening or how to fix this if we don't have repro steps. If anyone has any further details, it would be very helpful.

[rgomezp]

Closing due to no response

[moxspoy]

Hallo, im facing same issue. The issue was founded in Crashlytics, so we cannot reproduce this kind of bug.

[abdullahizzuddiin]

Hello, @moxspoy . Do yo know how to reproduce those errors?

According to my firebase console, those errors always occurred when the application in the beginning.

[panncr]

Maybe, notification received when the app still start up?

Have you tried to sent notification specific for your device a moment after you open the app?

[abdullahizzuddiin]

Yes @panncr . Your statement is true. After I followed your advice, I sent notification to my device exact after I open the app, my app is force closed.

I solved this issue by updated sendEvent() method on node_modules/react-native-onesignal/android/src/main/java/com/geektime/rnonesignalandroid/RNOneSignal.java

private void sendEvent(String eventName, Object params) {
        if(!mReactContext.hasActiveCatalystInstance()) {
            return;
        }

        mReactContext
              .getJSModule(DeviceEventManagerModule.RCTDeviceEventEmitter.class)
              .emit(eventName, params);
    }

[rgomezp]

Related stack overflow thread