You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've been seeing an error in the Play console for a while but it's increased significantly since our last app update. Not sure why as it's still using Delphi 12.1 with the same components as the previous build. The only change was an update to the latest Kastri sources but I can't see anything new in the Firebase and Admob sources to cause this.
It looks like this is related to the Admob banner component we use in Kastri, or maybe the firebase libraries. We're still using Firebase 10.
We aren't using ads lite either (as far as I know) so no idea why this is even happening unless it's a red herring.
I wanted to seek help as it's now reporting over 1000 crashes in the past 7 days which is messing with our crash stats and likely losing user confidence.
The call stack is:
Exception java.lang.NoClassDefFoundError:
at androidx.work.impl.WorkManagerImpl. (WorkManagerImpl.java:222)
at androidx.work.impl.WorkManagerImpl.initialize (WorkManagerImpl.java:198)
at androidx.work.WorkManager.initialize (WorkManager.java:210)
at com.google.android.gms.ads.internal.util.WorkManagerUtil.zzb (com.google.android.gms:play-services-ads-lite@@22.2.0:1)
at com.google.android.gms.ads.internal.util.WorkManagerUtil.zze (com.google.android.gms:play-services-ads-lite@@22.2.0:2)
at com.google.android.gms.ads.internal.util.zzbq.zzbE (com.google.android.gms:play-services-ads-lite@@22.2.0:3)
at com.google.android.gms.internal.ads.zzatp.onTransact (com.google.android.gms:play-services-ads-base@@22.2.0:3)
at android.os.Binder.transact (Binder.java:1054)
at m.ant.bh (:com.google.android.gms.policy_ads_fdr_dynamite@[email protected]:8)
at com.google.android.gms.ads.nonagon.offline.buffering.c.a (:com.google.android.gms.policy_ads_fdr_dynamite@[email protected]:82)
at com.google.android.gms.ads.nonagon.offline.buffering.h.b (:com.google.android.gms.policy_ads_fdr_dynamite@[email protected]:5)
at m.cjm.run (:com.google.android.gms.policy_ads_fdr_dynamite@[email protected]:30)
at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:641)
at java.lang.Thread.run (Thread.java:923)
Gemini is suggestion it's due to workmanager in the default Delphi 12.1 setup not including the R classes.
I can't reproduce this on any of my test devices. They all show ads without a problem and no logcat errors.
The crash is being reported on a range of device types and Android versions.
"The app is crashing because it cannot find a necessary resource from the AndroidX WorkManager library. Specifically, the androidx.work.R$bool class, which contains boolean resources used by the library, is not being found when the WorkManager is being initialized. This is happening during an operation related to Google Mobile Ads, as suggested by the presence of classes like com.google.android.gms.ads.internal.util.WorkManagerUtil in the stack trace. This indicates that the Google Mobile Ads SDK is attempting to utilize the WorkManager, but the WorkManager library, or a required part of it, seems to be missing or inaccessible at runtime."
This sounds like the R.jar for workmanager may need including but thought Delphi 12.1 did this automatically for the workmanager 2.7.0 library included by default.
Any help would be gratefully appreciated.
The text was updated successfully, but these errors were encountered:
Does Play Console report the device model and Android version?
Gemini is suggestion it's due to workmanager in the default Delphi 12.1 setup not including the R classes.
I see no errors in the logs regarding R classes. This:
Exception java.lang.NoClassDefFoundError:
at androidx.work.impl.WorkManagerImpl. (WorkManagerImpl.java:222)
at androidx.work.impl.WorkManagerImpl.initialize (WorkManagerImpl.java:198)
at androidx.work.WorkManager.initialize (WorkManager.java:210)
at com.google.android.gms.ads.internal.util.WorkManagerUtil.zzb (com.google.android.gms:play-services-ads-lite@@22.2.0:1)
Suggests that the package containing ads-lite is incompatible with the one containing WorkManager, which is work-runtime-2.7.0.jar (in Delphi 12.2), which is compatible according to this:
Nothing has been changed with the default libraries for 12.1 in my app so whatever this is, not sure why something is missing.
I might try to use Codex to download the ad-lite framework again and see if anything is different.
So hopefully, using the Add Android Package function of Codex (or whatever other process you use to generate R classes) to include this one may solve the issue. If I had one of those devices, I'd be able to test it :-)
We've been seeing an error in the Play console for a while but it's increased significantly since our last app update. Not sure why as it's still using Delphi 12.1 with the same components as the previous build. The only change was an update to the latest Kastri sources but I can't see anything new in the Firebase and Admob sources to cause this.
It looks like this is related to the Admob banner component we use in Kastri, or maybe the firebase libraries. We're still using Firebase 10.
We aren't using ads lite either (as far as I know) so no idea why this is even happening unless it's a red herring.
I wanted to seek help as it's now reporting over 1000 crashes in the past 7 days which is messing with our crash stats and likely losing user confidence.
The call stack is:
Exception java.lang.NoClassDefFoundError:
at androidx.work.impl.WorkManagerImpl. (WorkManagerImpl.java:222)
at androidx.work.impl.WorkManagerImpl.initialize (WorkManagerImpl.java:198)
at androidx.work.WorkManager.initialize (WorkManager.java:210)
at com.google.android.gms.ads.internal.util.WorkManagerUtil.zzb (com.google.android.gms:play-services-ads-lite@@22.2.0:1)
at com.google.android.gms.ads.internal.util.WorkManagerUtil.zze (com.google.android.gms:play-services-ads-lite@@22.2.0:2)
at com.google.android.gms.ads.internal.util.zzbq.zzbE (com.google.android.gms:play-services-ads-lite@@22.2.0:3)
at com.google.android.gms.internal.ads.zzatp.onTransact (com.google.android.gms:play-services-ads-base@@22.2.0:3)
at android.os.Binder.transact (Binder.java:1054)
at m.ant.bh (:com.google.android.gms.policy_ads_fdr_dynamite@[email protected]:8)
at com.google.android.gms.ads.nonagon.offline.buffering.c.a (:com.google.android.gms.policy_ads_fdr_dynamite@[email protected]:82)
at com.google.android.gms.ads.nonagon.offline.buffering.h.b (:com.google.android.gms.policy_ads_fdr_dynamite@[email protected]:5)
at m.cjm.run (:com.google.android.gms.policy_ads_fdr_dynamite@[email protected]:30)
at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:641)
at java.lang.Thread.run (Thread.java:923)
Gemini is suggestion it's due to workmanager in the default Delphi 12.1 setup not including the R classes.
I can't reproduce this on any of my test devices. They all show ads without a problem and no logcat errors.
The crash is being reported on a range of device types and Android versions.
"The app is crashing because it cannot find a necessary resource from the AndroidX WorkManager library. Specifically, the androidx.work.R$bool class, which contains boolean resources used by the library, is not being found when the WorkManager is being initialized. This is happening during an operation related to Google Mobile Ads, as suggested by the presence of classes like com.google.android.gms.ads.internal.util.WorkManagerUtil in the stack trace. This indicates that the Google Mobile Ads SDK is attempting to utilize the WorkManager, but the WorkManager library, or a required part of it, seems to be missing or inaccessible at runtime."
This sounds like the R.jar for workmanager may need including but thought Delphi 12.1 did this automatically for the workmanager 2.7.0 library included by default.
Any help would be gratefully appreciated.
The text was updated successfully, but these errors were encountered: