I have an Android app built with Android Studio using Gradle, and it uses Proguard for obfuscation. After uploading the .aab file to the Play Store, I noticed that the crashes reported in Firebase Crashlytics are incorrect. Here’s an example of a stack trace:

I have an Android app built with Android Studio using Gradle, and it uses Proguard for obfuscation. After uploading the .aab file to the Play Store, I noticed that the crashes reported in Firebase Crashlytics are incorrect. Here’s an example of a stack trace:

I have an Android app built with Android Studio using Gradle, and it uses Proguard for obfuscation. After uploading the .aab file to the Play Store, I noticed that the crashes reported in Firebase Crashlytics are incorrect. Here’s an example of a stack trace:

I’ve integrated Firebase into my Android game project and have successfully uploaded my libGame.so symbols to Firebase. I’ve also successfully generated crash reports, but when I look at the reports on Firebase Console it only shows the C++ module and line number where the crash occurred. It doesn’t show all the C++ calls that lead up to the crash. How do I get Firebase to show the full stack trace?

I was setting up Firebase Crashlytics by following the Firebase Crashlytics document But when I test crash, there is no crash report show up on my Firebase Crashlytics console. It shows the setup page as shown below :

After updating the Crashlytics Gradle plugin to 3.0.0 it fails with the following: