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

Question

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?

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](https://d.android.com/r/tools/task-configuration-avoidance)? — Michael Dodd, Sep 23 '18 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. — Michael Dodd, Sep 23 '18 at 20:45
Look at this answer. https://stackoverflow.com/questions/52412023/api-variant-getexternalnativebuildtasks-is-obsolete-and-has-been-replaced-wi/54566866#54566866 — Rahul Kushwaha, Feb 07 '19 at 05:33
Please see https://stackoverflow.com/questions/52412023/api-variant-getexternalnativebuildtasks-is-obsolete-and-has-been-replaced-wi/55193824#55193824 — David Figueroa, Mar 26 '19 at 00:25
This is still an issue with `4.3.1` and can be tracked at https://github.com/google/play-services-plugins/issues/65. Using version `4.2.0` in `build.gradle (Project)` seems like the most viable solution. — Asghar Musani, Sep 06 '19 at 16:35

Ewoks · Answer 1 · 2019-01-16T09:37:49.707

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

edited Jan 16 '19 at 09:37

answered Jan 16 '19 at 09:30

Ewoks

12,285
8
58
67

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](https://github.com/groovy/groovy-android-gradle-plugin) (for Spock tests). – AutonomousApps Jan 21 '19 at 18:53
2

This is the right answer. Who upvoted the gradle version update? – Pier Betos Feb 06 '19 at 05: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? – Billyjoker Mar 06 '19 at 16:22
@Billyjoker 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 – Ewoks Mar 07 '19 at 16:43
1

Really helpful. In my case it was the Hugo plugin. – AlvaroSantisteban Mar 21 '19 at 15:47
6

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 https://medium.com/@xabaras/automatically-copying-proguard-mapping-file-to-apk-build-directory-d7eed285632 – Someone Somewhere Apr 26 '19 at 11:58

score 83 · Accepted Answer · edited Jul 12 '19 at 13:55

83

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'
    }
}

edited Jul 12 '19 at 13:55

Naveed Ahmad

6,627
2
58
83

answered Apr 16 '19 at 08:32

Muhammad Noman

1,842
19
14

After upgrading the Fabric Gradle version Rebuild your project then your issue will be resolved. – Muhammad Noman Apr 18 '19 at 15:14
this is not the answer. See Ewoks answer. – Someone Somewhere Apr 26 '19 at 12:02
2

This is also a correct answer, the easy way to solve the facing problem. – Muhammad Noman Apr 30 '19 at 05:13
5

I have now `classpath 'io.fabric.tools:gradle:1.29.0'`. What should I do? – Faizan Mubasher Jun 29 '19 at 12:25
7

@FaizanMubasher try downgrade your google service to 4.2 – Infinite Loops Jul 03 '19 at 11:20
4

@InfiniteLoops suggestion to downgrade to 4.2 seems to work. – HondaGuy Jul 10 '19 at 16:17
@HondaGuy yeah that's my current version as of now. – Infinite Loops Jul 14 '19 at 00:50
1

Upgraded Fabric to 1.31.0 & Downgraded Google Services to 4.2.0 Solved – Mukeshkumar S Jul 31 '19 at 07:58
Fabric is no longer used, use Firebase Crashlytics. – Abhinav Saxena Dec 23 '21 at 13:09

score 63 · Answer 3 · answered Jun 30 '19 at 09:30

63

In my case, it was caused from gms services 4.3.0. So i had to change it to:

com.google.gms:google-services:4.2.0

I have found this by running:

gradlew sync -Pandroid.debug.obsoleteApi=true

in terminal. Go to view -> tool windows -> Terminal in Android Studio.

answered Jun 30 '19 at 09:30

Numan Karaaslan

1,365
1
17
25

in Ubuntu, unable to run this command how i can do in ubuntu. asking to install package and i install that package still i am not able to run. is there any other way? – Vasudev Vyas Jul 02 '19 at 08:40
3

I just changed my gms google service to 4.2 and the warning disappeared thanks. – Infinite Loops Jul 03 '19 at 11:19
2

@VasudevVyas if in android Studio, just add `./` before the command, that is if the terminal is set to the root of your android project. Otherwise you'll have to cd to the root of the project. – Guanaco Devs Jul 04 '19 at 15:27
3

Why should I downgrade google-services dependency. It's not a solution. – Ahamadullah Saikat Jul 06 '19 at 09:19
4

@AhamadullahSaikat this will probably be fixed in the future releases. Then you can upgrade it again. This is a workaround until it's fixed by google. – Numan Karaaslan Jul 10 '19 at 17:26

