API 'variant.getExternalNativeBuildTasks()' is obsolete

Question

I have updated my android studio. After that my Crashlytics create the problem. is it problem with crashlytics? or How can I solve this?

This is error

API 'variant.getExternalNativeBuildTasks()' is obsolete and has been 
replaced with 'variant.getExternalNativeBuildProviders()'.
It will be removed at the end of 2019.
For more information, see https://d.android.com/r/tools/task-configuration- 
avoidance.
To determine what is calling variant.getExternalNativeBuildTasks(), use - 
Pandroid.debug.obsoleteApi=true on the command line to display a stack 
trace.
Affected Modules: app

Austerity

I guess it's related to their plugins, and we can not really do anything – Miyokomizar

Possible duplicate of variantOutput.getPackageApplication() is obsolete – Baptize

@MartinZeitler How can it is duplicate. Please Read the question carefully. I already mention Crashlytics. Your issue may be migration. – Austerity

@Masum down-voted your question, too... because I'm not the one who did not read "carefully". and my issue isn't migration, but people who post duplicates, without having researched "carefully". – Baptize

Answer 1

This has been fixed in the latest release of the Fabric gradle plugin, 1.28.0. Have this in your top-level build.gradle:

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

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

Rightminded

I am using classpath 'io.fabric.tools:gradle:1.28.1. Still getting same warning. – Campbell

Answer 2

You can add

android.debug.obsoleteApi=true

to the gradle.properties file and it will show you stack trace, so you can determine what module is using obsolete APIs

However, this is considered as a warning at the moment, not an error. It's just annoying to see everytime you sync gradle . In the future modules will be updated & this warning will be gone

Hope this helps :)

Asch

What about when I am releasing apk file. – Austerity

Works for me. This is not an error, just a warning. – Asch

Answer 3

Probably now is late, but it helped me:

  apply plugin: 'com.android.application'
  apply plugin: 'io.fabric'
  apply plugin: 'kotlin-android'
  apply plugin: 'kotlin-android-extensions'

The problem was with apply plugin: 'io.fabric' I just had to comment this line and after it worked

apply plugin: 'com.android.application'
//apply plugin: 'io.fabric'
apply plugin: 'kotlin-android'
apply plugin: 'kotlin-android-extensions'

It happens after I updated Android Studio to 3.3.0.

Or you can downgrade to Android Studio 3.2.1.

Dody

This is bad advice imo. Doing so removes Crashlytics. – Shanika

Answer 4

It's caused by Fabric's plugin needed for Crashlytics.

Commenting out apply plugin: 'io.fabric' resolves the issue. So the only option is to wait until Google devs will fix Fabric's plugin

Viscose