Status Update
Comments
ze...@google.com <ze...@google.com>
sg...@google.com <sg...@google.com> #2
sg...@google.com <sg...@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?
pu...@gmail.com <pu...@gmail.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
sg...@google.com <sg...@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?
pu...@gmail.com <pu...@gmail.com> #6
Yes, always run the dex transform non-incrementally is another workaround.
ky...@gmail.com <ky...@gmail.com> #7
pu...@gmail.com <pu...@gmail.com> #8
I guess so, could you give it a try?
pu...@gmail.com <pu...@gmail.com> #9
Anyway, what about issue, I've tried a lot of attempts to fix and helped only turn off jacoco transformation `useJacocoTransformInstrumentation = false`.
What was changed in agp 7.4.x from 7.3.1 that break this?
ja...@gmail.com <ja...@gmail.com> #10
Are you referring to
(Regarding What was changed in agp 7.4.x from 7.3.1 that break this?
: I don't know, my theory is that some of your code has changed too when updating AGP, which exposed the Jacoco bug. Please post your comments in that issue if you'd like to continue discussing this.)
fl...@gmail.com <fl...@gmail.com> #11
Edit: we were actually not applying the patch correctly, so this was user error.
We've been running with a patched version of DexingTransformer.kt for about a week but are still seeing the issue. First I tried commenting out @CacheableTransform
on DexingNoClasspathTransform
, but after devs were still experiencing the error, I tried reverting that change and instead applying what I'd suggested in
Is there any other workaround or additional information I can provide to help debug? At first I thought it's perhaps the patched version of DexingTransformer.kt
wasn't being picked up, but I confirmed that it was by throwing an exception inside of doTransform
.
ap...@google.com <ap...@google.com> #12
Regarding the non-cacheable fix: Can you check if it actually takes effect (i.e., the transform outputs are not cached)? Maybe comment out @CacheableTransform
in the BaseDexingTransform
class too?
Regarding the non-incremental fix: Note that the stacktrace in
at com.android.build.gradle.internal.dependency.BaseDexingTransform.processIncrementally(DexingTransform.kt:227)
at com.android.build.gradle.internal.dependency.BaseDexingTransform.doTransform(DexingTransform.kt:137)
Please check your stacktrace after applying the non-incremental fix:
- If it still shows
processIncrementally
, that means the fix was not applied successfully. - If it shows
processNonIncrementally
, that is probably a different bug.
cl...@google.com <cl...@google.com> #13
Thanks! I did confirm we were not applying the patch correctly (as you pointed out, processIncrementally
was in the callstack) but we are now. I will report back if we're still having issues. Appreciate the support.
sg...@google.com <sg...@google.com> #15
Is it possible to cherry-pick changes to AGP 8.0?
ap...@google.com <ap...@google.com> #16
Thanks, but I'm afraid that it's a bit late for AGP 8.0.
(Btw, as mentioned at
ap...@google.com <ap...@google.com> #17
cl...@google.com <cl...@google.com> #18
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Studio Koala | 2024.1.1 Canary 6
- Android Gradle Plugin 8.5.0-alpha06
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
pu...@gmail.com <pu...@gmail.com> #19
cl...@google.com <cl...@google.com>
er...@gmail.com <er...@gmail.com> #20
pu...@gmail.com <pu...@gmail.com> #21
This issue is fixed in AS Ladybug 2024.1.3 Canary 1, as it uses R8 8.7.1-dev
(Interestingly this fix is not mentioned in the issue fixed list).
So if you had forced R8 8.6.12-dev
in your settings.gradle
, you can remove it now.
an...@google.com <an...@google.com> #22
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Studio Koala | 2024.1.1 Patch 2
- Android Gradle Plugin 8.5.2
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
he...@gmail.com <he...@gmail.com> #23
* Android Studio Koala | 2024.1.1 Patch 2
* Android Gradle Plugin 8.4.0
sg...@google.com <sg...@google.com> #24
In response to
Description
I just upgraded from Koala 2024.1.2 Canary 5 to Canary 6 (which was just released), which upgraded AGP to
8.6.0-alpha06
and R8 to8.6.6-dev
.Since then, a Gradle sync of my project fails with in
java.lang.Error: Unexpected backport missing from Android U: java.util.stream.DoubleStream java.util.stream.DoubleStream.iterate(double, java.util.function.DoublePredicate, java.util.function.DoubleUnaryOperator)
.Here's the full gradle trace below.
Note that a
gradle assembleRelease
on the command line fails the same when it reaches thelintVitalAnalyzeRelease
task.I tried to configure the build to use the latest R8 release at this time (8.6.8-dev), but the error is the same.
If you need more info, let me know.