score 34 · Answer 4 · answered Sep 23 '18 at 21:03

34

This is just a warning and it will probably be fixed before 2019 with plugin updates so don't worry about it. I would recommend you to use compatible versions of your plugins and gradle.

You can check your plugin version and gradle version here for better experience and performance.

https://developer.android.com/studio/releases/gradle-plugin

Try using the stable versions for a smooth and warning/error free code.

answered Sep 23 '18 at 21:03

Harshil Shah

537
4
15

25

It actually is more insidious than just a warning - it effects code editor and prevents you from searching references to classes. – IgorGanapolsky Oct 02 '18 at 10:30
this is not only in dev/canary editions, also in stable happen that, but, i think is a warning that with newer updates will be fixed. – Marlon López Nov 04 '18 at 18:57
1

@HarshilShah there is no guarantee that problematic plugin will ever be updated. Developers might never even know about the issue. Because of that the best we can do is following: https://stackoverflow.com/a/54213973/304270 – Ewoks Jan 23 '19 at 09:49

score 24 · Answer 5 · answered Jul 13 '19 at 06:52

I also faced the same issue. And after searching for a while, I figured it out that the warning was arising because of using the latest version of google-services plugin (version 4.3.0). I was using this plugin for Firebase functionalities in my application by the way. All I did was to downgrade my google-services plugin in buildscript in the build.gradle(Project) level file as follows:

buildscript{
    dependencies {
       // From =>
       classpath 'com.google.gms:google-services:4.3.0'
       // To =>
       classpath 'com.google.gms:google-services:4.2.0'
    }
}

I upgraded to 4.3.2 without this warning coming back. – tagy22 Oct 09 '19 at 10:17 — tagy22, Oct 09 '19 at 10:17

score 17 · Answer 6 · answered Aug 20 '19 at 09:07

1) Add android.debug.obsoleteApi=true to your gradle.properties. It will show you which modules is affected by your the warning log.

2) Update these deprecated functions.

variant.javaCompile to variant.javaCompileProvider
variant.javaCompile.destinationDir to variant.javaCompileProvider.get().destinationDir

score 10 · Answer 7 · edited Jul 17 '19 at 01:38

10

Change your Google Services version from your build.gradle:

dependencies {
  classpath 'com.google.gms:google-services:4.2.0'
}

edited Jul 17 '19 at 01:38

shizhen

12,251
9
52
88

answered Jul 17 '19 at 00:22

Bahman Omidipour

101
1
2

1

I'm on 4.3.0 and the issue is still there. – wesley franks Jul 31 '19 at 21:11
@wesleyfranks the same. But if I switch to 4.2.0 I don't have the problem anymore... – diAz Aug 02 '19 at 10:04
I'm on 4.3.1 and the issue is still there – pvalle Aug 23 '19 at 03:00

score 8 · Answer 8 · edited Nov 15 '18 at 08:38

8

This is a warning spit out by build tools for two reasons.
1. One of the plugin is relying on Task instead of TaskProvider, there is nothing much we can do.
2. You have configured usage of task, where as it supports TaskProvider.

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

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

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

Look out for snippets as below & update.

android {
    <library|application>Variants.all { variant ->
        /* Disable Generating Build config */
        // variant.generateBuildConfig.enabled = true // <- Deprecated
        variant.generateBuildConfigProvider.configure {
            it.enabled = true // Replacement
        }
    }
}

Similarly, find usages of 'variant.getJavaCompile()' or 'variant.javaCompile', 'variant.getMergeResources()' or 'variant.mergeResources'. Replace as above.

More information at Task Configuration Avoidance

edited Nov 15 '18 at 08:38

Louis CAD

10,965
2
39
58

answered Sep 25 '18 at 18:01

VenomVendor

15,064
13
65
96

1

This happens in every Android Studio project. Nothing to do with snippets you mentioned... – IgorGanapolsky Sep 28 '18 at 10:29
2

