WARNING: API 'variant.getJavaCompile()' is obsolete and has been replaced with 'variant.getJavaCompileProvider()'

Asked 23/9, 2018 at 20:36 Answered 26/3, 2023 at 6:24

Solved android android-studio compilation android-gradle-plugin google-fabric

203

Suddenly when Syncing Gradle, I get this error:

WARNING: API 'variant.getJavaCompile()' is obsolete and has been replaced with 'variant.getJavaCompileProvider()'. It will be removed at the end of 2019. For more information, see https://d.android.com/r/tools/task-configuration-avoidance Affected Modules: app

I've got this build.gradle for the app module:

apply plugin: 'com.android.application'

apply plugin: 'kotlin-android'

apply plugin: 'kotlin-android-extensions'
apply plugin: 'com.google.gms.google-services'

apply plugin: 'io.fabric'

android {
    compileSdkVersion 28
    buildToolsVersion "28.0.2"
    defaultConfig {
        applicationId "..."
        minSdkVersion 21
        targetSdkVersion 28
        versionCode 1
        versionName "..."
        testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
        versionNameSuffix = version_suffix

        [...]
    }
    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'

            [...]
        }
        debug {
            [...]
        }
    }
}

dependencies {
    implementation fileTree(include: ['*.jar'], dir: 'libs')
    implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:1.2.61"
    implementation 'androidx.appcompat:appcompat:1.0.0-rc02'
    implementation 'androidx.constraintlayout:constraintlayout:1.1.3'
    implementation "com.android.support:preference-v7:28.0.0"
    testImplementation 'junit:junit:4.12'
    androidTestImplementation 'androidx.test:runner:1.1.0-alpha4'
    androidTestImplementation 'androidx.test.espresso:espresso-core:3.1.0-alpha4'
    implementation 'com.google.android.material:material:1.0.0-rc02'

    [...]
}

I can compile the app correctly, but it's a bit bothering, and as I see it, something will stop working at the end of 2019. Any ideas of what is it and how to solve it?

Issiah answered 23/9, 2018 at 20:36 Comment(6)

Just as a slight nit-pick, a warning is not an error. Even with a warning your code should compile in the same way, whereas an error would cause your build to fail. It's just advanced notice that the current way of doing things may not work in the future, and will likely be fixed with plugin updates. Did you also take the time to read the page linked in the error? – Divorcement 23/9, 2018 at 20:40

My personal feeling is that it's being caused by a plugin that's not been updated to use the new Gradle API yet, which should fix itself in time. – Divorcement 23/9, 2018 at 20:45

Look at this answer. #52412523 – Apterygial 7/2, 2019 at 5:33

Try this. https://mcmap.net/q/93067/-api-39-variant-getexternalnativebuildtasks-39-is-obsolete-and-has-been-replaced-with-39-variant-getexternalnativebuildproviders – Hamo 16/3, 2019 at 5:44

Please see #52412523 – Spheroidal 26/3, 2019 at 0:25

This is still an issue with 4.3.1 and can be tracked at github.com/google/play-services-plugins/issues/65. Using version 4.2.0 in build.gradle (Project) seems like the most viable solution. – Manville 6/9, 2019 at 16:35

This issue is fixed now with update Fabric Gradle version 1.30.0:

Update release: March 19, 2019

Please see this Link: https://docs.fabric.io/android/changelog.html#march-15-2019

Please update your classpath dependency in project level Gradle:

buildscript {
    // ... repositories, etc. ...

    dependencies {
        // ...other dependencies ...
        classpath 'io.fabric.tools:gradle:1.30.0'
    }
}

Cropland answered 16/4, 2019 at 8:32 Comment(9)

After upgrading the Fabric Gradle version Rebuild your project then your issue will be resolved. – Cropland 18/4, 2019 at 15:14

this is not the answer. See Ewoks answer. – Counterfoil 26/4, 2019 at 12:2

This is also a correct answer, the easy way to solve the facing problem. – Cropland 30/4, 2019 at 5:13

I have now classpath 'io.fabric.tools:gradle:1.29.0'. What should I do? – Chaco 29/6, 2019 at 12:25

@FaizanMubasher try downgrade your google service to 4.2 – Considering 3/7, 2019 at 11:20

@InfiniteLoops suggestion to downgrade to 4.2 seems to work. – Sanborn 10/7, 2019 at 16:17

@Sanborn yeah that's my current version as of now. – Considering 14/7, 2019 at 0:50

Upgraded Fabric to 1.31.0 & Downgraded Google Services to 4.2.0 Solved – Crowson 31/7, 2019 at 7:58

Fabric is no longer used, use Firebase Crashlytics. – Ofeliaofella 23/12, 2021 at 13:9

100

I face this issue after updating to 3.3.0

If you are not doing what error states in gradle file, it is some plugin that still didn't update to the newer API that cause this. To figure out which plugin is it do the following (as explained in "Better debug info when using obsolete API" of 3.3.0 announcement):

Add 'android.debug.obsoleteApi=true' to your gradle.properties file which will log error with a more details
Try again and read log details. There will be a trace of "problematic" plugin
When you identify, try to disable it and see if issue is gone, just to be sure
go to github page of plugin and create issue which will contain detailed log and clear description, so you help developers fix it for everyone faster
be patient while they fix it, or you fix it and create PR for devs

Hope it helps others

Beckiebeckley answered 16/1, 2019 at 9:30 Comment(6)

This is the most general, useful answer, in my opinion. In my case, this warning is emitted because of use of the Groovy-Android plugin (for Spock tests). – Florin 21/1, 2019 at 18:53

This is the right answer. Who upvoted the gradle version update? – Narcosynthesis 6/2, 2019 at 5:46

This also worked for me, is there any new on this issue? Meanwhile it is supposed nothing we could to do, is it right? – Fritillary 6/3, 2019 at 16:22

@Fritillary actually there is... Contact developer of problematic plugin is step you need to do. It will not be resolved by itself and maybe not even by developer. In the meantime consider replacing plugin with some newer/modern and reconsider if you really need it, cause there is no guarantee whatsoever that 3rd party plugin will be ever fixed – Beckiebeckley 7/3, 2019 at 16:43

Really helpful. In my case it was the Hugo plugin. – Villon 21/3, 2019 at 15:47

after adding android.debug.obsoleteApi=true, To read the logged details: Go to Build tab at the bottom and within the "Build Output" window, click "Toggle View". When you click that the pretty, colors go away, scroll to the top where it says WARNING: API 'variant.getAssemble()' is obsolete. Then below it, it shows REASON: Called from: ... in my case it was due to medium.com/@xabaras/… – Counterfoil 26/4, 2019 at 11:58

This issue is fixed now with update Fabric Gradle version 1.30.0:

Update release: March 19, 2019

Please see this Link: https://docs.fabric.io/android/changelog.html#march-15-2019

Please update your classpath dependency in project level Gradle:

buildscript {
    // ... repositories, etc. ...

    dependencies {
        // ...other dependencies ...
        classpath 'io.fabric.tools:gradle:1.30.0'
    }
}