Android cache fix Gradle plugin

Some Android plugin versions have issues with Gradle's build cache feature. When applied to an Android project this plugin applies workarounds for these issues based on the Android plugin and Gradle versions.

• Supported Gradle versions: 5.4.1+
• Supported Android Gradle Plugin versions: 3.5.4, 3.6.4, 4.0.1, 4.1.3, 4.2.2, 7.0.2, 7.1.0-alpha11
• Supported Kotlin versions: 1.3.70+

We only test against the latest patch versions of each minor version of Android Gradle Plugin. This means that although it may work perfectly well with an older patch version (say 3.6.2), we do not test against these older patch versions, so the latest patch version is the only version from that minor release that we technically support.

The Android cache fix plugin is compatible with the Gradle Configuration Cache when used in conjunction with Android Gradle Plugin 4.2.0 and above. Using the configuration cache with earlier versions of the Android Gradle Plugin is not supported.

Should I use this?

Take a look at the list of issues especially unresolved issues. If any of these apply to your project, you can use this plugin to solve them.

How can I discover issues?

You can discover issues by using the task input comparison tool in Gradle Enterprise. More information about how to diagnose cache misses here. You can compare the inputs of a build that seeds the build cache - typically CI - with a build that consumes from the build cache like a local developer build.If you discover an issue related to the Android Gradle Plugin, please file an issue in the Android Bug Tracker. You can also file an issue here and we can see if a workaround is possible.

Applying the plugin

This plugin should be applied anywhere the com.android.application or com.android.library plugins are applied. Typically,this can just be injected from the root project's build.gradle (change '2.4.4' to the latest version of the cache fix pluginhere):

plugins {
    id "org.gradle.android.cache-fix" version "2.4.4" apply false
}

subprojects {
    plugins.withType(com.android.build.gradle.api.AndroidBasePlugin) {
        project.apply plugin: "org.gradle.android.cache-fix"
    }
}

plugins {
    id("org.gradle.android.cache-fix") version "2.4.4" apply false
}

subprojects {
    plugins.withType<com.android.build.gradle.api.AndroidBasePlugin>() {
        apply(plugin = "org.gradle.android.cache-fix")
    }
}

Note that if you are currently exporting schemas with the Room annotation processor, you will need to change how you specify the output directory according to the instructions here.

List of issues

You can take a look at the list of issues that the plugin fixes by looking at the classes in org.gradle.android.workarounds. It contains a number of Workaround implementations annotated with @AndroidIssue. The Javadoc has a short description of the problem, and the annotation gives information about when the problem was introduced, what is the first version of the Android plugin that fixes it, and there's a link to the issue on Android's issue tracker:

/**
 * Fix {@link org.gradle.api.tasks.compile.CompileOptions#getBootClasspath()} introducing relocatability problems for {@link AndroidJavaCompile}.
 */
@AndroidIssue(introducedIn = "3.0.0", fixedIn = "3.1.0-alpha06", link = "https://issuetracker.google.com/issues/68392933")
static class AndroidJavaCompile_BootClasspath_Workaround implements Workaround {
    // ...
}

Unresolved Issues

The following caching issues are fixed by the cache fix plugin but unresolved in any current or upcoming preview release of the Android Gradle Plugin as of 21.08.2020.

Please star them if you are experiencing them in your project.

• CompileLibraryResourcesTask is not relocatable: https://issuetracker.google.com/issues/155218379
• DexFileDependenciesTask is not cacheable: https://issuetracker.google.com/160138798
• MergeResources is not relocatable: https://issuetracker.google.com/issues/141301405
• Room annotation processor causes cache misses, doesn't declare outputs, overlapping outputs, etc: https://issuetracker.google.com/issues/132245929

Implementation Notes

RoomSchemaLocationWorkaround

Most of the workarounds in this plugin should apply to your project without any changes. However, one workaroundrequires some extra configuration. The Room schema location workaround allows you to specify an output directory forRoom schema exports without breaking caching for your Java and/or Kapt tasks where the annotation processor has been configured.There are various issues with how this annotation processor works (see https://issuetracker.google.com/issues/132245929and https://issuetracker.google.com/issues/139438151) which this workaround attempts to mitigate. However, in order todo so in a manageable way, it imposes some restrictions:

• The schema export directory must be configured via the "room" project extension instead of as an explicit annotationprocessor argument. If an explicit annotation processor argument is provided, an exception will be thrown, instructingthe user to configure it via the extension:

room {
    schemaLocationDir = file("roomSchemas")
}

room {
    schemaLocationDir.set(file("roomSchemas"))
}

• There can only be a single schema export directory for the project - you cannot configure variant-specific exportdirectories. Schemas exported from different variants will be merged in the directory specified in the "room" extension.

MergeNativeLibs, StripDebugSymbols, MergeJavaResources, MergeSourceSetFolders, BundleLibraryClassesJar and DataBindingMergeDependencyArtifacts Workarounds

It has been observed that caching the MergeNativeLibsTask, StripDebugSymbols, MergeJavaResources, MergeSourceSetFolders, BundleLibraryClassesJar and DataBindingMergeDependencyArtifacts tasks rarely provide any significant positive avoidance savings. In fact, they frequently provide negative savings, especially when fetched from a remote cache node. As such, these workarounds actually disable caching for these tasks.