[Question]: Why is there an issue in intialize or other things from react-native-onesignal saying appId as null value! The app is working fine in previous released version and current debug builds, but having issues in release builds

[rd273001]

How can we help?

Please let me know how to resolve or what can I do to for the below OneSignal errors logged on Crashlytics :-

Fatal Exception: java.lang.Exception: Must call 'initWithContext' before use
       at com.onesignal.internal.OneSignalImp.getNotifications(OneSignalImp.kt:99)
       at com.onesignal.OneSignal.getNotifications(OneSignal.kt:62)
       at com.onesignal.rnonesignalandroid.RNOneSignal.addNotificationClickListener(RNOneSignal.java:350)
       at com.facebook.jni.NativeRunnable.run(NativeRunnable.java)
       at android.os.Handler.handleCallback(Handler.java:883)
       at android.os.Handler.dispatchMessage(Handler.java:100)
       at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:27)
       at android.os.Looper.loop(Looper.java:224)
       at com.facebook.react.bridge.queue.MessageQueueThreadImpl.lambda$startNewBackgroundThread$2(MessageQueueThreadImpl.java:217)
       at com.facebook.react.bridge.queue.MessageQueueThreadImpl$$ExternalSyntheticLambda1.run(D8$$SyntheticClass)
       at java.lang.Thread.run(Thread.java:919)

Fatal Exception: java.lang.NullPointerException: Parameter specified as non-null is null: method z5.d.i, parameter appId
       at com.onesignal.OneSignal.i(OneSignal.kt:8)
       at com.onesignal.rnonesignalandroid.RNOneSignal.initialize(RNOneSignal.java:247)
       at com.facebook.jni.NativeRunnable.run(NativeRunnable.java)
       at android.os.Handler.handleCallback(Handler.java:883)
       at android.os.Handler.dispatchMessage(Handler.java:100)
       at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:27)
       at android.os.Looper.loop(Looper.java:224)
       at com.facebook.react.bridge.queue.MessageQueueThreadImpl.lambda$startNewBackgroundThread$2(MessageQueueThreadImpl.java:217)
       at java.lang.Thread.run(Thread.java:919)

Fatal Exception: java.lang.RuntimeException: Unable to destroy activity {com.qkclass.dfc/com.qkclass.dfc.MainActivity}: java.lang.Exception: Must call 'initWithContext' before use
       at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:5984)
       at android.app.ActivityThread.handleDestroyActivity(ActivityThread.java:6022)
       at android.app.servertransaction.DestroyActivityItem.execute(DestroyActivityItem.java:47)
       at android.app.servertransaction.ActivityTransactionItem.execute(ActivityTransactionItem.java:45)
       at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:185)
       at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:103)
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2643)
       at android.os.Handler.dispatchMessage(Handler.java:106)
       at android.os.Looper.loopOnce(Looper.java:257)
       at android.os.Looper.loop(Looper.java:368)
       at android.app.ActivityThread.main(ActivityThread.java:8839)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:572)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1049)

Code of Conduct

• [x] I agree to follow this project's Code of Conduct

[nan-li]

Hi @rd273001 thanks for reporting these stack-traces.

What version of react-native-onesignal are these crashes reported for?

Crash 1: Crash when adding notification click listener: When and how are you adding the notification click listener? This trace looks like it is happening on a background thread and SDK initialization may be happening on another thread and not finished?

Crash 2: appId is null It looks like OneSignal.initialize(appId) is being called with null app ID. Can you confirm you are always passing a valid non-null string app ID to this initialization method?

Crash 3: Unable to destroy activity Is this the full stacktrace? I don't see any references to OneSignal classes so I don't know where this is originating from. Do you have any more information on this crash?

[rd273001]

Hi @nan-li , thanks for replying! Sorry for my late response!

I was using ^5.2.8 and I am getting the app id as well. And YES above was the full stack trace. Still I am getting the error, and Firebase Crashlytics is giving the below error trace :-

Crashed: Thread #1 SIGABRT 0x0000000000000000 0 libc.so (Missing BuildId 328a3518945f3e056fc055f1eea1cc35) 1 libc.so (Missing BuildId 328a3518945f3e056fc055f1eea1cc35) 2 libart.so (Missing BuildId 8eb44ac8e1da6fb05559d1b4b0294596) 3 libbase.so (Missing BuildId 36cd125456a5320dd3dcb8cfbd889a1a) 4 libart.so (Missing BuildId 8eb44ac8e1da6fb05559d1b4b0294596) 5 libart.so (Missing BuildId 8eb44ac8e1da6fb05559d1b4b0294596) 6 libart.so (Missing BuildId 8eb44ac8e1da6fb05559d1b4b0294596) 7 libart.so (Missing BuildId 8eb44ac8e1da6fb05559d1b4b0294596) 8 libart.so (Missing BuildId 8eb44ac8e1da6fb05559d1b4b0294596) 9 libart.so (Missing BuildId 8eb44ac8e1da6fb05559d1b4b0294596) 10 libart.so (Missing BuildId 8eb44ac8e1da6fb05559d1b4b0294596) ..... ....