Nan

Hi @sebastinto, An update that I am able to run your project and receive the same error of `java.util.concurrent.ExecutionException: kotlin.UninitializedPropertyAccessException: lateinit property notificationManager has not been initialized`, and that changing...

Hi @lemeshkevich, thanks for your post, it makes sense to me. The goal with initializing WorkManager ourselves is if we detect there is not one and we are about to...

One internal report: 1. Not using custom WorkManagerInitializer and not disabling the default. No multiprocess. 2. The app developer has 8 `` tags in the Merged Manifest, 4 of which...

Hi @toseefhaiderkhansugguu, Another thing that stands out is that you can reproduce this crash, which is a big step forward because we have not heard reports of successful reproduction. >...

We saw the response from the Google representative, but they may not completely understand how `OneSignal-Android-SDK` is used in applications, or how the SDK uses `WorkManager`. It didn’t help us...

Hey @hayk888997, Good suggestion. Multiprocess support dependency is something that end users of OneSignal can add to their own Android Manifest if their app uses multiprocess. This rare crash we...

Hi @willyric17, Thank you for reporting this update, and I apologize for the delay in responding. The `WorkManager is already initialized` crash is something I thought may be possible after...

Hi @maoryadin, thanks for reaching out with your question. If `getDeviceState()` is called too early it will be `null` or not available. There is a server call to register the...

Hi @maoryadin, `addSubscriptionObserver` should be added after `OneSignal.initWithContext`. Did you test and it is not being triggered for you?

Hi @jt274 sorry for the delayed response. There have been numerous backend fixes since August, so it may have been fixed. Are you still seeing this 500 response anymore? I'll...