IssueTracker

(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?

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 https://issuetracker.google.com/169266011#comment27, section on "Workarounds" for an example.

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?

Yes, always run the dex transform non-incrementally is another workaround.

I guess so, could you give it a try?

Are you referring to https://issuetracker.google.com/266109833#comment2? That issue is different from this issue.

(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.)

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 comment #5, but we're still running into the issue.

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.

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 comment #1 is:

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.

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.

Update: We have fixed this issue with this change: https://android.googlesource.com/platform/tools/base/+/03bc950504c4c64cef2b0de377175f02a62e70d3. It will be included AGP 8.1.0-beta01.