Android Question New crash issue after upgrade to 13.40

ppgirl

Member
Licensed User
Longtime User
I found few crash logs from play-services-ads after upgrade to 13.4, Anyone can figure it?

Exception java.lang.NoClassDefFoundError: Failed resolution of: Landroidx/work/impl/WorkDatabase;
at androidx.work.impl.WorkManagerImplExtKt.createWorkManager$default (WorkManagerImplExt.kt:38)
at androidx.work.impl.WorkManagerImplExtKt.createWorkManager (Unknown Source:20)
at androidx.work.impl.WorkManagerImpl.initialize (WorkManagerImpl.java:214)
at androidx.work.WorkManager$Companion.initialize (WorkManager.kt:201)
at androidx.work.WorkManager.initialize (Unknown Source:2)
at com.google.android.gms.ads.internal.util.WorkManagerUtil.zzb (com.google.android.gms:play-services-ads-api@@24.4.0:1)
at com.google.android.gms.ads.internal.util.WorkManagerUtil.zze (com.google.android.gms:play-services-ads-api@@24.4.0:2)
at com.google.android.gms.internal.ads.zzebs.zza (com.google.android.gms:play-services-ads@@24.4.0:8)
at com.google.android.gms.internal.ads.zzebm.zza (Unknown Source:6)
at com.google.android.gms.internal.ads.zzebr.zzb (com.google.android.gms:play-services-ads@@24.4.0:2)
at com.google.android.gms.internal.ads.zzgcy.run (com.google.android.gms:play-services-ads@@24.4.0:6)
at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1156)
at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:651)
at java.lang.Thread.run (Thread.java:1119)
 

Sagenut

Expert
Licensed User
Longtime User
Did you download even New SDK + Resources?
Make a fresh new install following all the steps carefully and download everything new.
https://www.b4x.com/b4a.html
Don't forget to update Configure Paths to new folders.
 
Upvote 0

ppgirl

Member
Licensed User
Longtime User
Did you download even New SDK + Resources?
Make a fresh new install following all the steps carefully and download everything new.
https://www.b4x.com/b4a.html
Don't forget to update Configure Paths to new folders.
Yes, I followed the installation instructions exactly. The issue is not reproducible on all my devices, only a few reports on the Google console.
 
Upvote 0

ppgirl

Member
Licensed User
Longtime User
1. Two logs have a little difference.

2. as Erel said, "The cause of the original issue isn't clear. In a month or two, I plan to release an updated Android SDK and it will hopefully solve it. It looks like a component that should be part of the device installed Google Play Services, is missing." , I found the issue in new 13.40.
 
Upvote 0

ppgirl

Member
Licensed User
Longtime User
There is Play Console information. Android 11-15 , Samsung , Redmi , Oppo and other device.
screenshot.png
 
Upvote 0
Top