How to fix ERROR: No signature of method: build_ap86oam3dut3pxce3x49rdtma.android()?

Question

ERROR: No signature of method: build_ap86oam3dut3pxce3x49rdtma.android() is applicable for argument types: (build_ap86oam3dut3pxce3x49rdtma$_run_closure1) values: [build_ap86oam3dut3pxce3x49rdtma$_run_closure1@47588b04]

The build gradle is:

apply plugin: 'com.android.application'

    android{
    implementationSdkVersion 28
    buildToolsVersion "29.0.3"
    defaultConfig {
        applicationId "com.uiresource.taksiku"
        minSdkVersion 16
        targetSdkVersion 28
        versionCode 1
        versionName "1.0"
        testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
        vectorDrawables.useSupportLibrary = true
    }
    buildTypes {
        release {
            minifyEnabled true
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
        }
    }

    dependencies {
        implementation fileTree(dir: 'libs', include: ['*.jar'])
        androidTestImplementation('com.android.support.test.espresso:espresso-core:2.3-alpha', {
            exclude group: 'com.android.support', module: 'support-annotations'
        })
        implementation "com.android.support:appcompat-v7:$var"
        implementation 'com.android.support:design:28.0.0'
        testimplementation 'junit:junit:4.13'
        implementation 'com.android.support.constraint:constraint-layout:2.0.0-beta5'
        implementation 'de.hdodenhof:circleimageview:3.1.0'
        }

score 99 · Answer 1 · edited Apr 22 '22 at 07:50

99

If you are using kotlin version 1.4.21 or newer, kotlin-android-extension is deprecated. So if you removing the plugin you also have to remove the android experimental extension block. In my case, I had to remove these pieces of code.

apply plugin: 'kotlin-android-extensions'


androidExtensions {
    experimental = true
}

But if above did not fix it

This a kind of general and/or wrapping error which hides the real cause and/or problem, hence to see actual error message, try something like:

./gradlew :app:assembleDebug --stacktrace

And search for resulting real error-message instead.

edited Apr 22 '22 at 07:50

Top-Master

5,262
5
23
45

answered Jan 11 '21 at 13:52

Chintan Parmar

1,694
11
18

5

Thanks for this! Seems like that snippet should be added to the migration [guide](https://developer.android.com/topic/libraries/view-binding/migration) AS points you to for the deprecation notice. – A_Kiniyalocts Jan 14 '21 at 19:52
2

Thanks. Imagine, this is what AS gave me: `> No signature of method: build_1vktrv59g77woj77yc4fmjh74.android() is applicable for argument types: (build_1vktrv59g77woj77yc4fmjh74$_run_closure1) values: [build_1vktrv59g77woj77yc4fmjh74$_run_closure1@3918b394]` – nyxee Mar 24 '21 at 07:11
Thanks for the answer mate ! saved couple of hours – Panduka DeSilva Apr 26 '21 at 05:04

score 36 · Answer 2 · answered Jun 08 '20 at 00:42

36

I had the same error message until I commented out everything in the android plugin except the compile sdk version, trying to get back to a successful build config.

android {
    compileSdkVersion 23
/*
    ...
*/
}

Then, I started uncommenting things until I narrowed the problem down to using the following incorrectly.

ProductFlavors {
  ...
}

I'm not sure if you're using the same block, but at the moment, I'm leaving it commented out because I'm not sure it's needed. Once I got rid of it though, I was receiving other errors about sdk root dir location, so I was able to fix those.

I hope this helps!

answered Jun 08 '20 at 00:42

Daniel

369
2
2

3

Thanks for the idea. Was ```kotlinOptions { jvmTarget = '1.8'``` } for me – ShHolmes Jan 29 '21 at 14:11
@ShHolmes me too – Mohamed Medhat Sep 16 '21 at 08:03
1

I have the same problem with the `release` block within the `signingConfigs` block, my configuration looks correct, this is messed up, I don't know how I can fix it, commenting is no solution. – Martin Braun Feb 03 '22 at 09:45
Good trick for debuging.. – Shawn Lee Feb 15 '22 at 07:33
`until I commented out everything in the android plugin` worked for me. – Muhammad Saqib Mar 08 '22 at 08:31

score 19 · Answer 3 · answered Nov 06 '20 at 03:57

19

I was getting a similar error because the versionCode was being taken from a properties file, but the versionCode needs to be an integer and not a string, so toInteger() was needed.

Nice logs, android.

answered Nov 06 '20 at 03:57

htafoya

16,758
11
72
95

2

this also happened to me, checking version code solved the issue – Mehran Sahandi Far Apr 26 '21 at 07:07
this was a lot helpful!! my case was about versionCode number, which i set by using System.getenv("NEW_BUILD_NUMBER"), thats is a string! and i had to use System.getenv("NEW_BUILD_NUMBER").toInteger() – adrian oviedo Jul 07 '21 at 03:06
Well those logs are from Gradle, not Android. Most Gradle errors are very confusing, because groovy is doing a lot of magic in the background. – rekire Sep 08 '21 at 10:02
I've been bashing my head against the wall for hours because of this. Thanks for the tip! – K Mehta Nov 23 '21 at 08:58
I had the version code be the same as the Date.now() timestamp. Probably this integer is to big or something, because changing it to 130 worked. – Jaap Weijland Jan 20 '22 at 16:38
@JaapWeijland probably because Date.now() returns a Long, and it cannot be casted automatically to Int. – htafoya Jan 20 '22 at 16:59

score 16 · Answer 4 · answered Dec 19 '20 at 09:10

16

in my case I needed to comment out this lines in gradle

androidExtensions{
    experimental = true
}

answered Dec 19 '20 at 09:10

mahmood

241
3
7

saved my day!! :D – Alfetch Dec 22 '20 at 13:00

score 14 · Answer 5 · answered Oct 10 '20 at 06:46

14

Best thing you can do is comment parts of your build.gradle file related to the issue until you get a good build and them uncomment 1 by 1 until you find the problem. I had the same error and it was related with a typo in one of the app build.gradle blocks. I was using:

android {
    ...
    buildFeature {
        ...
    }
}

instead of

android {
    ...
    buildFeatures {
        ...
    }
}

Good luck!

answered Oct 10 '20 at 06:46

Brahyam

171
1
4

Look at your answer example, it's totally wrong..you had report the same lines.. – Alessandro Ornano Jan 23 '21 at 10:34
7

@AlessandroOrnano In my answer the difference is between `buildFeature` vs `buildFeatures` with an `s` at the end. the later is the correct one. – Brahyam Jan 24 '21 at 11:35

score 13 · Answer 6 · answered Sep 09 '21 at 11:59

13

I removed this code from my Gradle:

javaCompileOptions {
        annotationProcessorOptions {
            includeCompileClasspath true
        }
    }

answered Sep 09 '21 at 11:59

Shogun Nassar

512
4
15

score 12 · Answer 7 · answered Aug 12 '21 at 20:55

This is a syntax error somewhere in your gradle file inside the android {} closure. If you are someone having this same problem then the best solution to this problem is to comment out portions of code inside android {} and keep running gradle sync until you have a successful build. Then slowly add back commented out lines until you find the culprit.

score 12 · Answer 8 · answered Oct 04 '21 at 09:45

12

In Android Studio 2021.1.1 Canary 12, I removed

plugins{
   ...
   id 'kotlin-android-extensions'
}

But forgot to remove this from

android{
    androidExtensions {
            experimental = true
        }
}

after removing androidExtension block my problem solved

answered Oct 04 '21 at 09:45

mona baharlou

1,143
11
21

2

This solution worked for me. – Dheeraj Rijhwani Jan 24 '22 at 11:59

score 8 · Answer 9 · answered Jul 06 '21 at 03:34

8

This issue is usually related to some change on build.gradle file, for example in my case, was this line in the defaultConfig section on that file:

versionCode 1.1

I changed it to:

versionCode 2

and problem fixed.

answered Jul 06 '21 at 03:34

manuelpgs

903
10
19

score 7 · Answer 10 · answered Mar 10 '21 at 16:44

I was checking a very old project from Github and found the solution by matching the app level build.gradle file with my current project, hence the solution is to replace

runProguard false

with

minifyEnabled false

It must've been deprecated and removed in a later build which caused a similar issue - No signature of method: build_6f958jjxpxn7lllu9wu5brezx.android()

score 4 · Answer 11 · answered Dec 25 '20 at 03:31

It is because there's syntax error in android{..} part of build.gradle You've used implementationSdkVersion which should ideally be compileSdkVersion. Error in variable names in android{..} leads to such errors.

TLDR;

Replace implementationSdkVersion with compileSdkVersion

score 3 · Answer 12 · answered Nov 17 '21 at 15:19

3

There's no unique solution for this error, except that it's a syntax error inside build.gradle file.

answered Nov 17 '21 at 15:19

bra.Scene

462
5
13

score 3 · Answer 13 · answered Dec 15 '21 at 12:36

This problem is common in Flutter 2.8

Delete Folder with all sub Folder of C:\Users\LENOVO\.gradle
Go File menu > Setting (Ctrl+Alt+S) Go Appearance & Behaviour > System Setting > Android SDK > SDK Tool Tab and then uncheck Android SDK Build-Tool press OK Button 3)Run Project (Shift+F10) in Andriod Studio it will Download all required files from the internet and your issue resolve

