Status Update
No update yet.
Comments
rm...@google.com
Thank you for your feedback. Team may reach out for more feedback in reproducing or triaging this issue.
xa...@google.com
The screenshot shows that we use the path to AAPT as an input for the MergeResources task. Because this path will differ on mac/win/linux this makes the task caching no compatible for cross OS consumer and producer (think linux based CI contributing to the cache while all the consumers are on MacBooks).
We should fix this to instead use the version of AAPT as a @Input.
We should fix this to instead use the version of AAPT as a @Input.
je...@google.com
Change-Id: I30cb9d47ef5d1a6b750d25813e89cb439333d14a
Description
As you can see from the attached screencap (from a Gradle Enterprise build comparison of two builds, one on Linux, the other on OSX), this input is different depending on the environment in which it runs.
The example is from a real-world Android project with a size of about 130 kLOC Kotlin, ~50 modules, and support for ~70 languages (so, very many string resource files; I'm not sure if this is relevant). On this project, the fact that these tasks aren't cacheable across the OS boundary adds ~30s to a clean build. This is a four-minute build with a cold daemon, so it's not insignificant.