Fabric crashlytics报告混淆格式的崩溃 [英] Fabric crashlytics reports crashes in obfuscated format

问题描述

我使用crashlytics发送报告，但崩溃并未像这样混淆:

I use crashlytics to send my reports but crashs not de-obfuscated like this:

Fatal Exception: c.a

我在此处读并添加

-keepattributes *Annotation*
-keepattributes SourceFile,LineNumberTable

到我的proguard-rules文件中，没有

to my proguard-rules file and there is no

-printmapping mapping.txt

在我的配置文件中.这是我的build.gradle buildTypes部分:

in my configuration files. this is my build.gradle buildTypes part:

buildTypes {
        release {
            minifyEnabled true
            shrinkResources true
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'

            
        }
        debug_server {
            minifyEnabled false
            debuggable true

            matchingFallbacks = ['release']
        }
        debug {
            applicationIdSuffix '.debug'
            versionNameSuffix '-DEBUG'
            minifyEnabled false

        }

}

不是我所有的崩溃都这样，并且我将crashlytics更新为2.9.4版本.

not all of my crashes are like this and I updated crashlytics to 2.9.4 version.

更新:

我只是跳过了

-keep class com.crashlytics.** { *; }
-dontwarn com.crashlytics.**

因为我不需要在Crashlytics上跳过运行proguard.

as I don't need to skip running proguard on Crashlytics.

UPDATE2 :crashlytics v2.9.9.直到现在还没有固定.我无法检测到错误的真正原因.

UPDATE2: v2.9.9 of crashlytics. Not fixed until now. I can't detect the real cause of bugs.

推荐答案

您必须在 proguard 文件中添加一条额外规则，以保留所有 Kotlin 异常

You have to add an extra rule to proguard file to keep all Kotlin exceptions

-keep公共类*扩展了java.lang.Exception

这篇关于Fabric crashlytics报告混淆格式的崩溃的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！