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





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







88















Suddently 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 correctly the app, 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?










share|improve this question























  • 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?

    – Michael Dodd
    Sep 23 '18 at 20:40






  • 1





    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. stackoverflow.com/questions/52412023/…

    – Rahul Kushwaha
    Feb 7 at 5:33











  • Try this. stackoverflow.com/a/55193824/3806413

    – 0xalihn
    Mar 16 at 5:44











  • Please see stackoverflow.com/questions/52412023/…

    – David Figueroa
    Mar 26 at 0:25


















88















Suddently 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 correctly the app, 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?










share|improve this question























  • 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?

    – Michael Dodd
    Sep 23 '18 at 20:40






  • 1





    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. stackoverflow.com/questions/52412023/…

    – Rahul Kushwaha
    Feb 7 at 5:33











  • Try this. stackoverflow.com/a/55193824/3806413

    – 0xalihn
    Mar 16 at 5:44











  • Please see stackoverflow.com/questions/52412023/…

    – David Figueroa
    Mar 26 at 0:25














88












88








88


12






Suddently 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 correctly the app, 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?










share|improve this question














Suddently 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 correctly the app, 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?







android gradle compilation






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Sep 23 '18 at 20:36









Arnyminer ZArnyminer Z

6261613




6261613













  • 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?

    – Michael Dodd
    Sep 23 '18 at 20:40






  • 1





    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. stackoverflow.com/questions/52412023/…

    – Rahul Kushwaha
    Feb 7 at 5:33











  • Try this. stackoverflow.com/a/55193824/3806413

    – 0xalihn
    Mar 16 at 5:44











  • Please see stackoverflow.com/questions/52412023/…

    – David Figueroa
    Mar 26 at 0:25



















  • 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?

    – Michael Dodd
    Sep 23 '18 at 20:40






  • 1





    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. stackoverflow.com/questions/52412023/…

    – Rahul Kushwaha
    Feb 7 at 5:33











  • Try this. stackoverflow.com/a/55193824/3806413

    – 0xalihn
    Mar 16 at 5:44











  • Please see stackoverflow.com/questions/52412023/…

    – David Figueroa
    Mar 26 at 0:25

















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?

– Michael Dodd
Sep 23 '18 at 20:40





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?

– Michael Dodd
Sep 23 '18 at 20:40




1




1





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







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. stackoverflow.com/questions/52412023/…

– Rahul Kushwaha
Feb 7 at 5:33





Look at this answer. stackoverflow.com/questions/52412023/…

– Rahul Kushwaha
Feb 7 at 5:33













Try this. stackoverflow.com/a/55193824/3806413

– 0xalihn
Mar 16 at 5:44





Try this. stackoverflow.com/a/55193824/3806413

– 0xalihn
Mar 16 at 5:44













Please see stackoverflow.com/questions/52412023/…

– David Figueroa
Mar 26 at 0:25





Please see stackoverflow.com/questions/52412023/…

– David Figueroa
Mar 26 at 0:25












14 Answers
14






active

oldest

votes


















3














This issue is fixed now with update Fabric Gradle version 1.28.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.28.0'
}


}






share|improve this answer
























  • this doesn't work with 1.28.1

    – isudansh
    Apr 18 at 11:32











  • After upgrading the Fabric Gradle version Rebuild your project then your issue will be resolved.

    – M.Noman
    Apr 18 at 15:14



















35














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






share|improve this answer





















  • 1





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

    – AutonomousApps
    Jan 21 at 18:53






  • 2





    This is the right answer. Who upvoted the gradle version update?

    – Pier Betos
    Feb 6 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?

    – Billyjoker
    Mar 6 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 7 at 16:43






  • 1





    Really helpful. In my case it was the Hugo plugin.

    – AlvaroSantisteban
    Mar 21 at 15:47



















32














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.






share|improve this answer



















  • 20





    It actually is more insidious than just a warning - it effects code editor and prevents you from searching references to classes.

    – IgorGanapolsky
    Oct 2 '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 4 '18 at 18:57






  • 9





    it is now an error for me and i cant build app

    – puya ars
    Nov 7 '18 at 12:01






  • 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: stackoverflow.com/a/54213973/304270

    – Ewoks
    Jan 23 at 9:49



















5














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






