Bug (Android) : java.lang.NoClassDefFoundError: ayc

[Liran Barsisa]

I've updated some of Google's repos within the gradle file, and now it looks like this: 

compile 'com.android.support:appcompat-v7:23.4.0'
compile 'com.android.support:recyclerview-v7:23.4.0'
compile 'com.android.support:design:23.4.0'
compile 'com.android.support:cardview-v7:23.4.0'

compile 'com.google.android.gms:play-services-ads:8.4.0'
compile 'com.google.android.gms:play-services-plus:8.4.0'

Recently I get crash reports like this:

java.lang.NoClassDefFoundError: ayc

at ajb.a(:com.google.android.gms.DynamiteModulesA:20)

at po.a(:com.google.android.gms.DynamiteModulesA:536)

at po.a(:com.google.android.gms.DynamiteModulesA:144)

at pm.a(:com.google.android.gms.DynamiteModulesA:312)

at qa.a(:com.google.android.gms.DynamiteModulesA:112)

at ul.onTransact(:com.google.android.gms.DynamiteModulesA:81)

at android.os.Binder.transact(Binder.java:295)

at com.google.android.gms.ads.internal.client.zzu$zza$zza.zzb(Unknown Source)

at com.google.android.gms.ads.internal.client.zzab.zza(Unknown Source)

at com.google.android.gms.ads.BaseAdView.loadAd(Unknown Source)

at com.google.android.gms.ads.AdView.loadAd(Unknown Source)

at com.lb.app_manager.activities.main_activity.b.a.b(SourceFile:259)

at com.lb.app_manager.activities.main_activity.b.a.e(SourceFile:44)

at com.lb.app_manager.activities.main_activity.b.c.a(SourceFile:87)

at com.lb.app_manager.utils.d.b.a(SourceFile:114)

at com.lb.app_manager.utils.d.a.g.run(SourceFile:630)

at android.os.Handler.handleCallback(Handler.java:587)

at android.os.Handler.dispatchMessage(Handler.java:92)

at android.os.Looper.loop(Looper.java:130)

at android.app.ActivityThread.main(ActivityThread.java:3859)

at java.lang.reflect.Method.invokeNative(Native Method)

at java.lang.reflect.Method.invoke(Method.java:507)

at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:890)

at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:648)

at dalvik.system.NativeStart.main(Native Method)

Please fix this.

It didn't occur on the previous versions. Here's my app:

https://play.google.com/store/apps/details?id=com.lb.app_manager

And the crash occurred on Android 2.3.x, on "Motorola Master Touch " .

I've searched the Internet, and found others have reported about this.

http://stackoverflow.com/q/37236208/878126

[John Smith]

me2

[Vu Chau (Mobile Ads SDK Team)]

Hi all,

As you are probably aware, the cause of the crash was SDK-related.  A fix is in the pipeline, and scheduled to go live in the next SDK release.

Vu Chau

Mobile Ads SDK Team

[Liran Barsisa]

What causes this exactly? Is there a workaround?
Does it expected to occur only in specific scenarios, devices or Android versions?

When will a fix be available? Currently users will keep getting crashes...

[Vu Chau (Mobile Ads SDK Team)]

Hi Liran,

The most recent release of Google Play services contains a bug affecting devices running Gingerbread. The SDK team has identified the problem and created a server-side workaround that should eliminate it. These crashes should tail off in the coming days, so you should expect to see fewer and fewer of them going forward.

Vu Chau

Mobile Ads SDK Team

[Liran Barsisa]

I see. Wish all bugs were handled this way :)

Thanks

[neobie]

May I know when will this be fixed? My app is getting bad ratings since few days ago.

I wonder how can Google compensate for this.

[Vu Chau (Mobile Ads SDK Team)]

Hi all,

The fix is server-side and is rolling out to production.  

Vu Chau

Mobile Ads SDK Team

[Piotr Kułaga]

We have problem with DynamiteModule too. It's happen from 2 days and probably drastticly affected on RPM. What can we do with that?

Fatal Exception: java.lang.IllegalArgumentException: Invalid NativeAdManager type. Found: qa; Required: NativeAdManager.

       at alt.a(:com.google.android.gms.DynamiteModulesA:94)

       at pv.run(:com.google.android.gms.DynamiteModulesA:241)

       at android.os.Handler.handleCallback(Handler.java:730)

       at android.os.Handler.dispatchMessage(Handler.java:92)

       at android.os.Looper.loop(Looper.java:177)

       at android.app.ActivityThread.main(ActivityThread.java:5496)

       at java.lang.reflect.Method.invokeNative(Method.java)

       at java.lang.reflect.Method.invoke(Method.java:525)

       at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1225)

       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1041)

       at dalvik.system.NativeStart.main(NativeStart.java) 

[Vu Chau (Mobile Ads SDK Team)]

Hi Piotr,

While this crash might be the same as the previous one reported in this thread, we'd need to be able to reproduce it before confirming that. 

 

Are you able to replicate this crash in our sample example?  If so, what is your ad unit ID?  If not, could you share some code snippets & steps?

A few other pieces of information that might be useful for us (if you have them): 1) The Android API level you are seeing this crash on, as well as 2) the Google Play services version.

Thanks!

Vu Chau

Mobile Ads SDK Team

[K Auzins]

Using the latest Google Play services version:

[Vu Chau (Mobile Ads SDK Team)]

Hi there,

Thanks for the notice.  As you already know, this is a known bug, and we have rolled out a fix server-side.  Until this fix reaches 100%, there might still be remote crashes on Gingerbread devices (Android 2.3 - 2.3.7).  However, going forward, you should see less and less of these crashes.

