Use AAR & dependency's Proguard files instead of replicating their rules #3865
Labels
bug
End user-perceivable behaviors which are not desirable.
Impact: Low
Low perceived user impact (e.g. edge cases).
Issue: Needs Clarification
Indicates that an issue needs more detail in order to be able to be acted upon.
Z-ibt
Temporary label for Ben to keep track of issues he's triaged.
We have a lot of Proguard rules for the Bazel build, but ideally we should generate a single Proguard file from all of our dependencies (which I think Gradle via AGP mostly does). bazelbuild/bazel#4467 seems related, but it's not clear to me yet if that will actually provide a means to solve this problem.
The text was updated successfully, but these errors were encountered: