OneSignal-Android-SDK icon indicating copy to clipboard operation
OneSignal-Android-SDK copied to clipboard

[`WorkManager`] java.lang.IllegalStateException com.onesignal.OSNotificationRestoreWorkManager.beginEnqueueingWork

Open albomenti opened this issue 3 years ago • 12 comments

Description:

After migrating to SDK >4 I'm getting this errors on my Play Console, I cant reproduce it myself but userbase can .

Environment

Anything else:

java.lang.IllegalStateException
com.onesignal.OSNotificationRestoreWorkManager.beginEnqueueingWork
java.lang.RuntimeException
java.lang.RuntimeException: 
  at android.app.ActivityThread.performResumeActivity (ActivityThread.java:4789)
  at android.app.ActivityThread.handleResumeActivity (ActivityThread.java:4821)
  at android.app.servertransaction.ResumeActivityItem.execute (ResumeActivityItem.java:52)
  at android.app.servertransaction.TransactionExecutor.executeLifecycleState (TransactionExecutor.java:176)
  at android.app.servertransaction.TransactionExecutor.execute (TransactionExecutor.java:97)
  at android.app.ActivityThread$H.handleMessage (ActivityThread.java:2305)
  at android.os.Handler.dispatchMessage (Handler.java:106)
  at android.os.Looper.loop (Looper.java:257)
  at android.app.ActivityThread.main (ActivityThread.java:8192)
  at java.lang.reflect.Method.invoke (Native Method)
  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:626)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1015)
Caused by: java.lang.IllegalStateException: 
  at androidx.work.impl.WorkManagerImpl.getInstance (WorkManagerImpl.java:36)
  at androidx.work.WorkManager.getInstance (WorkManager.java)
  at com.onesignal.OSNotificationRestoreWorkManager.beginEnqueueingWork (OSNotificationRestoreWorkManager.java:27)
  at com.onesignal.OneSignal.onAppFocusLogic (OneSignal.java:29)
  at com.onesignal.OneSignal.onAppFocus (OneSignal.java:74)
  at com.onesignal.ActivityLifecycleHandler.handleFocus (ActivityLifecycleHandler.java:71)
  at com.onesignal.ActivityLifecycleHandler.onActivityResumed (ActivityLifecycleHandler.java:28)
  at com.onesignal.ActivityLifecycleListener.onActivityResumed (ActivityLifecycleListener.java:4)
  at android.app.Application.dispatchActivityResumed (Application.java:453)
  at android.app.Activity.dispatchActivityResumed (Activity.java:1460)
  at android.app.Activity.onResume (Activity.java:1998)
  at android.app.Instrumentation.callActivityOnResume (Instrumentation.java:1506)
  at android.app.Activity.performResume (Activity.java:8254)
  at android.app.ActivityThread.performResumeActivity (ActivityThread.java:4779)
  at android.app.ActivityThread.handleResumeActivity (ActivityThread.java:4821)
  at android.app.servertransaction.ResumeActivityItem.execute (ResumeActivityItem.java:52)
  at android.app.servertransaction.TransactionExecutor.executeLifecycleState (TransactionExecutor.java:176)
  at android.app.servertransaction.TransactionExecutor.execute (TransactionExecutor.java:97)
  at android.app.ActivityThread$H.handleMessage (ActivityThread.java:2305)
  at android.os.Handler.dispatchMessage (Handler.java:106)
  at android.os.Looper.loop (Looper.java:257)
  at android.app.ActivityThread.main (ActivityThread.java:8192)
  at java.lang.reflect.Method.invoke (Native Method)
  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:626)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1015)

albomenti avatar Oct 14 '21 13:10 albomenti

@albomenti Could you let us know the device models and Android versions you are seeing the crash on?

Also could you provide the error message after "Caused by: java.lang.IllegalStateException:"? The Play console may not show it by default but this would be helpful for us to have.

You noted you are using the OneSignal SDK 4 or greater, can you let us know the exact version?

jkasten2 avatar Oct 19 '21 18:10 jkasten2

@jkasten2 i too have this issue

here is the excpetion

java.lang.IllegalStateException: 
  at androidx.work.impl.WorkManagerImpl.getInstance (WorkManagerImpl.java:140)
  at androidx.work.WorkManager.getInstance (WorkManager.java:180)
  at com.onesignal.OSNotificationWorkManager.beginEnqueueingWork$49ab0f00 (OSNotificationWorkManager.java:82)
  at com.onesignal.NotificationBundleProcessor$3.onResult (NotificationBundleProcessor.java:436)
  at com.onesignal.OSNotificationDataController$5.run (OSNotificationDataController.java:242)
  at java.lang.Thread.run (Thread.java:818)

