新版Google Play控制台中发生数千起奇怪的崩溃 [英] Thousands of strange crashes in new Google Play Console version

问题描述

ANR和Google Play控制台的崩溃"部分最近已更新，可以显示更多ANR和崩溃(自动从选择加入的用户中收集).

The ANRs & crashes section of the Google Play Console has been recently updated to display more ANRs & crashes (automatically collected from users that have opted in).

我在各种Android版本和设备上发现了很多奇怪的新崩溃:

I found a lot of strange new crashes, on various Android versions and devices:

1)最常见的(每周发生数千次)，没有任何类名的ClassNotFoundException:

1) The most common (thousands of occurrences a week), a ClassNotFoundException without any 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)最常见(数百个)，似乎与admob(com.google.android.gms.ads.internal.*)相关的RuntimeException:

2) The most common (hundreds), a RuntimeException that seems 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)
  ...

注意:

• 堆栈跟踪非常长，并且包含很多方法，其行号始终为0

• the stack trace is very long and contains a lot of methods with , line number is always 0

该应用使用Proguard

the app uses Proguard

lib文件夹体系结构

lib folder architecture

3)一堆其他具有相同跟踪类型的异常(很多方法的行号为0)

3) a bunch of other exceptions with same kind of traces (a lot of methods with and line number 0)

我的问题是:

• 您是否遇到过类似的报告?
• 这些报告真的相关吗?我的意思是，我应该收到更多直接的用户反馈.是否有可能是无声的"崩溃?
• 是否存在任何已知问题/修复程序?

推荐答案

我通过将以下行添加到Proguard文件中来设法减少了它的出现:

I managed to decrease occurrences of it by adding these lines to my Proguard file:

-keep class android.app.Application
-keep class <<MyPackage>>.MyApplication

可以缩写为:

-keep class * extends android.app.Application

根据android源代码，我认为它已解决了第一个问题.

According to android source code I suppose it fixed the first issue.

我还将所有库更新到了应该修复第二个库的最新版本(Google Play服务11.0.2，支持库25.4.0).

I also updated all my libs to the last versions (Google Play Services 11.0.2, support lib 25.4.0) that should have fixed the second one.

更新:它不能完全解决问题.我的发生次数要少得多，但是仍然有一些.

UPDATE: it doesn't fix the issue completely. I got far less occurrences but there are still some.

这篇关于新版Google Play控制台中发生数千起奇怪的崩溃的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！