Gradle Caching issue with AAR exploded resources when bumping dependencies.

[geoff-powell]

Description When bumping a gradle dependency version that is packaged as an AAR with resources, the :preparePaparazziResources task doesn't correctly rerun and uses an older cached version from local/remote gradle cache. This can cause issues loading resources when the exploded aar directory no longer exists in your local gradle home cache directory.

Steps to Reproduce

• Run sample with a dependency that is an AAR and refrence a resource like drawable or string. Using an older version then latest helps illustrate issue.
• Bump dependency version to latest version (test case is version 0.65.0)
• Re-run same test and see error message similar to the following.

  WARNING: Error reading ~/.gradle/caches/transforms-4/2ab825712fd47d3ee279f3575986818d/transformed/android-0.63.0/public.txt: java.nio.file.NoSuchFileException: ~/.gradle/caches/transforms-4/2ab825712fd47d3ee279f3575986818d/transformed/android-0.63.0/public.txt

• View resources.json file in build/intermediates/paparazzi and see old version references in aarExplodedDirs key

Expected behavior Test regenerates resources file and tests always pass.

Additional information:

• Paparazzi Version: 1.3.3
• OS: Mac OS X
• Compile SDK: 33
• Gradle Version: 8.4
• Android Gradle Plugin Version: 8.2.2

[geoff-powell]

Heads up, when debugging incorrect cache hits/misses, -Dorg.gradle.caching.debug=true property is very helpful understand the caching layer without relying on gradle build scans (docs).