After if the issue is Not resolved then Second Step is:

Go > android\app\build.gradle in your project Please Add > minSdkVersion 19 or 20 // Remove it because, 16 is by default minSdkVersion in flutter 2.8 //minSdkVersion flutter.minSdkVersion
add multiDexEnabled true if file size increase from limits

score 2 · Answer 14 · answered Jun 02 '20 at 00:11

I'm new to Android but i got a message similar to yours today when i try to use a different version (not the suggested ones) of the Gradle plugin and gradle engine on Android Studio 4.1 canary.

When I had on my App build.gradle these lines:

task wrapper(type: Wrapper){
    gradleVersion = '5.6.4'
}

and on my build.gradle for the module this line

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

This was the message i got with previous settings:

A problem occurred evaluating project ':app'.
> No signature of method: build_5dcjpn4h9nkpym0yszxs5w2uh.android() is applicable for argument types: (build_5dcjpn4h9nkpym0yszxs5w2uh$_run_closure1) values: [build_5dcjpn4h9nkpym0yszxs5w2uh$_run_closure1@2e4515b3]

The way i found to solve this error was changing version for the gradle plugin on my build.gradle for the module like this

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

I hope this could help you. Happy coding!

score 2 · Answer 15 · answered Nov 24 '20 at 23:48

