Fix LazyClassKey proguard file issues. #4556
Closed
+0
−0
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.
Fix LazyClassKey proguard file issues.
test.FooModule
wastestFooModule_LazyClassKeys.pro
and is nowtest_FooModule_LazyClassKeys.pro
).writeResource
call ([KSP] Incremental symbol processing not working (or working poorly) #4549).StringBuilder
was declared outside module for-loop, which could lead to duplicate entries across proguard rules for different modules.ClassName#toString()
usage toClassName#canonicalName()
, sincetoString()
is ambiguous and will silently break things when we migrate toXClassName
.Fixes #4549
RELNOTES=Fixes #4549: Fixes incremental processing for LazyClassKey proguard files by adding the originating element to the
writeResource
call.