this crash was from Crash HTC Desire 10 pro Android 6.0 (SDK 23)

other devices are ris41 HTC Desire 10 pro Motorola Moto G (3rd Gen) Samsung Galaxy A51 Others

sdk version this occurs on

Android 6.0 (SDK 23) Android 11 (SDK 30) Android 7.0 (SDK 24) Android 9 (SDK 28

i use com.onesignal:OneSignal:4.6.0

mahmoudElfeel67 avatar Oct 20 '21 22:10 mahmoudElfeel67

ECF6C9C53798143DC5BC4CFC6166EE2F me too!

TaoGEe avatar Oct 29 '21 04:10 TaoGEe

Me too. Same problem

image

123dma avatar Nov 07 '21 18:11 123dma

Putting this note here: Seeing that this IllegalStateException is coming from WorkManagerImpl.getInstance The error message is probably this:

"WorkManager is not initialized properly. You have explicitly disabled WorkManagerInitializer in your manifest, have not manually called WorkManager#initialize at this point, and your Application does not implement Configuration.Provider."

nan-li avatar Nov 07 '21 19:11 nan-li

Hi @mahmoudElfeel67, thanks for sharing the device and Android version information.

  • When did you start experiencing this exception?
  • Did it start occurring after updating OneSignal SDK version to 4.6.0 from a previous version?
  • Are you able to reproduce it yourself?

Hi @TaoGEe and @123dma,

  • Can you provide device and Android versions experiencing the exception?
  • Which OneSignal SDK version are you using?
  • When did you start experiencing this exception?
  • Are you able to reproduce it yourself?

Additional questions:

  • Are you using a custom WorkManager configuration and initialization?
  • Do you have android:multiprocess="true"

nan-li avatar Nov 19 '21 03:11 nan-li

I believe the line references seem to indicate an older version of work-runtime.

Looking at the source code for WorkManagerImpl.java line 140 and WorkManager.java line 180 seem to line up only for androidx.work:work-runtime:2.3.0-alpha02 and below.

It may be worth checking out which version of work-runtime your app is actually using and need to update to a newer version?

nan-li avatar Nov 24 '21 21:11 nan-li

@nan-li my app is using Gradle__androidx_work_work_runtime_2_1_0_aar is that what is causing the issue ? should i force some version ? i cant reprduce the issue

mahmoudElfeel67 avatar Dec 08 '21 20:12 mahmoudElfeel67

Hi @mahmoudElfeel67, it may be worth trying a newer version of androidx.work:work-runtime like 2.7.1.

For context, 2.1.0 was released in July 11, 2019.

nan-li avatar Jan 27 '22 21:01 nan-li

@nan-li

Hi @TaoGEe and @123dma,

  • Can you provide device and Android versions experiencing the exception? Samsung Galaxy A30 Samsung Galaxy A12 Samsung Galaxy A31 Samsung Galaxy A11 Motorola moto g(8) plus
  • Which OneSignal SDK version are you using? 'gradle.plugin.com.onesignal:onesignal-gradle-plugin:[0.12.10, 0.99.99]' implementation 'com.onesignal:OneSignal:[4.0.0, 4.99.99]'
  • When did you start experiencing this exception? image
  • Are you able to reproduce it yourself? No Additional questions:

  • Are you using a custom WorkManager configuration and initialization? No

  • Do you have android:multiprocess="true" No

123dma avatar Mar 29 '22 02:03 123dma

Thank you for the information @123dma and I am sorry for the delayed response.

Can you provide the version of androidx.work:work-runtime you are using?

nan-li avatar Apr 28 '22 22:04 nan-li

androidx.work:work-runtime

Hi @nan-li this version implementation 'androidx.work:work-runtime-ktx:2.7.1'

123dma avatar May 09 '22 11:05 123dma

Hello everyone! Apologies that this issue has gone stale. Much of our work in the last few quarters have been on a new major release where many improvements and enhancements are introduced. We will continue to investigate 4.x.x bugs, though we encourage you to update to our latest release as that will be the most-supported release going forward. Please see our migration guide for full details on upgrading.

If this crash is still a current concern, please let us know and we will investigate further.

jennantilla avatar Mar 13 '24 23:03 jennantilla