Android Studio 3.0 - Unable to find method 'com.android.build.gradle.internal.variant.BaseVariantData.getOutputs()Ljava/util/List'

Question

Trying to start a new Kotlin project with Android Studio 3.0 Canary 1 displays this error. Full trace:

Error:Unable to find method \'com.android.bui

Answer 1

It worked for me

Using the 8.4.0 version

 classpath 'com.jakewharton:butterknife-gradle-plugin:8.4.0'  

Answer 2

Update your kotlin version to the latest:

ext.kotlin_version = '1.1.2-4' //currently it's the latest version

Then you may face some more errors, so before syncing again, make sure that your buildToolsVersion is "26.0.2" or higher.

Answer 3

For Java

Just remove

classpath 'me.tatarka:gradle-retrolambda:3.7.0'

downgrade butterknifeversion to 8.4.0

classpath 'com.jakewharton:butterknife-gradle-plugin:8.4.0'

Don't forget to remove

apply plugin: 'me.tatarka.retrolambda'

from app level build gradle.

Answer 4

This is a known issue in Android Studio Preview 3.0:

If you see this error, it's possible you have a pre-existing version of the Kotlin plugin that is incompatible with the new Android Plugin for Gradle that's in Android Studio 3.0. The solution is to delete the old Kotlin plugin.

Open your project-level build.gradle file and locate ext.kotlin_version. It should be 1.1.2-4 (or higher). If it shows an older version, you need to delete the old Kotlin plugin so it does not obstruct the version included with Android Studio 3.0.

On Windows, it should be located at

C:\Users\user_name\AndroidStudio_version\config\plugins\Kotlin\

On Mac, look in

~/Library/Application\ Support/AndroidStudio_version/Kotlin/

Answer 5

In my case, the issue was caused because we were applying butterknife-gradle-plugin. Upgrading to 8.8.1 didn't fix the issue, but removing it certainly did.

The build.gradle belongs to the application, so I don't even know why we are using that plugin (I'm new to the project)

Answer 6

In my build.gradle changing

ext.kotlin_version = '1.1.2-3'

to

ext.kotlin_version = '1.1.2-4'

fixed this.

You can find the most recent version here.