R8 configuration in Firebase Crashlytics
See original GitHub issueWhat feature would you like to see?
Looking at the official guide, it’s recommended to add the following configuration for “faster, obfuscated build with ProGuard”.
-keep class com.google.firebase.crashlytics.** { *; }
-dontwarn com.google.firebase.crashlytics.**
Is this required also for R8? If yes, could it be bundled with the SDK?
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Firebase Crashlytics Minify R8 Android - Stack Overflow
The app works fine under normal instances but when I try to implement minify and R8. This raises the following error ...
Read more >Get readable crash reports in the Crashlytics dashboard
By default, Firebase Crashlytics automatically processes your debug symbol (dSYM) files to give you deobfuscated and human-readable crash reports.
Read more >When Does Firebase Crashlytics Upload Proguard/R8 ...
This file is produced by ProGuard or R8 when compiling your application. This documentation will show you how to configure obfuscation in. The...
Read more >R8 shuffles the code causing reporting tools to ... - Issue Tracker
When going from proguard to R8, It appears the code is shuffled around, thus, analytics tools like new Relic and firebase, report the...
Read more >Adding crashlytics causes gradle r8 problem - Unity Forum
android.tools.r8.CompilationFailedException: Compilation failed to complete See the Console for details. ... I used Firebase Analytics and Cloud ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @quiro91 - we’ve had these as part of the Crashlytics SDK docs for a long time, and it’s definitely worth asking the question of whether they’re still relevant! I’ll raise this up to the team and see how we can best clean this up. Thanks!
Hi folks - this has been cleaned up, and should be reflected in the official docs soon. Thanks for the report!