Thousands of strange crashes in the new version of the Google Play console
The ANR and Crash section in the Google Play Console was recently updated to display more ANR and Crashes (automatically collected from users who selected).
I have found many strange new crashes on different Android versions and devices:
1) Most common (thousands of occurrences per week), ClassNotFoundException without class name:
java.lang.RuntimeException:
at android.app.LoadedApk.makeApplication(LoadedApk.java:509)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4657)
at android.app.ActivityThread.access$1400(ActivityThread.java:159)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1376)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:176)
at android.app.ActivityThread.main(ActivityThread.java:5419)
at java.lang.reflect.Method.invokeNative(Method.java:0)
at java.lang.reflect.Method.invoke(Method.java:525)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1046)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:862)
at dalvik.system.NativeStart.main(NativeStart.java:0)
Caused by: java.lang.ClassNotFoundException:
at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:64)
at java.lang.ClassLoader.loadClass(ClassLoader.java:501)
at java.lang.ClassLoader.loadClass(ClassLoader.java:461)
at android.app.Instrumentation.newApplication(Instrumentation.java:992)
at android.app.LoadedApk.makeApplication(LoadedApk.java:504)
2) The most common (hundreds), RuntimeException which seems to be related to admob (com.google.android.gms.ads.internal. *):
java.lang.RuntimeException:
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2377)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2429)
at android.app.ActivityThread.access$800(ActivityThread.java:151)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1342)
at android.os.Handler.dispatchMessage(Handler.java:110)
at android.os.Looper.loop(Looper.java:193)
at android.app.ActivityThread.main(ActivityThread.java:5333)
at java.lang.reflect.Method.invokeNative(Method.java:0)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:828)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:644)
at dalvik.system.NativeStart.main(NativeStart.java:0)
Caused by: java.lang.IllegalStateException:
at com.google.android.gms.ads.internal.zzj.a(zzj.java:322)
at com.google.android.gms.ads.internal.client.ak.onTransact(ak.java:98)
at android.os.Binder.transact(Binder.java:361)
at com.google.android.gms.internal.zzet$zza$zza.zza(zzet.java:0)
at <OR>.zza(zzet.java:0)
at <OR>.zza(zzet.java:0)
...
at <OR>.zza(zzet.java:0)
...
Notes:
-
the stack trace is very long and contains many methods, with the line number always being 0
-
the app uses Proguard
-
lib folder architecture
3) a bunch of other exceptions with the same traces (many methods with line number 0)
My questions:
- Are you experiencing similar reports?
- How relevant are these reports? I mean, I should get more direct user reviews. Is it possible that these are "silent" failures?
- Are there any information issues / fixes?
source to share
I managed to reduce its appearance by adding these lines to the Proguard file:
-keep class android.app.Application
-keep class <<MyPackage>>.MyApplication
which can be shortened to:
-keep class * extends android.app.Application
As per Android source code, I assume it fixed the first issue.
I also updated all my libraries to the latest versions (Google Play Services 11.0.2, support lib 25.4.0) which should have fixed the second one.
UPDATE: It doesn't fix the problem completely. I got a lot fewer cases, but there are some more.
source to share
The first error looks like a multiple dex issue. Make sure you have the correct implementation. Or if you have .so files in the libs folder, make sure they cover all processor architectures. If it still happens, check the proguard file
The second error concerns versions of Google Play services. Your app requires a higher service version, and the device does not. It needed to be updated or make sure it also has gaming services. You can search the internet for Google Play availability information for more information.
Good luck.
Emre
source to share