fix: Android support AGP9: proguard optimize - #340
Merged
Merged
Conversation
steinv
changed the title
Owner
|
Great PR - much appreciated! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Android SDK ships two default rule sets:
Modern Android builds use R8. Recent AGP/R8 turned getDefaultProguardFile('proguard-android.txt') from a tolerated call into a hard error. The line has been fine for a long time, it only surfaces once a consumer is on an AGP 9 to enforce this, so existing users won't see it until they update AGP.