marchbold
commented
2 years ago Can you check you have the latest audience_network.dex file in your application? This was updated with the last release as well.
Closed SponsorAds closed 1 year ago
marchbold
commented
2 years ago Can you check you have the latest audience_network.dex file in your application? This was updated with the last release as well.
SponsorAds
commented
2 years ago Yes, I always point directly to the extracted folder instead of moving assets around.
I also did not add the following provider, maybe that could explain it (we don't have devices to test it):
<provider
android:name="androidx.startup.InitializationProvider"
android:authorities="*.androidx-startup"
android:exported="false" >
<meta-data
android:name="androidx.work.WorkManagerInitializer"
android:value="androidx.startup" />
<meta-data
android:name="androidx.lifecycle.ProcessLifecycleInitializer"
android:value="androidx.startup" />
</provider>This provider seems to cause crashes on older ANE versions though, that's why it's not added right now.
marchbold
commented
2 years ago Yes it will crash on older versions. The manifest additions must match the versions of the extensions you are using, you can't mix and match them.
SponsorAds
commented
2 years ago That is obvious and not the issue (it is a big issue for anyone wanting to downgrade and missing older docs).
Do you believe that missing provider would cause these crashes on just one device manufacturer? We obviously can't yolo it and hope for the best.
Such incredibly important breaking changes should be mentioned in change logs. Oftentimes in the past your docs were not up to date, so they're simply no guarantee in the first place. Simply updating sdk numbers or compatibility (according to change logs) should not require going through the entire setup process unless important changes are mentioned.
marchbold
commented
2 years ago We put a lot of work into the extensions so it's always disappointing to hear feedback like this. We are moving towards using apm solely as our distribution means as manually managing manifests is something no one should have to do. And we do not advise anyone use old versions of the extensions, in the mobile world this is generally not feasible as the ecosystem is changing so fast.
From what I can tell from the log I would suggest you double check you are using the latest facebook mediator and audience_network.dex. There were some last minute fixes pushed out that may help here. It is more likely that than a missing provider. Missing the provider would more likely cause things to function incorrectly than cause a crash loading dynamic classes.
github-actions[bot]
commented
1 year ago This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 5 days.
github-actions[bot]
commented
1 year ago This issue was closed because it has been stalled for 5 days with no activity.
We experience vast amount of crashes after updating to your newest ANE version (2022.03.08 [v6.3.0]). It seems to exclusively affect xiaomi (redmi) devices.
Looking at the descriptor, we are missing READ_EXTERNAL_STORAGE permission. Everything else is set up correctly.