Fixed
Status Update
No update yet.
Comments
ja...@gmail.com
Related:
ga...@google.com
Until resource processing API is added to the R8, AGP can handle resources by simply copying them. This will match the default Proguard behavior.
ga...@google.com
I've uploaded ag/I654e91d006c8a47d7c5e5eb3661434da5002fe18 to just copy the Java resources to the output.
ga...@google.com
This is now fixed in the plugin. There is more work to be done in R8 regarding Java resources, but we should track that in a separate bug.
Fixed in: 3.2.0-alpha07.
Fixed in: 3.2.0-alpha07.
ja...@gmail.com
I don't see this as working in alpha 7, for what it's worth. I'll check again in alpha 8.
Or maybe I'll figure out how to get the latest from master onto my project's classpath.
Or maybe I'll figure out how to get the latest from master onto my project's classpath.
ga...@google.com
The CL missed the 3.2.0-alpha07 and alpha08 cutoff, so it should be in AGP 3.2.0-alpha09.
Description
OkHttp bundles a small .gz file as a Java resource inside its jar. The configuration for ProGuard passes these through untouched by default. I could have sworn that this used to be mentioned on their website, but I can't seem to find it now. Regardless, it is a regression.
Repro:
* Clone
* Checkout SHA abd633fbd39fdcd3db1146f07cda859aea250904
* Build release APK: ./gradlew assembleRelease
* List APK contents: unzip -l frontend/android/build/outputs/apk/release/sdk-search-release.apk
* Notice the lack of okhttp/ folder.
To compare with ProGuard:
* Checkout SHA dcdaa1adfb6ac5bf93450663dc095fc7e92db9ff
* Build release APK: ./gradlew assembleRelease
* List APK contents: unzip -l frontend/android/build/outputs/apk/release/sdk-search-release.apk
* Notice the presence of okhttp/ folder.