I added debug under buildTypes in the gradle file and missed a comma after "API_URL":

not working:

buildTypes {
    ...
    debug {
        buildConfigField "String", "API_URL" "\"http://myapi.com/\""
    }
}

working:

buildTypes {
    ...
    debug {
        buildConfigField "String", "API_URL", "\"http://myapi.com/\""
    }
}

good luck!

score 2 · Answer 16 · answered Aug 26 '21 at 21:38

For me I had updated firebase-crashlytics-gradle from 2.5.2 to 2.7.1 in my project build.gradle and that caused the issue.

dependencies {
    [...]
    classpath "com.google.firebase:firebase-crashlytics-gradle:2.7.1
}

I removed an unnecessary firebaseCrashlytics configuration in my app module build.grade and then it worked again:

// TODO this entire block had to be deleted to fix the issue
firebaseCrashlytics {
    mappingFileUploadEnabled = false
}

Harisewak · Answer 17 · 2022-03-11T15:16:01.540

2

I received this error while creating a new Jetpack Compose project. 'app' module's build.gradle was cracking up.

Removing packagingOptions did the trick for me ->

packagingOptions {
        
        resources {
            excludes += '/META-INF/{AL2.0,LGPL2.1}'
        }
        
    }
}

edited Mar 11 '22 at 15:16

answered Sep 24 '21 at 10:18

Harisewak

570
6
15

score 1 · Answer 18 · answered Dec 04 '20 at 15:02

1

I had a similar issue because I had added a trailing comma , in defaultConfig in android/app/build.gradle

answered Dec 04 '20 at 15:02

Raphael Pinel

1,572
18
19

score 1 · Answer 19 · answered Apr 06 '21 at 04:58

For me, the problem was in this block

defaultConfig {
        applicationId "abc"
        minSdkVersion rootProject.ext.minSdkVersion
        targetSdkVersion rootProject.ext.targetSdkVersion
        versionCode 12.1 **-> 13**
        versionName "3"
    }

The 'versionCode' mustn't be a decimal number

score 1 · Answer 20 · answered Apr 15 '21 at 16:03

1

I had a problem similar to @LalitFauzdar 's but with a different solution. A plugin that I'm using requires custom ProGuard rules for release builds, but adding a reference to the rules file in the app gradle file resulted in the error in question. Here is the offending line, commented-out:

buildTypes {
  release {
    signingConfig signingConfigs.release
    // proguardFiles 'proguard-rules.pro'
  }
}

answered Apr 15 '21 at 16:03

WillHaslett

558
5
11

Yes, this line was the culprit for my case too. Also, the console error logs are HORRIBLE. Seriously, google couldn't have come up with worse logs. – kc_dev Dec 08 '21 at 05:53

