Fixed
Status Update
Comments
ad...@google.com <ad...@google.com>
tn...@google.com <tn...@google.com>
ji...@google.com <ji...@google.com> #2
deleted
tn...@google.com <tn...@google.com> #3
(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?
tn...@google.com <tn...@google.com> #4
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
an...@google.com <an...@google.com> #5
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?
Description
STEPS TO REPRODUCE:
1. create any kt file
2. type:
buildList {
this += ""
}
Replacing with add("") fixing the issue, but "operator fun" can be more readable in some cases.
------------------
IMPORTANT: Please read
all required information.
------------------
Studio Build:
Android Studio Jellyfish | 2023.3.1 Beta 2
Build #AI-233.14808.21.2331.11608968, built on March 21, 2024
Runtime version: 17.0.10+0-17.0.10b1087.21-11572160 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Version of Gradle Plugin: 8.2.0, 8.4.0-beta02
Version of Gradle: 8.2-bin, 8.6-bin
Version of Java: Azul Zulu 17.0.7, JetBrains runtime 17.0.10
OS: macOS 14.4.1