IssueTracker

In the following execution:

(dexing means dexing artifact transform)
build A:
dexing lib-0.1.87 (cacheKey = A) -> produces lib-0.1.87/classes.dex -> add to cache => cache entry main1
dexing lib-0.1.87 for test (cacheKey = B) -> produces lib-0.1.87/classes.dex -> add to cache => cache entry test1

build B:
dexing lib-0.1.90 (cacheKey = A) -> produces lib-0.1.90/classes.dex -> add to cache (e.g cache is not available or similar) => cache entry main2
dexing lib-0.1.90 for test (cacheKey = B) -> produces lib-0.1.90/classes.dex -> add to cache (e.g cache is not available or similar) => cache entry test2

==========
build C:
dexing lib-0.1.90 (cacheKey = A) => get entry main1 => lib-0.1.87/classes.dex
dexing lib-0.1.90 (cacheKey = B) => get entry test2 => lib-0.1.90/classes.dex

Build C will not have correct android test runtime classpath. It is expected that lib-0.1.90 should only be packaged in the main (tested) APK, but it will also be packged in the android test APK. This is because AGP fails to remove lib-0.1.90 from the test runtime classpath because subtraction logic relies on removing the same ComponentArtifactIdentifier and the same files (as-in the same paths on the file system), but here:

• ComponentArtifactIdentifier for the main artifact is group:lib:0.1.90,filename=lib-0.1.87 and the test artifact is group:li:0.1.90,filename=lib-0.1.90
• output produced by the artifact transform is not the same

We need to modify AGP artifact transforms to:

• have at least NAME_ONLY path sensitivity for artifact transform inputs in order to avoid this issue.
• do not use input artifact name as part of the output path (however, this is bad because it makes error messages and debugging more difficult as all dex files will have paths like $hash/transformed/dex/classes.dex.

At the same time, it feels like Gradle should probably not make file name part of the ComponentArtifactIdentifier.