@IgorGanapolsky, It would also happen in terminal. Try executing `./gradlew`. This has nothing to do with AS, it is in build tools. Upgrade/downgrade to `com.android.tools.build:gradle:3.2.0` & execute `./gradlew`. This will not come. – VenomVendor Sep 28 '18 at 15:55
Did not find ```variant.generateBuildConfig.enabled``` in my project. I still get the above warning – kbsbng Feb 13 '19 at 03:01
Did not find ```variant.generateBuildConfig.enabled``` in my project. I still get the above warning – kbsbng Feb 13 '19 at 03:01
@VenomVendor This is the most useful answer as per my problem, can you still help with this code snippet? https://codeshare.io/G6ogzk – Raghav Satyadev Feb 20 '19 at 07:10
@RaghavSatyadev It is from android build tools, `output.outputFile` calls deprecated API. This is just a warning, you can still use it. – VenomVendor Feb 20 '19 at 18:22
@VenomVendor I know, but at some point I have to update it. So was asking – Raghav Satyadev Feb 21 '19 at 05:09
@RaghavSatyadev You need not update, when android build tools update, this warning will go away :) – VenomVendor Feb 22 '19 at 16:05
We're now at gradle plugin 3.5.3 and this warning remains. I tried replacing `javaCompile` with `javaCompileProvider`, and it works even though AS does not offer any auto-complete for it. However, the provider that is returned does not have the same properties as the old task. Example: `groovy.lang.MissingPropertyException: Could not get unknown property 'source' for provider(task compileReleaseJavaWithJavac, class com.android.build.gradle.tasks.AndroidJavaCompile) of type org.gradle.api.internal.tasks.DefaultTaskContainer$TaskCreatingProvider_Decorated.` – JHH Jan 28 '20 at 19:51
Is there a 1-1 migration guide for how to use the provider instead? I think the "task config avoidance" page was quite unclear. – JHH Jan 28 '20 at 19:51

erluxman · Answer 9 · 2019-10-22T11:34:20.707

5

Upgrading the Kotlin (Plugin and stdLib) version to 1.3.1 solved that warning in my case. Update the Kotlin version in whole project by replacing existing Kotlin version with :

ext.kotlin_version = '1.3.50'

edited Oct 22 '19 at 11:34

answered Nov 17 '18 at 04:16

erluxman

18,155
20
92
126

ext.kotlin_version = '1.3.10' or '1.3.50' – Pushkin Oct 22 '19 at 09:41
this was my issue. before was `ext.kotlin_version = '1.2.71'` .. Changed it to the answer above and it worked fine! -- i deleted my `/android` and `/ios` folders and then ran `flutter create .` to rebuild the Flutter app and it placed `ext.kotlin_version = '1.2.71'` in my `build.gradle` – MaylorTaylor Oct 23 '19 at 02:21

score 5 · Answer 10 · edited Feb 03 '19 at 15:54

5

Downgrading the version of Gradle worked for me:

classpath 'com.android.tools.build:gradle:3.2.0'

edited Feb 03 '19 at 15:54

סטנלי גרונן

2,917
23
46
68

answered Feb 03 '19 at 11:21

Naimish Verma

51
1
2

5

downgrading is never an option – Roshana Pitigala Apr 11 '19 at 13:42
This is the answer what I want .Thank you! – linjiejun Jul 18 '19 at 03:27
downgrading is fine in certain circumstances – martinseal1987 Dec 06 '19 at 15:27
Of course it will. This is no brainer! But how long when you run out of downgrades? – sud007 Nov 22 '21 at 06:29

score 4 · Answer 11 · answered Oct 10 '18 at 09:16

4

Go back from classpath 'com.android.tools.build:gradle:3.3.0-alpha13' to classpath 'com.android.tools.build:gradle:3.2.0'

this worked for me

answered Oct 10 '18 at 09:16

Eben Watts

141
6

6

that's just temporal workaround cause you can't stay forever on 3.2.0, especially when final 3.3.0 is already out – Ewoks Jan 23 '19 at 16:50
downgrade gradle version is not an option! . – Jorgesys Feb 19 '19 at 16:54

score 4 · Answer 12 · edited Jan 23 '19 at 09:41

4

Updating gradle to gradle:3.3.0

The default 'assemble' task only applies to normal variants. Add test variants as well.

android.testVariants.all { variant ->
    tasks.getByName('assemble').dependsOn variant.getAssembleProvider()
}

also comment apply fabric

//apply plugin: 'io.fabric'

edited Jan 23 '19 at 09:41

Ewoks

12,285
8
58
67

answered Jan 15 '19 at 14:36

Krste Moskov

157
2
6

1

What are the "normal" variants? What is android.testVariants.all {...} code for (what is the purpose of it)? Where is this quoted text from? Can you please update the answer? – Ewoks Jan 16 '19 at 10:00
I've changed Manifest path for chrashlytics `crashlytics { manifestPath = "$buildDir/intermediates/aapt_friendly_merged_manifests/debug/processDebugManifest/aapt/AndroidManifest.xml" }` – A.N.R.I Jan 16 '19 at 10:56
1