share|improve this answer





















  • 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 at 3:01











  • Did not find variant.generateBuildConfig.enabled in my project. I still get the above warning

    – kbsbng
    Feb 13 at 3:01











  • @VenomVendor This is the most useful answer as per my problem, can you still help with this code snippet? codeshare.io/G6ogzk

    – Raghav Satyadev
    Feb 20 at 7:10





















4














if I remove this row from application gradle:



apply plugin: 'io.fabric'


error will not appear anymore.



Reference link github






share|improve this answer

































    3














    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






    share|improve this answer



















    • 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 at 16:50











    • downgrade gradle version is not an option! .

      – Elenasys
      Feb 19 at 16:54



















    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






    share|improve this answer



















    • 2





      For me it's happens because I'm using oss-licenses-plugin

      – Mikhail
      Jan 22 at 16:08



















    2














    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'





    share|improve this answer





















    • 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 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 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 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 at 12:09






    • 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 at 9:46



















    1














    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.1'





    share|improve this answer

































      1














      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





      share|improve this answer

































        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.






        share|improve this answer


























        • that's just a temporary workaround for you

          – Basi
          Jan 24 at 5:32













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

          – Sergio KS
          Jan 24 at 9:09



















        0














        Downgrading the version of Gradle worked for me:



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





        share|improve this answer


























        • downgrading is never an option

          – Roshana Pitigala
          Apr 11 at 13:42



















        0














        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






        share|improve this answer































          0














          Update fabric plugin to 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.28.0'





          share|improve this answer
























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f52470044%2fwarning-api-variant-getjavacompile-is-obsolete-and-has-been-replaced-with%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            14 Answers
            14






            active

            oldest

            votes








            14 Answers
            14






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            3














            This issue is fixed now with update Fabric Gradle version 1.28.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.28.0'
            }


            }






            share|improve this answer
























            • this doesn't work with 1.28.1

              – isudansh
              Apr 18 at 11:32











            • After upgrading the Fabric Gradle version Rebuild your project then your issue will be resolved.

              – M.Noman
              Apr 18 at 15:14
















            3














            This issue is fixed now with update Fabric Gradle version 1.28.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.28.0'
            }


            }






            share|improve this answer
























            • this doesn't work with 1.28.1

              – isudansh
              Apr 18 at 11:32











            • After upgrading the Fabric Gradle version Rebuild your project then your issue will be resolved.

              – M.Noman
              Apr 18 at 15:14














            3












            3








            3







            This issue is fixed now with update Fabric Gradle version 1.28.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.28.0'
            }


            }






            share|improve this answer













            This issue is fixed now with update Fabric Gradle version 1.28.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.28.0'
            }


            }







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Apr 16 at 8:32









            M.NomanM.Noman

            26148




            26148













            • this doesn't work with 1.28.1

              – isudansh
              Apr 18 at 11:32











            • After upgrading the Fabric Gradle version Rebuild your project then your issue will be resolved.

              – M.Noman
              Apr 18 at 15:14



















            • this doesn't work with 1.28.1

              – isudansh
              Apr 18 at 11:32











            • After upgrading the Fabric Gradle version Rebuild your project then your issue will be resolved.

              – M.Noman
              Apr 18 at 15:14

















            this doesn't work with 1.28.1

            – isudansh
            Apr 18 at 11:32





            this doesn't work with 1.28.1

            – isudansh
            Apr 18 at 11:32













            After upgrading the Fabric Gradle version Rebuild your project then your issue will be resolved.

            – M.Noman
            Apr 18 at 15:14





            After upgrading the Fabric Gradle version Rebuild your project then your issue will be resolved.

            – M.Noman
            Apr 18 at 15:14













            35














            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






            share|improve this answer





















            • 1





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

              – AutonomousApps
              Jan 21 at 18:53






            • 2





              This is the right answer. Who upvoted the gradle version update?

              – Pier Betos
              Feb 6 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?

              – Billyjoker
              Mar 6 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 7 at 16:43






            • 1





              Really helpful. In my case it was the Hugo plugin.

              – AlvaroSantisteban
              Mar 21 at 15:47
















            35














            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






            share|improve this answer





















            • 1





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

              – AutonomousApps
              Jan 21 at 18:53






            • 2





              This is the right answer. Who upvoted the gradle version update?

              – Pier Betos
              Feb 6 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?

              – Billyjoker
              Mar 6 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 7 at 16:43






            • 1





              Really helpful. In my case it was the Hugo plugin.

              – AlvaroSantisteban
              Mar 21 at 15:47














            35












            35








            35







            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






            share|improve this answer















            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







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Jan 16 at 9:37

























            answered Jan 16 at 9:30









            EwoksEwoks

            10.1k44859




            10.1k44859








            • 1





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

              – AutonomousApps
              Jan 21 at 18:53






            • 2





              This is the right answer. Who upvoted the gradle version update?

              – Pier Betos
              Feb 6 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?

              – Billyjoker
              Mar 6 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 7 at 16:43






            • 1





              Really helpful. In my case it was the Hugo plugin.

              – AlvaroSantisteban
              Mar 21 at 15:47














            • 1





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

              – AutonomousApps
              Jan 21 at 18:53






            • 2





              This is the right answer. Who upvoted the gradle version update?

              – Pier Betos
              Feb 6 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?

              – Billyjoker
              Mar 6 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 7 at 16:43






            • 1





              Really helpful. In my case it was the Hugo plugin.

              – AlvaroSantisteban
              Mar 21 at 15:47








            1




            1





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

            – AutonomousApps
            Jan 21 at 18:53





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

            – AutonomousApps
            Jan 21 at 18:53




            2




            2





            This is the right answer. Who upvoted the gradle version update?

            – Pier Betos
            Feb 6 at 5:46





            This is the right answer. Who upvoted the gradle version update?

            – Pier Betos
            Feb 6 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?

            – Billyjoker
            Mar 6 at 16:22





            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 6 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 7 at 16:43





            @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 7 at 16:43




            1




            1





            Really helpful. In my case it was the Hugo plugin.

            – AlvaroSantisteban
            Mar 21 at 15:47





            Really helpful. In my case it was the Hugo plugin.

            – AlvaroSantisteban
            Mar 21 at 15:47











            32














            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.






            share|improve this answer



















            • 20





              It actually is more insidious than just a warning - it effects code editor and prevents you from searching references to classes.

              – IgorGanapolsky
              Oct 2 '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 4 '18 at 18:57






            • 9





              it is now an error for me and i cant build app

              – puya ars
              Nov 7 '18 at 12:01






            • 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: stackoverflow.com/a/54213973/304270

              – Ewoks
              Jan 23 at 9:49
















            32














            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.






            share|improve this answer



















            • 20





              It actually is more insidious than just a warning - it effects code editor and prevents you from searching references to classes.

              – IgorGanapolsky
              Oct 2 '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 4 '18 at 18:57






            • 9





              it is now an error for me and i cant build app

              – puya ars
              Nov 7 '18 at 12:01






            • 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: stackoverflow.com/a/54213973/304270

              – Ewoks
              Jan 23 at 9:49














            32












            32








            32







            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.






            share|improve this answer













            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.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Sep 23 '18 at 21:03









            Harshil ShahHarshil Shah

            479311




            479311








            • 20





              It actually is more insidious than just a warning - it effects code editor and prevents you from searching references to classes.

              – IgorGanapolsky
              Oct 2 '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 4 '18 at 18:57






            • 9





              it is now an error for me and i cant build app

              – puya ars
              Nov 7 '18 at 12:01






            • 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: stackoverflow.com/a/54213973/304270

              – Ewoks
              Jan 23 at 9:49














            • 20





              It actually is more insidious than just a warning - it effects code editor and prevents you from searching references to classes.

              – IgorGanapolsky
              Oct 2 '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 4 '18 at 18:57






            • 9





              it is now an error for me and i cant build app

              – puya ars
              Nov 7 '18 at 12:01






            • 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: stackoverflow.com/a/54213973/304270

              – Ewoks
              Jan 23 at 9:49








            20




            20





            It actually is more insidious than just a warning - it effects code editor and prevents you from searching references to classes.

            – IgorGanapolsky
            Oct 2 '18 at 10:30





            It actually is more insidious than just a warning - it effects code editor and prevents you from searching references to classes.

            – IgorGanapolsky
            Oct 2 '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 4 '18 at 18:57





            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 4 '18 at 18:57




            9




            9





            it is now an error for me and i cant build app

            – puya ars
            Nov 7 '18 at 12:01





            it is now an error for me and i cant build app

            – puya ars
            Nov 7 '18 at 12:01




            1




            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: stackoverflow.com/a/54213973/304270

            – Ewoks
            Jan 23 at 9:49





            @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

            – Ewoks
            Jan 23 at 9:49











            5














            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






            share|improve this answer





















            • 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 at 3:01











            • Did not find variant.generateBuildConfig.enabled in my project. I still get the above warning

              – kbsbng
              Feb 13 at 3:01











            • @VenomVendor This is the most useful answer as per my problem, can you still help with this code snippet? codeshare.io/G6ogzk

              – Raghav Satyadev
              Feb 20 at 7:10


















            5














            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






            share|improve this answer





















            • 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 at 3:01











            • Did not find variant.generateBuildConfig.enabled in my project. I still get the above warning

              – kbsbng
              Feb 13 at 3:01











            • @VenomVendor This is the most useful answer as per my problem, can you still help with this code snippet? codeshare.io/G6ogzk

              – Raghav Satyadev
              Feb 20 at 7:10
















            5












            5








            5







            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






            share|improve this answer















            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







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Nov 15 '18 at 8:38









            Louis CAD

            6,05822339




            6,05822339










            answered Sep 25 '18 at 18:01









            VenomVendorVenomVendor

            10.7k115483




            10.7k115483








            • 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 at 3:01











            • Did not find variant.generateBuildConfig.enabled in my project. I still get the above warning

              – kbsbng
              Feb 13 at 3:01











            • @VenomVendor This is the most useful answer as per my problem, can you still help with this code snippet? codeshare.io/G6ogzk

              – Raghav Satyadev
              Feb 20 at 7:10
















            • 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 at 3:01











            • Did not find variant.generateBuildConfig.enabled in my project. I still get the above warning

              – kbsbng
              Feb 13 at 3:01











            • @VenomVendor This is the most useful answer as per my problem, can you still help with this code snippet? codeshare.io/G6ogzk

              – Raghav Satyadev
              Feb 20 at 7:10










            1




            1





            This happens in every Android Studio project. Nothing to do with snippets you mentioned...

            – IgorGanapolsky
            Sep 28 '18 at 10:29





            This happens in every Android Studio project. Nothing to do with snippets you mentioned...

            – IgorGanapolsky
            Sep 28 '18 at 10:29




            2




            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





            @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 at 3:01





            Did not find variant.generateBuildConfig.enabled in my project. I still get the above warning

            – kbsbng
            Feb 13 at 3:01













            Did not find variant.generateBuildConfig.enabled in my project. I still get the above warning

            – kbsbng
            Feb 13 at 3:01





            Did not find variant.generateBuildConfig.enabled in my project. I still get the above warning

            – kbsbng
            Feb 13 at 3:01













            @VenomVendor This is the most useful answer as per my problem, can you still help with this code snippet? codeshare.io/G6ogzk

            – Raghav Satyadev
            Feb 20 at 7:10







            @VenomVendor This is the most useful answer as per my problem, can you still help with this code snippet? codeshare.io/G6ogzk

            – Raghav Satyadev
            Feb 20 at 7:10













            4














            if I remove this row from application gradle:



            apply plugin: 'io.fabric'


            error will not appear anymore.



            Reference link github






            share|improve this answer






























              4














              if I remove this row from application gradle:



              apply plugin: 'io.fabric'


              error will not appear anymore.



              Reference link github






              share|improve this answer




























                4












                4








                4







                if I remove this row from application gradle:



                apply plugin: 'io.fabric'


                error will not appear anymore.



                Reference link github






                share|improve this answer















                if I remove this row from application gradle:



                apply plugin: 'io.fabric'


                error will not appear anymore.



                Reference link github







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Mar 10 at 9:36









                Mahdi Moqadasi

                640630




                640630










                answered Jan 27 at 13:19









                Java coderJava coder

                2,12611261




                2,12611261























                    3














                    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






                    share|improve this answer



















                    • 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 at 16:50











                    • downgrade gradle version is not an option! .

                      – Elenasys
                      Feb 19 at 16:54
















                    3














                    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






                    share|improve this answer



















                    • 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 at 16:50











                    • downgrade gradle version is not an option! .

                      – Elenasys
                      Feb 19 at 16:54














                    3












                    3








                    3







                    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






                    share|improve this answer













                    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







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Oct 10 '18 at 9:16









                    Narh-ngwah Ebenezer WattsNarh-ngwah Ebenezer Watts

                    1152




                    1152








                    • 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 at 16:50











                    • downgrade gradle version is not an option! .

                      – Elenasys
                      Feb 19 at 16:54














                    • 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 at 16:50











                    • downgrade gradle version is not an option! .

                      – Elenasys
                      Feb 19 at 16:54








                    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 at 16:50





                    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 at 16:50













                    downgrade gradle version is not an option! .

                    – Elenasys
                    Feb 19 at 16:54





                    downgrade gradle version is not an option! .

                    – Elenasys
                    Feb 19 at 16:54











                    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






                    share|improve this answer



















                    • 2





                      For me it's happens because I'm using oss-licenses-plugin

                      – Mikhail
                      Jan 22 at 16:08
















                    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






                    share|improve this answer



















                    • 2





                      For me it's happens because I'm using oss-licenses-plugin

                      – Mikhail
                      Jan 22 at 16:08














                    2












                    2








                    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






                    share|improve this answer













                    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







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Jan 20 at 9:12









                    Anggrayudi HAnggrayudi H

                    9,84773766




                    9,84773766








                    • 2





                      For me it's happens because I'm using oss-licenses-plugin

                      – Mikhail
                      Jan 22 at 16:08














                    • 2





                      For me it's happens because I'm using oss-licenses-plugin

                      – Mikhail
                      Jan 22 at 16:08








                    2




                    2





                    For me it's happens because I'm using oss-licenses-plugin

                    – Mikhail
                    Jan 22 at 16:08





                    For me it's happens because I'm using oss-licenses-plugin

                    – Mikhail
                    Jan 22 at 16:08











                    2














                    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'





                    share|improve this answer





















                    • 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 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 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 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 at 12:09






                    • 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 at 9:46
















                    2














                    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'





                    share|improve this answer





















                    • 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 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 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 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 at 12:09






                    • 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 at 9:46














                    2












                    2








                    2







                    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'





                    share|improve this answer















                    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'






                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited Jan 23 at 9:41









                    Ewoks

                    10.1k44859




                    10.1k44859










                    answered Jan 15 at 14:36









                    Krste MoskovKrste Moskov

                    13725




                    13725








                    • 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 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 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 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 at 12:09






                    • 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 at 9:46














                    • 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 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 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 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 at 12:09






                    • 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 at 9:46








                    1




                    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 at 10:00





                    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 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 at 10:56







                    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 at 10:56






                    1




                    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 at 10:05







                    @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 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 at 12:09





                    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 at 12:09




                    1




                    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 at 9:46





                    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 at 9:46











                    1














                    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.1'





                    share|improve this answer






























                      1














                      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.1'





                      share|improve this answer




























                        1












                        1








                        1







                        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.1'





                        share|improve this answer















                        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.1'






                        share|improve this answer














                        share|improve this answer



                        share|improve this answer








                        edited Nov 17 '18 at 5:03

























                        answered Nov 17 '18 at 4:16









                        erluxmanerluxman

                        6,12134473




                        6,12134473























                            1














                            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





                            share|improve this answer






























                              1














                              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





                              share|improve this answer




























                                1












                                1








                                1







                                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





                                share|improve this answer















                                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






                                share|improve this answer














                                share|improve this answer



                                share|improve this answer








                                edited Jan 29 at 7:30









                                Sohil R. Memon

                                7,22312144




                                7,22312144










                                answered Jan 29 at 6:42









                                Hamed safariHamed safari

                                112




                                112























                                    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.






                                    share|improve this answer


























                                    • that's just a temporary workaround for you

                                      – Basi
                                      Jan 24 at 5:32













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

                                      – Sergio KS
                                      Jan 24 at 9:09
















                                    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.






                                    share|improve this answer


























                                    • that's just a temporary workaround for you

                                      – Basi
                                      Jan 24 at 5:32













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

                                      – Sergio KS
                                      Jan 24 at 9:09














                                    0












                                    0








                                    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.






                                    share|improve this answer















                                    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.







                                    share|improve this answer














                                    share|improve this answer



                                    share|improve this answer








                                    edited Jan 24 at 9:08

























                                    answered Oct 18 '18 at 16:30









                                    Sergio KSSergio KS

                                    286




                                    286













                                    • that's just a temporary workaround for you

                                      – Basi
                                      Jan 24 at 5:32













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

                                      – Sergio KS
                                      Jan 24 at 9:09



















                                    • that's just a temporary workaround for you

                                      – Basi
                                      Jan 24 at 5:32













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

                                      – Sergio KS
                                      Jan 24 at 9:09

















                                    that's just a temporary workaround for you

                                    – Basi
                                    Jan 24 at 5:32







                                    that's just a temporary workaround for you

                                    – Basi
                                    Jan 24 at 5:32















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

                                    – Sergio KS
                                    Jan 24 at 9:09





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

                                    – Sergio KS
                                    Jan 24 at 9:09











                                    0














                                    Downgrading the version of Gradle worked for me:



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





                                    share|improve this answer


























                                    • downgrading is never an option

                                      – Roshana Pitigala
                                      Apr 11 at 13:42
















                                    0














                                    Downgrading the version of Gradle worked for me:



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





                                    share|improve this answer


























                                    • downgrading is never an option

                                      – Roshana Pitigala
                                      Apr 11 at 13:42














                                    0












                                    0








                                    0







                                    Downgrading the version of Gradle worked for me:



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





                                    share|improve this answer















                                    Downgrading the version of Gradle worked for me:



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






                                    share|improve this answer














                                    share|improve this answer



                                    share|improve this answer








                                    edited Feb 3 at 15:54









                                    סטנלי גרונן

                                    1,76482445




                                    1,76482445










                                    answered Feb 3 at 11:21









                                    Naimish VermaNaimish Verma

                                    1




                                    1













                                    • downgrading is never an option

                                      – Roshana Pitigala
                                      Apr 11 at 13:42



















                                    • downgrading is never an option

                                      – Roshana Pitigala
                                      Apr 11 at 13:42

















                                    downgrading is never an option

                                    – Roshana Pitigala
                                    Apr 11 at 13:42





                                    downgrading is never an option

                                    – Roshana Pitigala
                                    Apr 11 at 13:42











                                    0














                                    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






                                    share|improve this answer




























                                      0














                                      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






                                      share|improve this answer


























                                        0












                                        0








                                        0







                                        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






                                        share|improve this answer













                                        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







                                        share|improve this answer












                                        share|improve this answer



                                        share|improve this answer










                                        answered Feb 6 at 9:06









                                        SamSam

                                        2,57342432




                                        2,57342432























                                            0














                                            Update fabric plugin to 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.28.0'





                                            share|improve this answer




























                                              0














                                              Update fabric plugin to 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.28.0'





                                              share|improve this answer


























                                                0












                                                0








                                                0







                                                Update fabric plugin to 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.28.0'





                                                share|improve this answer













                                                Update fabric plugin to 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.28.0'






                                                share|improve this answer












                                                share|improve this answer



                                                share|improve this answer










                                                answered Apr 11 at 6:22









                                                Bibaswann BandyopadhyayBibaswann Bandyopadhyay

                                                2,5712423




                                                2,5712423






























                                                    draft saved

                                                    draft discarded




















































                                                    Thanks for contributing an answer to Stack Overflow!


                                                    • Please be sure to answer the question. Provide details and share your research!

                                                    But avoid



                                                    • Asking for help, clarification, or responding to other answers.

                                                    • Making statements based on opinion; back them up with references or personal experience.


                                                    To learn more, see our tips on writing great answers.




                                                    draft saved


                                                    draft discarded














                                                    StackExchange.ready(
                                                    function () {
                                                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f52470044%2fwarning-api-variant-getjavacompile-is-obsolete-and-has-been-replaced-with%23new-answer', 'question_page');
                                                    }
                                                    );

                                                    Post as a guest















                                                    Required, but never shown





















































                                                    Required, but never shown














                                                    Required, but never shown












                                                    Required, but never shown







                                                    Required, but never shown

































                                                    Required, but never shown














                                                    Required, but never shown












                                                    Required, but never shown







                                                    Required, but never shown







                                                    Popular posts from this blog

                                                    Xamarin.iOS Cant Deploy on Iphone

                                                    Glorious Revolution

                                                    Dulmage-Mendelsohn matrix decomposition in Python