[Bug]: 5.4.0 - SyncJobService.onStopJob - Caused by java.lang.NullPointerException com.onesignal.core.internal.application.impl.ApplicationService.getAppContext (ApplicationService.kt:40)

[michael-winkler]

What happened?

 Fatal Exception: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
       at android.app.job.JobServiceEngine$JobHandler.handleMessage(JobServiceEngine.java:183)
       at android.os.Handler.dispatchMessage(Handler.java:107)
       at android.os.Looper.loopOnce(Looper.java:257)
       at android.os.Looper.loop(Looper.java:342)
       at android.app.ActivityThread.main(ActivityThread.java:9638)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:619)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:929)
        

 Caused by java.lang.reflect.InvocationTargetException:
       at java.lang.reflect.Constructor.newInstance0(Constructor.java)
       at java.lang.reflect.Constructor.newInstance(Constructor.java:343)
       at com.onesignal.common.services.ServiceRegistrationReflection.resolve(ServiceRegistration.kt:85)
       at com.onesignal.common.services.ServiceProvider.getServiceOrNull(ServiceProvider.kt:75)
       at com.onesignal.common.services.ServiceProvider.getService(ServiceProvider.kt:65)
       at com.onesignal.common.services.ServiceRegistrationReflection.resolve(ServiceRegistration.kt:78)
       at com.onesignal.common.services.ServiceProvider.getAllServices(ServiceProvider.kt:53)
       at com.onesignal.common.services.ServiceRegistrationReflection.resolve(ServiceRegistration.kt:68)
       at com.onesignal.common.services.ServiceProvider.getServiceOrNull(ServiceProvider.kt:75)
       at com.onesignal.common.services.ServiceProvider.getService(ServiceProvider.kt:65)
       at com.onesignal.internal.OneSignalImp.getService(OneSignalImp.kt:330)
       at com.onesignal.OneSignal.getService(OneSignal.java:264)
       at com.onesignal.core.services.SyncJobService.onStopJob(SyncJobService.kt:61)
       at android.app.job.JobService$1.onStopJob(JobService.java:123)
       at android.app.job.JobServiceEngine$JobHandler.handleMessage(JobServiceEngine.java:179)
       at android.os.Handler.dispatchMessage(Handler.java:107)
       at android.os.Looper.loopOnce(Looper.java:257)
       at android.os.Looper.loop(Looper.java:342)
       at android.app.ActivityThread.main(ActivityThread.java:9638)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:619)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:929)
        

And now the relevant lines:

Caused by java.lang.NullPointerException:
       at com.onesignal.core.internal.application.impl.ApplicationService.getAppContext(ApplicationService.kt:40)
       at com.onesignal.core.internal.preferences.impl.PreferencesService.getSharedPrefsByName(PreferencesService.kt:229)
       at com.onesignal.core.internal.preferences.impl.PreferencesService.get(PreferencesService.kt:129)
       at com.onesignal.core.internal.preferences.impl.PreferencesService.getString(PreferencesService.kt:37)
       at com.onesignal.common.modeling.ModelStore.load(ModelStore.kt:170)
       at com.onesignal.common.modeling.SimpleModelStore.<init>(SimpleModelStore.kt:23)
       at com.onesignal.core.internal.config.ConfigModelStore.<init>(ConfigModelStore.kt:8)
       at java.lang.reflect.Constructor.newInstance0(Constructor.java)
       at java.lang.reflect.Constructor.newInstance(Constructor.java:343)
       at com.onesignal.common.services.ServiceRegistrationReflection.resolve(ServiceRegistration.kt:85)
       at com.onesignal.common.services.ServiceProvider.getServiceOrNull(ServiceProvider.kt:75)
       at com.onesignal.common.services.ServiceProvider.getService(ServiceProvider.kt:65)
       at com.onesignal.common.services.ServiceRegistrationReflection.resolve(ServiceRegistration.kt:78)
       at com.onesignal.common.services.ServiceProvider.getAllServices(ServiceProvider.kt:53)
       at com.onesignal.common.services.ServiceRegistrationReflection.resolve(ServiceRegistration.kt:68)
       at com.onesignal.common.services.ServiceProvider.getServiceOrNull(ServiceProvider.kt:75)
       at com.onesignal.common.services.ServiceProvider.getService(ServiceProvider.kt:65)
       at com.onesignal.internal.OneSignalImp.getService(OneSignalImp.kt:330)
       at com.onesignal.OneSignal.getService(OneSignal.java:264)
       at com.onesignal.core.services.SyncJobService.onStopJob(SyncJobService.kt:61)
       at android.app.job.JobService$1.onStopJob(JobService.java:123)
       at android.app.job.JobServiceEngine$JobHandler.handleMessage(JobServiceEngine.java:179)
       at android.os.Handler.dispatchMessage(Handler.java:107)
       at android.os.Looper.loopOnce(Looper.java:257)
       at android.os.Looper.loop(Looper.java:342)
       at android.app.ActivityThread.main(ActivityThread.java:9638)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:619)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:929)

Steps to reproduce?

Firebase crash report

What did you expect to happen?

No null pointer

OneSignal Android SDK version

5.4.0

Android version

15

Specific Android models

Samsung Galaxy A54 5G

Relevant log output

-

Code of Conduct

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

[jkasten2]

@michael-winkler thanks for reporting, can you add a few more details to help us narrow down this issue?

1. What percentage and occurrences of this crash are you seeing?
2. What percentage of the crashes are happening in the background vs the foreground?
3. Are you able to reproduce the issue yourself?

[michael-winkler]

I dont have more informations. That's all I see from Firebase

[tlahtinen-mlb]

Is there an ETA on a fix for this issue?

[jinliu9508]

Thank you for reporting this issue and providing the stack trace. It appears to have been introduced in version 5.4.0, and we are actively working on a permanent fix.

@michael-winkler @tlahtinen-mlb — could you confirm whether this behavior started occurring after upgrading to 5.4.0? In the meantime, upgrading to 5.4.1, which includes a rollback, should solve the issue.

[michael-winkler]

Yes correct. It started with 5.4.0 and is gone with 5.4.1