@Ewoks normal variants are build variants (debug/release) they using a specific set of rules..you can set many different variants (flavors).. Additionally, you can create testing source sets that target specific build variants. – Krste Moskov Jan 17 '19 at 10:05
I know about flavours but not sure that this applies here and how it is related. That's why I asked if you can update the answer by clarifying what source did you quote and to fix formatting (guess you mixed formatting of code with comment) – Ewoks Jan 17 '19 at 12:09
read title of post "WARNING: API 'variant.getJavaCompile()' is obsolete and has been replaced with 'variant.getJavaCompileProvider()'" i have the same and that's the way how ive fix.. – Krste Moskov Jan 18 '19 at 00:15
1

There is no guarantee that fabric was the source of the issue at all. Actually with this "solution" we have no clue where was the issue. In addition, there is no explanation why to do anything with testVariants and how is that related?!? That's why original answer of @KrsteMoskov is misleading and apply just to specific use case if it solves anything at all. To help you get "on board" I formatted your answer properly and left the content as you wrote it, so others can decide if this is useful for them – Ewoks Jan 23 '19 at 09:46

score 4 · Answer 13 · edited Jul 08 '19 at 09:26

4

Update fabric plugin to the latest in project level Gradle file (not app level). In my case, this line solved the problem

classpath 'io.fabric.tools:gradle:1.25.4'

to

classpath 'io.fabric.tools:gradle:1.29.0'

edited Jul 08 '19 at 09:26

Ramesh R

7,009
4
25
38

answered Apr 11 '19 at 06:22

Bibaswann Bandyopadhyay

3,389
2
31
30

score 3 · Answer 14 · answered Feb 06 '19 at 09:06

3

In my case

build.gradle(Project)

was

ext.kotlin_version = '1.2.71'

updated to

ext.kotlin_version = '1.3.0'

looks problem has gone for now

answered Feb 06 '19 at 09:06

Samir

6,405
5
39
42

That's strange. I updated to 1.4.0 and it appeared. Maybe after upgrade. :) – CoolMind Sep 03 '20 at 15:04

score 2 · Answer 15 · answered Jan 20 '19 at 09:12

2

In my case, I had to comment out com.google.firebase.firebase-crash plugin:

apply plugin: 'com.android.application'
// apply plugin: 'com.google.firebase.firebase-crash' <== this plugin causes the error

It is a bug since Android Studio 3.3.0

answered Jan 20 '19 at 09:12

Anggrayudi H

14,977
11
54
87

2

For me it's happens because I'm using `oss-licenses-plugin` – Mikhail Jan 22 '19 at 16:08

score 2 · Answer 16 · edited Mar 10 '19 at 09:36

2

if I remove this row from application gradle:

apply plugin: 'io.fabric'

error will not appear anymore.

Reference link github

edited Mar 10 '19 at 09:36

Mahdi Moqadasi

2,029
4
26
52

answered Jan 27 '19 at 13:19

Muhammad Waleed

2,517
4
27
75

1

DO NOT DO THIS otherwise Crashlytics will stop working. This is just hiding the problem. – Roger Oba Aug 06 '19 at 04:29

score 2 · Answer 17 · edited Jan 29 '19 at 07:30

2

When the plugin detects that you're using an API that's no longer supported, it can now provide more-detailed information to help you determine where that API is being used. To see the additional info, you need to include the following in your project's gradle.properties file:

android.debug.obsoleteApi=true

edited Jan 29 '19 at 07:30

Sohil R. Memon

9,404
1
31
57

answered Jan 29 '19 at 06:42

Hamed safari

295
4
6

where build,gradle or app.gradle – Jithish P N Dec 26 '19 at 09:42
just search for gradle.properties file in your project – Hamed safari Dec 28 '19 at 14:20

Adarsh Vijayan P · Answer 18 · 2019-08-07T05:37:09.660

2

Migrate your project to androidX.

dependencies are upgraded to androidX. so if you want to use androidX contents migrate your project to androidX.

With Android Studio 3.2 and higher, you can quickly migrate an existing project to use AndroidX by selecting Refactor > Migrate to AndroidX from the menu bar.

Downgrading dependencies may fix your problem this time - but not recommended

edited Aug 07 '19 at 05:37

answered Jul 12 '19 at 06:05

Adarsh Vijayan P

2,964
2
16
27

2

I have AndroidX and i´m still getting the message. – Jorgesys Aug 20 '19 at 19:28

