Status Update
No update yet.
Comments
xa...@google.com
ws...@gmail.com
(reposting under work account)
We have been hitting this issue constantly. Is it possible to configure those tasks to be non cacheable as a workaround or is that only possible inside of AGP?
hm...@google.com
hm...@google.com
Currently the only way to disable caching for dexing transforms is to patch AGP manually by providing a patched DexTransform.kt file in buildSrc. Please see
ws...@gmail.com
Thanks. Ignoring potential build perf impacts, if we essentially commented out the processIncrementally block in DexingTransform.kt and always ran non-incrementally, would that workaround this issue?
an...@google.com
Yes, always run the dex transform non-incrementally is another workaround.
an...@google.com
an...@google.com
I guess so, could you give it a try?
Description
After upgrading to AGP 8.5, we're seeing many more
mergeDebugResourcetasks being run. It's having a large negative impact on our build times -- we're now downloading ~9GB of artifacts from our Gradle remote build cache, whereas before it was 1GB, and most of that increase is frommergeDebugResources.This is reproduced by running
./gradlew compileDebugSources.I believe this is caused by this commit:https://cs.android.com/android-studio/platform/tools/base/+/03860fa78241c5d41556868241e2abd74bce42f0
It appears that
mergeDebugResourcesis always run now, regardless of yourunitTestOptions.includeAndroidResourcessetting.Studio Build: N/A Version of Gradle Plugin: 8.5.1 Version of Gradle: 8.7 Version of Java: 17.0.5 OS: N/A