Obsolete
Status Update
No update yet.
Comments
np...@google.com
je...@google.com
cm...@google.com
Luke - am I right in thinking this already fixed in AGP at head?
lu...@google.com
Yes, all Android resource inputs can now only use relative path sensitivity, apart from custom resource directories located outside the project when data binding is enabled. The mentioned inputs in the stacktrace such as resourcesComputer.resources.fastdev.sourceDirectoriesAbsolute have been removed at head.
ke...@twitter.com
Is "head" == AGP 7.3.1?
or 7.3.0?
Could you please look at git history to see which version the fix is in?
lu...@google.com
This change will be present in AGP 8.0.0-alpha01, since this changed happened very recently.
ke...@twitter.com
any chance it could be cherrypicked to 7.3.1 or 7.4? Would be nice to see better remote cache hit rates.
Description
PLEASE READ:
This form is only for reporting bugs found in the Android system while developing Android applications. Use the Developer Tools subcomponent for issues with the developer tools.https://issuetracker.google.com/issues/new?component=192633
Please describe the problem in detail. Be sure to include:
Don't forget to mention which version of Android you're using, and/or which device the problem appears on (model and Android version).
Apple M1 Max
MacOS Monterey 12.5.1
Gradle 7.3.3
AGP 7.2.2
I'm running 03-validate-local-build-caching-different-locations.sh on our app usinghttps://github.com/gradle/gradle-enterprise-build-validation-scripts/blob/main/Gradle.md , this builds the app using different local build cache locations on the same machine.
I'm getting cache misses on the 2nd build due to absolute path usages in
com.android.build.gradle.internal.res.LinkApplicationAndroidResourcesTaskandcom.android.build.gradle.tasks.MergeResources