score 1 · Answer 21 · answered May 23 '21 at 15:20

I had this error when i added 2 product flavors to my build.gradle app module file with the following names:

productFlavors {
    normal-sv1 {
    ...
    }
    normal-sv2 {
    ...
    }
}

Found out that this error was because of the '-' int the middle of the flavors' names. When i used '_' instead of '-', like below, the error was gone.

productFlavors {
    normal_sv1 {
    ...
    }
    normal_sv2 {
    ...
    }
}

Muzammil Hussain · Answer 22 · 2022-04-27T05:15:21.953

1

i was trying to add parcelable plugin in my project. this was the same error in my case too. Because, JetBrains extracted the Parcelize from Kotlin Android Extensions to a new plugin, kotlin-parcelize

So, If you want to add easy parcelable in kotlin then follow these steps:

First you will need to add kotlin-parcelize plugin to your module

plugins {
    ..
    id 'kotlin-parcelize'
}

Then change your old import statement from

import kotlinx.android.parcel.Parcelize

to

import kotlinx.parcelize.Parcelize

Example:

import kotlinx.parcelize.Parcelize

import android.os.Parcelable

@Parcelize
class User(

val name: String, 
val age: Int

): Parcelable

edited Apr 27 '22 at 05:15

answered Jun 10 '21 at 07:36

Muzammil Hussain

139
1
3

if this doesn't work, also have to remember to remove following from gradle (inside android {} ) if previously using `kotlin-android-extensions`: androidExtensions { experimental = true } – Stefan Indaco Jun 15 '21 at 22:02

score 1 · Answer 23 · answered Mar 22 '22 at 12:44

1

I just removed useProguard true in build.gradle > android > buildTypes, and it worked for me.

answered Mar 22 '22 at 12:44

Sumit Saurabh

1,166
1
15
30

score 0 · Answer 24 · answered Oct 09 '20 at 15:33

0

Make sure you are using the kotlin android plugin instead of the kotlin jvm plugin.

apply plugin: 'kotlin-android' // NOT kotlin-jvm

answered Oct 09 '20 at 15:33

cambunctious

6,718
4
30
44

score 0 · Answer 25 · edited Apr 08 '22 at 22:45

I had this exact same issue. It is a nasty one.

I followed the answer first here Deprecated Gradle features not compatible and ran in the terminal

cd android && ./gradlew clean && ./gradlew :app:bundleRelease

the gradlew command gave more detialed feedback, and turned out my Java and JDK were 32bit instead of 64 and also outdated...

This resulted in further errors, but could resolve them step by step: Invalid initial heap size -Xms4096M Could not find tools.jar. Please check that C:\Program Files\Java\jre1.8.0_151 contains a valid JDK installation

score 0 · Answer 26 · answered Oct 19 '20 at 04:54

0

Try to comment this in your app level build.gradle file

openOptions {
    disable 'InvalidPackage'
}

answered Oct 19 '20 at 04:54

Amir Eleuch

39
5

score 0 · Answer 27 · edited Apr 08 '22 at 22:44

0

In my case, the error cause is below

compilpepeeSdkVersion

rather than

compileSdkVersion

edited Apr 08 '22 at 22:44

Boken

4,062
9
31
41

answered Jan 05 '21 at 14:47

oiyio

4,329
3
37
49

score 0 · Answer 28 · answered Jan 29 '21 at 13:44

0

Thanks for mentioning to just comment things and test, for me it was:

kapt {
    useBuildCache = true
}

Removed it, everything was building again. Happened after updating Kotlin version.

answered Jan 29 '21 at 13:44

cV2

5,676
4
43
54

score 0 · Answer 29 · answered Feb 08 '21 at 00:22

Old issue but worth noting you might need to follow the migration guide here if you see this issue:

https://developer.android.com/topic/libraries/view-binding/migration

For me, removing the line apply plugin: 'kotlin-android-extensions' and adding view binding as below resolved the issue:

buildFeatures {
    viewBinding true
}

score 0 · Answer 30 · answered Mar 31 '21 at 17:31

0

I got this problem after adding

kapt {
    // etc
}

because I hadn't added:

apply plugin: 'kotlin-kapt'

answered Mar 31 '21 at 17:31

Edmund Johnson

594
8
13

score 0 · Answer 31 · answered Apr 01 '21 at 15:01

For me the reason was misspelling the native libs command for gradle, as of version updates and old tutorials.

    externalNativeBuild {
        ndkBuild {
            path 'Android.mk'
        }
    }

