Open SergioPoq opened 9 months ago
Thank you for your feedback, we are looking into this issue
I found a tread discussing a similar issue with Airship, they suggested adding the following to your apps AndroidManifest.xml
<provider
android:name="androidx.startup.InitializationProvider"
tools:node="merge"
android:authorities="${applicationId}.androidx-startup"
android:exported="false">
<meta-data
android:name="androidx.work.WorkManagerInitializer"
android:value="androidx.startup"
tools:node="remove" />
<meta-data
android:name="com.urbanairship.AirshipInitializer"
tools:node="remove" />
<meta-data
android:name="com.urbanairship.NoDependencyAirshipInitializer"
android:value="androidx.startup" />
</provider>
I tested this in the BambuserPlayerSDK demo app and it removed the RuntimeException you mentioned above.
Could this solve your issue for now?
The discussion mentioned above also lead me to this issue registered with google. We will keep an eye on it to see if it might lead to an update of the WorkManager that could help us in solving this issue more permanently in the future.
Yes, this solves the issue, thanks! It would be great if this issue gets resolved internally so we don't need to modify other SDKs
Great! Unfortunately the fix above can't be implemented on our side since the Bambuser Player SDK don't use Airship. Resolving the issue on our side would be optimal, and we will continue to look out for a solution but most likely we won't have a fix anytime soon.
When using BambuserPlayerSDK alongside other SDKs using WorkManager (in my case is Airship), the app crashes upon repeated app launches with the following error:
The solution provided in the README is not feasible since I can't control all the WorkManager factories from other SDKs