205

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?

Improve this question
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? Commented Sep 23, 2018 at 20:40
  • 2
    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. Commented Sep 23, 2018 at 20:45
  • Look at this answer. stackoverflow.com/questions/52412023/… Commented Feb 7, 2019 at 5:33
  • Try this. stackoverflow.com/a/55193824/3806413 Commented Mar 16, 2019 at 5:44
  • Please see stackoverflow.com/questions/52412023/… Commented Mar 26, 2019 at 0:25

28 Answers 28

Reset to default
101

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

Improve this answer
Sign up to request clarification or add additional context in comments.

6 Comments

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).
This is the right answer. Who upvoted the gradle version update?
This also worked for me, is there any new on this issue? Meanwhile it is supposed nothing we could to do, is it right?
Really helpful. In my case it was the Hugo plugin.
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/…
|
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' } }
Improve this answer

9 Comments

This is also a correct answer, the easy way to solve the facing problem.
I have now classpath 'io.fabric.tools:gradle:1.29.0'. What should I do?
@FaizanMubasher try downgrade your google service to 4.2
@InfiniteLoops suggestion to downgrade to 4.2 seems to work.
Upgraded Fabric to 1.31.0 & Downgraded Google Services to 4.2.0 Solved
|
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.

Improve this answer

5 Comments

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?
I just changed my gms google service to 4.2 and the warning disappeared thanks.
@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.
Why should I downgrade google-services dependency. It's not a solution.
@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.
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.

Improve this answer

3 Comments

It actually is more insidious than just a warning - it effects code editor and prevents you from searching references to classes.
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.
@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: stackoverflow.com/a/54213973/304270
24

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' } }
Improve this answer

1 Comment

I upgraded to 4.3.2 without this warning coming back.
17

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

Improve this answer

Comments

10

Change your Google Services version from your build.gradle: 

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

3 Comments

I'm on 4.3.0 and the issue is still there.
@wesleyfranks the same. But if I switch to 4.2.0 I don't have the problem anymore...
I'm on 4.3.1 and the issue is still there
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

Improve this answer

10 Comments

This happens in every Android Studio project. Nothing to do with snippets you mentioned...
@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.
Did not find variant.generateBuildConfig.enabled in my project. I still get the above warning
Did not find variant.generateBuildConfig.enabled in my project. I still get the above warning
@VenomVendor This is the most useful answer as per my problem, can you still help with this code snippet? codeshare.io/G6ogzk
|
5

Downgrading the version of Gradle worked for me: 

classpath 'com.android.tools.build:gradle:3.2.0'
Improve this answer

3 Comments

downgrading is never an option
downgrading is fine in certain circumstances
Of course it will. This is no brainer! But how long when you run out of downgrades?
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'
Improve this answer

2 Comments

ext.kotlin_version = '1.3.10' or '1.3.50'
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
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

Improve this answer

2 Comments

that's just temporal workaround cause you can't stay forever on 3.2.0, especially when final 3.3.0 is already out
downgrade gradle version is not an option! .
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'
Improve this answer

6 Comments

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?
I've changed Manifest path for chrashlytics crashlytics { manifestPath = "$buildDir/intermediates/aapt_friendly_merged_manifests/debug/processDebugManifest/aapt/AndroidManifest.xml" }
@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.
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)
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
|
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'
Improve this answer

Comments

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

Improve this answer

1 Comment

That's strange. I updated to 1.4.0 and it appeared. Maybe after upgrade. :)
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

Improve this answer

1 Comment

For me it's happens because I'm using oss-licenses-plugin
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
Improve this answer

2 Comments

where build,gradle or app.gradle
just search for gradle.properties file in your project
2

if I remove this row from application gradle:

apply plugin: 'io.fabric'

error will not appear anymore.

Reference link github

Improve this answer

1 Comment

DO NOT DO THIS otherwise Crashlytics will stop working. This is just hiding the problem.
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

Improve this answer

1 Comment

I have AndroidX and i´m still getting the message.
1

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' } }
Improve this answer

Comments

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.

Improve this answer

1 Comment

yes, when I update the version, theses warning are gone
0

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 }
Improve this answer

Comments

0

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.

Improve this answer

Comments

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'
Improve this answer

Comments

0

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

Analyze > "Run Inspection By Name"

run inspection by name android result

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] ...
Improve this answer

Comments

0

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 }
Improve this answer

Comments

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}"
Improve this answer

1 Comment

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.
0

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 { .... } }
Improve this answer

Comments

0

Change this with new provider API as follows

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

Thanks

Improve this answer

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.