Firebase Crashlytics - crash reports won't de-obfuscate
Asked Answered
A

0

6

I have recently integrated Firebase Crashlytics to my KMM app and set up a release build with obfuscation. I followed the official documentation (https://firebase.google.com/docs/crashlytics/get-deobfuscated-reports?platform=android) in order to obtain readable reports in Crashlytics dashboard for obfuscated builds, but I still get obfuscated errors.

Here is my build.gradle.kts release build setup:

   getByName("release") {
        isDebuggable = true
        isMinifyEnabled = true
        configure<com.google.firebase.crashlytics.buildtools.gradle.CrashlyticsExtension> {
            mappingFileUploadEnabled = true
        }
        proguardFiles(
            getDefaultProguardFile("proguard-android-optimize.txt"),
            "proguard/crashlytics.pro"
        )
    }

And my crashlytics.pro file

-keepattributes SourceFile,LineNumberTable        # Keep file names and line numbers.
-keep public class * extends java.lang.Exception  # Optional: Keep custom exceptions.

I am using Firebase BoM version 29.3.0.

Appleton answered 19/4, 2022 at 12:11 Comment(3)
Have you found a solution for this issue yet?Must
I used the latest Firebase version "firebase-bom:31.0.2" and enable mappingFileUploadEnabled to release builds, I'm still getting the obfuscated errors. did you find any solution for this ?Syck
This answer helped me: https://mcmap.net/q/1918728/-firebase-crashlytics-crash-reports-are-not-de-obfuscated-after-publishing-app-as-a-app-bundleOwenowena

© 2022 - 2025 — McMap. All rights reserved.