Crash in WorkerScheduler.startService about android-sdk HOT 12 CLOSED

@jaeopt thanks so much for the quick response- we do not use a custom WorkManager configuration (and therefore do not set Configuration.Provider)

from android-sdk.

@upside-sarah We'll continue looking into the issue and get you updated.

from android-sdk.

@upside-sarah Thanks for sharing. We'll take a look.

from android-sdk.

@upside-sarah can you confirm if you use a custom WorkManager configuration and Configuration.Provider has been set properly? https://developer.android.com/topic/libraries/architecture/workmanager/advanced/custom-configuration

from android-sdk.

@jaeopt we removed this receiver from our manifest as a short-term fix to resolve these crashes in our release, but would love to find a more permanent solution so we can add this behavior back in a future release soon!

from android-sdk.

@upside-sarah it's a good idea. We'll get you updated when we find more info on the issue.

from android-sdk.

@jaeopt Update: we removed all references of EventRescheduler in our latest app version, but we are still seeing this issue reported for that release in the Play Store. Would love any additional guidance here. Thank you!

from android-sdk.

@upside-sarah It does not make sense that EventRescheduler is still called even after the receiver has been removed from the manifest. We'll look into it.
Can you confirm that those new crashes come from EventRescheduler and also if you do not register it programmatically anywhere in your app?

from android-sdk.

@jaeopt I agree that it doesn't make sense 😅

1. confirmed that the issue is coming from EventRescheduler. We're seeing the same stacktrace as before:

Exception java.lang.RuntimeException: Unable to start receiver com.optimizely.ab.android.event_handler.EventRescheduler: java.lang.IllegalStateException: 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.

2. we don't have any references to EventRescheduler in our app (searching the entire codebase for "EventRescheduler" returns nothing)

I don't know if there's some possibility that on upgrade, the previous receiver would be called? Otherwise, I'm unclear as to how this would be triggering.

from android-sdk.

@upside-sarah we found why you get the call even after EventRescheduler link is removed. In SDK 3.10.0+, the receiver is declared in the SDK manifest, which will be automatically merged into your final app manifest (so you do not need to declare the receiver again in your app manifest).

You can disable the receiver from our SDK with this ("remove") in your manifest -

<receiver
      android:name="com.optimizely.ab.android.event_handler.EventRescheduler"
      tools:node="remove">
</receiver>

Let us know if it works for you.

from android-sdk.

Hi @jaeopt- that completely makes sense, we can definitely explicitly remove the EventRescheduler in our next release. Just want to confirm y'all are still looking into a solution for the greater problem (i.e. why declaring the rescheduler leads to a crash?), ideally we wouldn't have this disabled indefinitely. Thank you!

from android-sdk.

Closing this open git issue as fixed per the above. we do have a backlog issue for the long-term fix tied to feature backlog.

from android-sdk.