... 
// But i had:  
    externalNativeBuild {
        ndk {
            path 'Android.mk'
        }
    }

But as the number of answer indicate, there are several possibilites for this issue.
Most probably after some version updates some gradle functions are no longer available.

score 0 · Answer 32 · answered Apr 07 '21 at 15:09

0

I have been struggling with the error after adding Flutter flavors. Apparently if you have flavor names which contain - it won't work.

e.g. Transformed names from test-preprod to test_preprod and it is now working.

answered Apr 07 '21 at 15:09

George Dobrin

1

score 0 · Answer 33 · answered May 19 '21 at 12:49

0

For me it was useIR true inside kotlinOptions

answered May 19 '21 at 12:49

Matt Robertson

2,551
5
27
56

score 0 · Answer 34 · answered Jun 20 '21 at 06:13

Most of the time its missing dependencies, if you are using "dagger/Hilt"

Ensure its added in project level build.graddle

   dependencies {
       // ....
        classpath "com.google.dagger:hilt-android-gradle-plugin:$hilt_version"
    
    }

add hilt plugin in the app level build.graddle

plugins {
 //....
    id 'dagger.hilt.android.plugin'
}

add complete hilt and dagger dependencies

   //hilt

    implementation "com.google.dagger:hilt-android:$hilt_version"

    // Dagger Core 
    implementation "com.google.dagger:dagger:2.28"
    kapt "com.google.dagger:dagger-compiler:2.28"

    // Dagger Android
    api 'com.google.dagger:dagger-android:2.35.1'
    api 'com.google.dagger:dagger-android-support:2.31'
    kapt 'com.google.dagger:dagger-android-processor:2.31'

//Dagger - Hilt
    implementation "com.google.dagger:hilt-android:2.32-alpha"
    kapt "com.google.dagger:hilt-android-compiler:2.28-alpha"

score 0 · Answer 35 · answered Aug 16 '21 at 11:52

0

For me, the problem was that the Gradle Plugin update assistant replaced this:

aaptOptions {
    noCompress "..."
}

With this:

androidResources {
        noCompress '...'
}

Undoing it, solved the build error. Of course this is just a workaround.

answered Aug 16 '21 at 11:52

falconforce

121
1
2

score 0 · Answer 36 · answered Dec 18 '21 at 14:16

0

Remove this line, it will work.

includeCompileClasspath true

answered Dec 18 '21 at 14:16

Visal Varghese

397
4
14

1

This works for me. `includeCompileClasspath true` is deprecated in AGP 4.2 [see](https://developer.android.com/studio/build/dependencies?utm_source=android-studio#annotation_processor), maybe deleted in AGP 7.0. – Vít Kapitola Jan 30 '22 at 16:55
This work for me too. I was using `javaCompileOptions { annotationProcessorOptions includeCompileClasspath false}}` after remove this code. It work. – Quimbo Jun 02 '22 at 06:35

score 0 · Answer 37 · answered Jan 09 '22 at 16:39

Today I got this error when I was making signed apk and I made a mistake while doing setup for playstore, In android/app/build.gradle

signingConfigs{
debug{
 .....
 .....
}
release {....}  // I added the release config outside the signing config
}

Correct-way-todo-just-for-ref

score 0 · Answer 38 · answered Jan 30 '22 at 18:44

0

I had mispelled signingConfig as signingConfigs

So it is actually signingConfig signingConfigs.{yourVariantName}

And NOT signingConfigs signingConfigs.{yourVariantName}

answered Jan 30 '22 at 18:44

gtxtreme

1,219
1
7
20

score 0 · Answer 39 · answered Mar 06 '22 at 10:08

I had the same problem with a vanilla just-created new project in Android Studio Bumblebee (2021.1):

The auto-generated build.gradle had this in it:

buildTypes {
    release {
        minifyEnabled false
        proguardFiles
            getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
    }
}

Notice that proguardFiles "function call"'s parameters are on a separate line, this is not valid Groovy code.

score 0 · Answer 40 · answered Mar 07 '22 at 10:35

In my case I need to remove following in app/build.gradle:

packagingOptions {
        jniLibs {
            pickFirsts += ['lib/armeabi-v7a/libc++_shared.so', 'lib/arm64-v8a/libc++_shared.so', 'lib/x86/libc++_shared.so', 'lib/x86_64/libc++_shared.so']
        }
    }

How to fix ERROR: No signature of method: build_ap86oam3dut3pxce3x49rdtma.android()?

40 Answers40

But if above did not fix it

Linked