Fixed ProGuard rules for obfuscation to work correctly #2983
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 current rules only apply if the companion class is called
Companion
. If obfuscation is triggered, the rule does not work and the staticCompanion
field is not kept, which breaks the lookup of a companion.A rule has also been added that preserves the named companion class name and field, as they must match to correctly search for the named companion in runtime.
Fixes #2976