未使用Android App Bundle表示的Google Play崩溃日志 [英] Google Play crash logs not symbolicated with Android App Bundle

问题描述

我们最近更新了我们的应用程序，以使用Android App Bundles（aab），还包括arm64本机库。

这样做以来，我们的崩溃记录了本机代码在 Google Play控制台-> Android Vitals-> ANR和崩溃不能正确表示（java调用栈可以表示正常）。

典型调用栈中的片段如下：

 ＃21 pc 000000000015addc /data/app/com.mycompany.mygame-2/split_config.arm64_v8a.apk 
＃22 pc 0000000000293768 /data/app/com.mycompany .mygame-2 / split_config.arm64_v8a.apk 
＃23 pc 0000000000294cf0 /data/app/com.mycompany.mygame-2/split_config.arm64_v8a.apk 
  

该问题影响armv7和arm64的崩溃。有时，错误将具有正确符号化的调用堆栈，现在大约有10％被正确符号化。在使用AAB和arm64之前，我们已经看到几乎所有的调用栈都正确地用符号表示了。

要解决此问题，我们使用Crashlytics进行了研究，但是很难获得正确的符号表示调用栈也是如此。由于我们之前没有使用过Crashlytics，因此我们很难知道它是否遇到相同的问题，或者我们是否只是错误地设置了Crashlytics。但是，此帖子表示其他用户可能有麻烦

还有其他人遇到类似的困难吗？

有没有已知的解决方法？ p>

是否有人更新过使用AAB，并且在Google Play控制台中没有看到崩溃报告符号的任何问题？

解决方案

编辑：NDK 21 RC1应该可以解决此问题。

这似乎与以下事实有关：本机库保持未压缩状态。 APK。

通过在 gradle.properties 中添加以下选项，可以将其禁用：

  android.bundle.enableUncompressedNativeLibs = false 
  

您需要发布使用此选项构建的新应用程序捆绑包。

We have recently updated our apps to use Android App Bundles (aab) and to also include arm64 native libs.

Since doing so, our crash logs in native code in the 'Google Play Console'->'Android Vitals'->'ANRs & Crashes' are not symbolicating correctly (java callstacks symbolicate fine).

A snippet from a typical callstack looks like this:

  #21  pc 000000000015addc  /data/app/com.mycompany.mygame-2/split_config.arm64_v8a.apk
  #22  pc 0000000000293768  /data/app/com.mycompany.mygame-2/split_config.arm64_v8a.apk
  #23  pc 0000000000294cf0  /data/app/com.mycompany.mygame-2/split_config.arm64_v8a.apk

The issue affects crashes from both armv7 and arm64. Occasionally a bug will have a properly symbolicated callstack, approximately 10% are symbolicated properly now. Prior to the use of AAB and arm64, we were seeing almost all callstacks symbolicated correctly.

To work around this, we investigated using Crashlytics, but had trouble getting a properly symbolicated callstack that way also. As we haven't used Crashlytics before it is difficult for us to know whether it suffers from the same issue or whether we simply setup Crashlytics incorrectly. However, this post indicates that other users may be having trouble with AABs and Crashlytics.

Is anyone else experiencing similar difficulties?

Are there any known workarounds?

Has anyone updated to use AABs and is not seeing any problem with crash report symbolication in the Google Play console?

解决方案

Edit: The NDK 21 RC1 should fix this issue.

This seems related to the fact that native libraries are kept uncompressed in the APK.

By adding the following option in your gradle.properties, you can disable it:

android.bundle.enableUncompressedNativeLibs=false

You'll need to release a new App Bundle built with this option.

这篇关于未使用Android App Bundle表示的Google Play崩溃日志的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！