Crashlytics不会反混淆代码 [英] Crashlytics not deobfusticating code

问题描述

我是Crashlytics的新手，但我遇到的问题是它不会使我的堆栈跟踪模糊.根据Crashlytics的说法，这应该是自动发生的.它应该使用.apk中包含的mappings.txt文件来解密堆栈跟踪.我对整个过程以及如何解决该问题有一些疑问.

I'm new to Crashlytics, and I'm having a problem where it is not de-obfusticating my stack traces. According to Crashlytics this should be happening automatically. It should be using the mappings.txt file that's included in your .apk to decrypt the stack traces. I have a few questions about the whole process, as well as how I should go about solving the problem.

1)默认情况下，mappings.txt文件应与.apk打包正确吗?我正在使用gradle；您必须设置任何选项吗?

1) The mappings.txt file should be packaged with .apk by default correct? I'm using gradle; are there any options that you have to set?

2)我似乎无法从Crashlytics下载stacktrace，也无法更新其仪表板上的mappings.txt文件.这些选项都可能吗?

2) I can't seem to download the stacktrace from Crashlytics, nor update the mappings.txt file on their dashboard. Are either of these options possible?

3)我可以在其他任何地方获取堆栈跟踪信息吗，该应用程序已启用GSM服务.

3) Can I get the stacktraces anywhere else, the application has GSM services enabled.

推荐答案

我遇到了同样的问题，但似乎已通过手动重新安装Crashlytics插件得到了解决.

I had the same problem, but it seems to have been fixed by manually reinstalling the Crashlytics plugin.

https://www.crashlytics.com/downloads/android-studio

(使用Android Studio 1.0 RC2)

(Using Android Studio 1.0 RC2)

Crashlytics现在是 https://fabric.io Fabric现在是 https://firebase.google.com/docs/crashlytics/

Crashlytics is now part of https://fabric.io
Fabric is now part of https://firebase.google.com/docs/crashlytics/

这篇关于Crashlytics不会反混淆代码的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！