Vu Chau

Mobile Ads SDK Team

[Piotr Kułaga]

We are using code from Firebase instructions: https://firebase.google.com/docs/admob/android/native-express

We can't replicate this because it's not happening on our devices but in some of end users. We are using 9.0.0 (9080000) version. Stats from crashalitycs:

Devices

samsung

76%

asus

11%

Lenovo

7%

Other…

6%

Operating Systems

4

42%

5

38%

6

20%

[Vu Chau (Mobile Ads SDK Team)]

Hi Piotr,

Thanks for the details!

Would you mind describing to us your use case (how you are implementing native ad express + a bit of actual code)?  Since native ad express is relatively new (inaugurated on I/O 2016), we'd like to get as much feedback as possible from developers like you on how you are using it, so that we can improve the developer experience.  If we see something in your implementation that can be tweaked, we will give some recommendations.

Also, I think it'll be better if we continue the discussion in a new separate thread, since this thread was devoted to another crash.

Vu Chau

Mobile Ads SDK Team

[Piotr Kułaga]

thread with more people with that error

https://groups.google.com/forum/#!category-topic/google-admob-ads-sdk/xcRD_bEL9YA

[Liran Barsisa]

This bug still exists, and I use the latest version of admob:

    compile 'com.google.android.gms:play-services-ads:9.2.1'

It happened to 3 times this week to a device called "Moto G (1st Gen) (falcon_umtsds)" with Android 5.1 on my app:

https://play.google.com/store/apps/details?id=com.lb.app_manager

[Vu Chau (Mobile Ads SDK Team)]

Hi Liran,

Thanks for informing us on that.  Do you have a stack trace?

Vu Chau

Mobile Ads SDK Team

[Liran Barsisa]

Sure, but it's very similar to what others have written:

android.util.AndroidRuntimeException: android.content.pm.PackageManager$NameNotFoundException: com.google.android.webview

at android.webkit.WebViewFactory.getFactoryClass(WebViewFactory.java:174)

at android.webkit.WebViewFactory.getProvider(WebViewFactory.java:109)

at android.webkit.CookieManager.getInstance(CookieManager.java:42)

at com.google.android.gms.ads.internal.util.am.b(:com.google.android.gms.DynamiteModulesA:487)

at com.google.android.gms.ads.internal.c.a(:com.google.android.gms.DynamiteModulesA:542)

at com.google.android.gms.ads.internal.c.a(:com.google.android.gms.DynamiteModulesA:144)

at com.google.android.gms.ads.internal.a.a(:com.google.android.gms.DynamiteModulesA:312)

at com.google.android.gms.ads.internal.o.a(:com.google.android.gms.DynamiteModulesA:116)

at com.google.android.gms.ads.internal.client.ai.onTransact(:com.google.android.gms.DynamiteModulesA:81)

at android.os.Binder.transact(Binder.java:380)

at com.google.android.gms.ads.internal.client.zzu$zza$zza.zzb(Unknown Source)

at com.google.android.gms.ads.internal.client.zzae.zza(Unknown Source)

at com.google.android.gms.ads.BaseAdView.loadAd(Unknown Source)

at com.google.android.gms.ads.AdView.loadAd(Unknown Source)

at com.lb.app_manager.activities.main_activity.b.a.b(SourceFile:259)

at com.lb.app_manager.activities.main_activity.b.a.e(SourceFile:44)

at com.lb.app_manager.activities.main_activity.b.c.a(SourceFile:87)

at com.lb.app_manager.utils.d.b.a(SourceFile:95)

at com.lb.app_manager.utils.d.a.g.run(SourceFile:623)

at android.os.Handler.handleCallback(Handler.java:739)

at android.os.Handler.dispatchMessage(Handler.java:95)

at android.os.Looper.loop(Looper.java:135)

at android.app.ActivityThread.main(ActivityThread.java:5343)

at java.lang.reflect.Method.invoke(Native Method)

at java.lang.reflect.Method.invoke(Method.java:372)

at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:905)

at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:700)

Caused by: android.content.pm.PackageManager$NameNotFoundException: com.google.android.webview

at android.app.ApplicationPackageManager.getPackageInfo(ApplicationPackageManager.java:114)

at android.webkit.WebViewFactory.getFactoryClass(WebViewFactory.java:146)

... 26 more

[Vu Chau (Mobile Ads SDK Team)]

Hi Liran,

The stack trace you posted just now references a different exception (NameNotFoundException), which is different from the original exception you reported on this thread (NoClassDefFoundError).

As far as the NameNotFoundException goes (and going by the package referenced in the crash), we anticipate the fix for this crash to be included in v9.4 of Google Play services.  The issue in question was that ads are not shown on devices that don't have Google Play services.  

Feel free to check with the release notes for an update.

Vu Chau

Mobile Ads SDK Team

[Liran Barsisa]

OK, I thought it's the same because of the "DynamiteModulesA" part. 

I can't see v9.4 in the release notes. Not even 9.3 ...

[Vu Chau (Mobile Ads SDK Team)]

v9.4 is being rolled out into production.  Once it is 100% completed, the change log will reflect that.

[Liran Barsisa]

What happened to 9.3 ? Why the skip of numbers? Reminds me of the huge skips of versions on Chrome And even Android itself (from 6.0.1 to 7) . 

[Vu Chau (Mobile Ads SDK Team)]

The SDK ships with Google Play services, so we (as the SDK team) don't get to decide on the version number.  I will see if I can find an answer from the Play services team :)

Vu

[Liran Barsisa]

Haha, ok. 

Tell them to also go easy on Android versions skipping :)