问题
I recently publish my app to play store as a app bundle and everything is working fine except for above mentioned issue. I have added bellow pro-guard rules in my app and it was working fine with my old builds.
#CrashLitics
-keepattributes SourceFile,LineNumberTable
-keep public class * extends java.lang.Exception
Is there any addition pro-guard rules to include when publishing as a app bundle?
回答1:
I contacted the Firebase team. Their reply was to add :app:crashlyticsUploadDeobsRelease (or whichever build flavor you are using) to your gradle arguments. It worked for me.
回答2:
We had a similar issue. With release build from Android Studio, we were getting de-obfuscated crash logs but with CI it was not working. While observing build logs we realized that Task :app:uploadCrashlyticsMappingFileRelease was never called while generating builds from CI. So we updated our build command like this
./gradlew clean :app:bundleRelease :app:uploadCrashlyticsMappingFileRelease
And then everything worked as expected.
来源：https://stackoverflow.com/questions/53699547/firebase-crashlytics-crash-reports-are-not-de-obfuscated-after-publishing-app-as