[Feedback]: Overly broad ProGuard/R8 rules used throughout the library

[gajicm93]

What's on your mind?

I have analyzed my app with the recently introduced R8 Configuration Analyzer and found that 3 out of top 5 files with broadest keep rules come from your library.

E.g. report for the core-5.9.2 artifact is in the attachment.

It would be nice if you revised your R8 rules to be more narrow and target only specific classes/methods that need to be kept for library to work.

Resources to help you:

1. Optimization for library authors
2. YouTube video from Google IO 2026 that explains the issue

Code of Conduct

• I agree to follow this project's Code of Conduct

[sherwinski]

Hey @gajicm93 and thanks for reporting this. Someone from the team will dig into this and get back to you with any updates.