score 1 · Answer 19 · answered Jul 11 '19 at 10:21

This fixed my problem.. All I needed to do was to downgrade my google-services plugin in buildscript in the build.gradle(Project) level file as follows

buildscript{
     dependencies {
        // From =>
        classpath 'com.google.gms:google-services:4.3.0'
        // To =>
        classpath 'com.google.gms:google-services:4.2.0'
        // Add dependency
        classpath 'io.fabric.tools:gradle:1.28.1'
    }
}

Sergio KS · Answer 20 · 2019-01-24T09:08:15.287

0

Here a temporary workaround, If you are using room just upgrade to 1.1.0 or higher

implementation "android.arch.persistence.room:runtime:1.1.0"

it removes this warning for me.

edited Jan 24 '19 at 09:08

answered Oct 18 '18 at 16:30

Sergio KS

33
7

yes, when I update the version, theses warning are gone – Sergio KS Jan 24 '19 at 09:09

score 0 · Answer 21 · answered May 18 '19 at 07:02

keep you Project(not app) Build.gradle dependncies classpath version code is new

 dependencies {
    classpath 'com.android.tools.build:gradle:3.5.0-beta01'
    classpath 'com.novoda:bintray-release:0.8.1'
    // NOTE: Do not place your application dependencies here; they belong
    // in the individual module build.gradle files
}

score 0 · Answer 22 · answered Jul 15 '19 at 13:37

This is a popular question. If you do not use these methods, the solution is updating the libraries. Please update your kotlin version, and all your dependencies like fabric, protobuf etc. If you are sure that you have updated everything, try asking the author of the library.

score 0 · Answer 23 · answered Sep 25 '19 at 08:51

0

Upgrading protobuf-gradle-plugin to version 0.8.10 solved my problem. Replace your existing protobuf with

classpath 'gradle.plugin.com.google.protobuf:protobuf-gradle-plugin:0.8.10'

answered Sep 25 '19 at 08:51

Nejweti

113
2
11

score 0 · Answer 24 · answered Sep 26 '19 at 21:14

That's mostly due to libraries which are obsolete. To check for new updates manually, you should navigate to

Analyze > "Run Inspection By Name"

That should be enough. Another option is to run a gradle dependency update using

./gradlew dependencyUpdates

that will produce a report like this:

:dependencyUpdates

------------------------------------------------------------
: Project Dependency Updates (report to plain text file)
------------------------------------------------------------

The following dependencies are using the latest milestone version:
 - com.github.ben-manes:gradle-versions-plugin:0.15.0

The following dependencies have later milestone versions:
 - com.google.auto.value:auto-value [1.4 -> 1.4.1]
 - com.google.errorprone:error_prone_core [2.0.19 -> 2.0.21]
 - com.google.guava:guava [21.0 -> 23.0-rc1]
 - net.ltgt.gradle:gradle-apt-plugin [0.9 -> 0.10]
 - net.ltgt.gradle:gradle-errorprone-plugin [0.0.10 -> 0.0.11]

...

score 0 · Answer 25 · answered Nov 05 '19 at 06:24

upgrading the google services in project-level build.gradle solved my problem.

After upgrading:

dependencies {
    ...
    classpath 'com.google.gms:google-services:4.3.2'
    // NOTE: Do not place your application dependencies here; they belong
    // in the individual module build.gradle files
}

score 0 · Answer 26 · answered Feb 20 '20 at 08:44

0

I had same problem and it solved by defining kotlin gradle plugin version in build.gradle file.

change this

 classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"

to

 classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:1.3.50{or latest version}"

answered Feb 20 '20 at 08:44

Zahra

2,231
3
21
41

Thanks! So, we also have to change in `app\build.gradle`: `implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk8:1.4.0"`. Then instead of warning we will receive the same message as information. – CoolMind Sep 03 '20 at 15:01

score 0 · Answer 27 · answered Mar 01 '20 at 19:25

In my case I followed this. Summary, in gradle app level: change this :

variant.outputs.all { output ->
    variant.assemble.doLast {
        ....
    }
}

to

variant.outputs.all { output ->
variant.getAssembleProvider().configure() {
    it.doLast { 
        ....
    }
}

score 0 · Answer 28 · answered Mar 26 '23 at 06:24

0

Change this with new provider API as follows

variant.getJavaCompileProvider().configure() { javaCompile ->
      // You have javaCompile object, you can play with it here. 
}

Thanks

answered Mar 26 '23 at 06:24

Minion

964
14
16

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

28 Answers28

Linked

Related