Cannot find symbol DataBindingComponent on Android Studio 3.2 Canary 16 Kotlin project

I just created a new project on Android Studio 3.2 Canary 16 with Kotlin enabled. Then I also enabled data binding, but I'm getting an error saying that it could not find the DataBindingComponent class.

Here's my project gradle:

// Top-level build file where you can add configuration options common to all sub-projects/modules.



buildscript {

    ext.kotlin_version = '1.2.41'

    ext.android_plugin_version = '3.2.0-alpha10'

    repositories {

        google()

        jcenter()

    }

    dependencies {

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

        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"



        // NOTE: Do not place your application dependencies here; they belong

        // in the individual module build.gradle files

    }

}



allprojects {

    repositories {

        google()

        jcenter()

    }

}



task clean(type: Delete) {

    delete rootProject.buildDir

}

My module gradle file:

apply plugin: 'com.android.application'



apply plugin: 'kotlin-android'



apply plugin: 'kotlin-kapt'



apply plugin: 'kotlin-android-extensions'



android {

    compileSdkVersion 27

    defaultConfig {

        applicationId "net.julianonunes.myapp"

        minSdkVersion 22

        targetSdkVersion 27

        versionCode 1

        versionName "1.0"

    }

    buildTypes {

        release {

            minifyEnabled false

            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'

        }

    }

    dataBinding {

        enabled = true

    }

}



dependencies {

    implementation fileTree(dir: 'libs', include: ['*.jar'])

    implementation"org.jetbrains.kotlin:kotlin-stdlib:$kotlin_version"

    implementation 'com.android.support:appcompat-v7:27.1.1'

    implementation 'com.android.support.constraint:constraint-layout:1.1.0'

    implementation 'com.squareup.okhttp3:okhttp:3.10.0'

    implementation 'com.android.support:design:27.1.1'

    kapt "com.android.databinding:compiler:3.1.2"

}

My activity's xml:

<?xml version="1.0" encoding="utf-8"?>

<layout xmlns:android="http://schemas.android.com/apk/res/android"

    xmlns:app="http://schemas.android.com/apk/res-auto"

    xmlns:tools="http://schemas.android.com/tools">



    <data>

        <variable

            name="data"

            type="net.julianonunes.myapp.RegisterData" />

    </data>



    ....

</layout>

And here's the build output:

Executing tasks: [clean, :app:assembleDebug]



Configuration on demand is an incubating feature.



> Configure project :app

app: 'annotationProcessor' dependencies won't be recognized as kapt annotation processors. Please change the configuration name to 'kapt' for these artifacts: 'androidx.databinding:databinding-compiler:3.2.0-alpha16'.



> Task :clean

> Task :app:clean

> Task :app:preBuild UP-TO-DATE

> Task :app:preDebugBuild

> Task :app:compileDebugAidl NO-SOURCE

> Task :app:compileDebugRenderscript

> Task :app:checkDebugManifest

> Task :app:generateDebugBuildConfig

> Task :app:prepareLintJar UP-TO-DATE

> Task :app:mainApkListPersistenceDebug

> Task :app:generateDebugResValues

> Task :app:generateDebugResources

> Task :app:mergeDebugResources

> Task :app:createDebugCompatibleScreenManifests

> Task :app:processDebugManifest

> Task :app:splitsDiscoveryTaskDebug

> Task :app:processDebugResources

> Task :app:generateDebugSources

> Task :app:dataBindingExportBuildInfoDebug

> Task :app:transformDataBindingBaseClassLogWithDataBindingMergeGenClassesForDebug

> Task :app:transformDataBindingWithDataBindingMergeArtifactsForDebug

> Task :app:dataBindingGenBaseClassesDebug

Download https://dl.google.com/dl/android/maven2/com/android/databinding/compiler/3.1.2/compiler-3.1.2.pom

Download https://dl.google.com/dl/android/maven2/com/android/databinding/compiler/3.1.2/compiler-3.1.2.jar

> Task :app:kaptGenerateStubsDebugKotlin

e: /home/juliano/Documents/Projetos/myapp/app/build/generated/data_binding_base_class_source_out/debug/dataBindingGenBaseClassesDebug/out/net/julianonunes/myapp/databinding/ActivityMainBinding.java:28: error: cannot find symbol

  protected ActivityMainBinding(DataBindingComponent _bindingComponent, View _root,

                                ^

  symbol:   class DataBindingComponent

  location: class ActivityMainBinding

e: /home/juliano/Documents/Projetos/myapp/app/build/generated/data_binding_base_class_source_out/debug/dataBindingGenBaseClassesDebug/out/net/julianonunes/myapp/databinding/ActivityMainBinding.java:46: error: cannot find symbol

      @Nullable ViewGroup root, boolean attachToRoot, @Nullable DataBindingComponent component) {

                                                                ^

  symbol:   class DataBindingComponent

  location: class ActivityMainBinding

e: /home/juliano/Documents/Projetos/myapp/app/build/generated/data_binding_base_class_source_out/debug/dataBindingGenBaseClassesDebug/out/net/julianonunes/myapp/databinding/ActivityMainBinding.java:57: error: cannot find symbol

      @Nullable DataBindingComponent component) {

                ^

  symbol:   class DataBindingComponent

  location: class ActivityMainBinding

e: /home/juliano/Documents/Projetos/myapp/app/build/generated/data_binding_base_class_source_out/debug/dataBindingGenBaseClassesDebug/out/net/julianonunes/myapp/databinding/ActivityMainBinding.java:68: error: cannot find symbol

      @Nullable DataBindingComponent component) {

                ^

  symbol:   class DataBindingComponent

  location: class ActivityMainBinding

e: [kapt] An exception occurred: java.lang.NullPointerException

    at java.io.File.<init>(File.java:277)

    at android.databinding.annotationprocessor.ProcessExpressions.onHandleStep(ProcessExpressions.java:77)

    at android.databinding.annotationprocessor.ProcessDataBinding$ProcessingStep.runStep(ProcessDataBinding.java:203)

    at android.databinding.annotationprocessor.ProcessDataBinding$ProcessingStep.access$000(ProcessDataBinding.java:188)

    at android.databinding.annotationprocessor.ProcessDataBinding.doProcess(ProcessDataBinding.java:90)

    at android.databinding.annotationprocessor.ProcessDataBinding.process(ProcessDataBinding.java:65)

    at org.jetbrains.kotlin.kapt3.ProcessorWrapper.process(annotationProcessing.kt:131)

    at com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:794)

    at com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:705)

    at com.sun.tools.javac.processing.JavacProcessingEnvironment.access$1800(JavacProcessingEnvironment.java:91)

    at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1035)

    at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1176)

    at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1170)

    at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1068)

    at org.jetbrains.kotlin.kapt3.AnnotationProcessingKt.doAnnotationProcessing(annotationProcessing.kt:87)

    at org.jetbrains.kotlin.kapt3.AnnotationProcessingKt.doAnnotationProcessing$default(annotationProcessing.kt:45)

    at org.jetbrains.kotlin.kapt3.AbstractKapt3Extension.runAnnotationProcessing(Kapt3Extension.kt:257)

    at org.jetbrains.kotlin.kapt3.AbstractKapt3Extension.analysisCompleted(Kapt3Extension.kt:212)

    at org.jetbrains.kotlin.kapt3.ClasspathBasedKapt3Extension.analysisCompleted(Kapt3Extension.kt:95)

    at org.jetbrains.kotlin.cli.jvm.compiler.TopDownAnalyzerFacadeForJVM$analyzeFilesWithJavaIntegration$2.invoke(TopDownAnalyzerFacadeForJVM.kt:97)

    at org.jetbrains.kotlin.cli.jvm.compiler.TopDownAnalyzerFacadeForJVM.analyzeFilesWithJavaIntegration(TopDownAnalyzerFacadeForJVM.kt:107)

    at org.jetbrains.kotlin.cli.jvm.compiler.TopDownAnalyzerFacadeForJVM.analyzeFilesWithJavaIntegration$default(TopDownAnalyzerFacadeForJVM.kt:84)

    at org.jetbrains.kotlin.cli.jvm.compiler.KotlinToJVMBytecodeCompiler$analyze$1.invoke(KotlinToJVMBytecodeCompiler.kt:374)

    at org.jetbrains.kotlin.cli.jvm.compiler.KotlinToJVMBytecodeCompiler$analyze$1.invoke(KotlinToJVMBytecodeCompiler.kt:64)

    at org.jetbrains.kotlin.cli.common.messages.AnalyzerWithCompilerReport.analyzeAndReport(AnalyzerWithCompilerReport.kt:101)

    at org.jetbrains.kotlin.cli.jvm.compiler.KotlinToJVMBytecodeCompiler.analyze(KotlinToJVMBytecodeCompiler.kt:365)

    at org.jetbrains.kotlin.cli.jvm.compiler.KotlinToJVMBytecodeCompiler.compileModules$cli(KotlinToJVMBytecodeCompiler.kt:130)

    at org.jetbrains.kotlin.cli.jvm.K2JVMCompiler.doExecute(K2JVMCompiler.kt:161)

    at org.jetbrains.kotlin.cli.jvm.K2JVMCompiler.doExecute(K2JVMCompiler.kt:63)

    at org.jetbrains.kotlin.cli.common.CLICompiler.execImpl(CLICompiler.java:107)

    at org.jetbrains.kotlin.cli.common.CLICompiler.execImpl(CLICompiler.java:51)

    at org.jetbrains.kotlin.cli.common.CLITool.exec(CLITool.kt:96)

    at org.jetbrains.kotlin.daemon.CompileServiceImpl$compile$1$1$2.invoke(CompileServiceImpl.kt:405)

    at org.jetbrains.kotlin.daemon.CompileServiceImpl$compile$1$1$2.invoke(CompileServiceImpl.kt:98)

    at org.jetbrains.kotlin.daemon.CompileServiceImpl$doCompile$$inlined$ifAlive$lambda$2.invoke(CompileServiceImpl.kt:920)

    at org.jetbrains.kotlin.daemon.CompileServiceImpl$doCompile$$inlined$ifAlive$lambda$2.invoke(CompileServiceImpl.kt:98)

    at org.jetbrains.kotlin.daemon.common.DummyProfiler.withMeasure(PerfUtils.kt:137)

    at org.jetbrains.kotlin.daemon.CompileServiceImpl.checkedCompile(CompileServiceImpl.kt:950)

    at org.jetbrains.kotlin.daemon.CompileServiceImpl.doCompile(CompileServiceImpl.kt:919)

    at org.jetbrains.kotlin.daemon.CompileServiceImpl.compile(CompileServiceImpl.kt:404)

    at sun.reflect.GeneratedMethodAccessor91.invoke(Unknown Source)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

    at java.lang.reflect.Method.invoke(Method.java:498)

    at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:346)

    at sun.rmi.transport.Transport$1.run(Transport.java:200)

    at sun.rmi.transport.Transport$1.run(Transport.java:197)

    at java.security.AccessController.doPrivileged(Native Method)

    at sun.rmi.transport.Transport.serviceCall(Transport.java:196)

    at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)

    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)

    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)

    at java.security.AccessController.doPrivileged(Native Method)

    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)

    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

    at java.lang.Thread.run(Thread.java:745)



> Task :app:kaptDebugKotlin FAILED



FAILURE: Build failed with an exception.



* What went wrong:

Execution failed for task ':app:kaptDebugKotlin'.

> Compilation error. See log for more details



* Try:

Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.



* Get more help at https://help.gradle.org



Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.

See https://docs.gradle.org/4.7/userguide/command_line_interface.html#sec:command_line_warnings



BUILD FAILED in 8s

20 actionable tasks: 19 executed, 1 up-to-date

What is wrong with my project?

PS: The problem also happens on Android Studio 3.1.2

edited May 30 '18 at 11:05

asked May 29 '18 at 23:49

Juliano Nunes Silva Oliveira

3,421941115

did you get any solution?

– Brijesh Joshi
Jul 25 '18 at 9:46

@BrijeshJoshi see my answer below

– Edijae Crusar
Aug 29 '18 at 12:40

For me the true error was actually printed after this. After fixing that error, this one goes away as well.

– Mygod
Sep 19 '18 at 12:42

1

In my case no other error was shown in log, but after reviewing my diffs I found an unimported annotation in some kt file. After fixing import, build works. Seems to be some problem in kapt processor.

– androidguy
Oct 16 '18 at 0:31

Cannot find symbol DataBindingComponent when build from command line using ./gradlew assembleDebug

– Chetan Chaudhari
Jan 10 at 10:09

|
show 1 more comment

Here's my project gradle:

// Top-level build file where you can add configuration options common to all sub-projects/modules.



buildscript {

    ext.kotlin_version = '1.2.41'

    ext.android_plugin_version = '3.2.0-alpha10'

    repositories {

        google()

        jcenter()

    }

    dependencies {

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

        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"



        // NOTE: Do not place your application dependencies here; they belong

        // in the individual module build.gradle files

    }

}



allprojects {

    repositories {

        google()

        jcenter()

    }

}



task clean(type: Delete) {

    delete rootProject.buildDir

}

My module gradle file:

apply plugin: 'com.android.application'



apply plugin: 'kotlin-android'



apply plugin: 'kotlin-kapt'



apply plugin: 'kotlin-android-extensions'



android {

    compileSdkVersion 27

    defaultConfig {

        applicationId "net.julianonunes.myapp"

        minSdkVersion 22

        targetSdkVersion 27

        versionCode 1

        versionName "1.0"

    }

    buildTypes {

        release {

            minifyEnabled false

            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'

        }

    }

    dataBinding {

        enabled = true

    }

}



dependencies {

    implementation fileTree(dir: 'libs', include: ['*.jar'])

    implementation"org.jetbrains.kotlin:kotlin-stdlib:$kotlin_version"

    implementation 'com.android.support:appcompat-v7:27.1.1'

    implementation 'com.android.support.constraint:constraint-layout:1.1.0'

    implementation 'com.squareup.okhttp3:okhttp:3.10.0'

    implementation 'com.android.support:design:27.1.1'

    kapt "com.android.databinding:compiler:3.1.2"

}

My activity's xml:

<?xml version="1.0" encoding="utf-8"?>

<layout xmlns:android="http://schemas.android.com/apk/res/android"

    xmlns:app="http://schemas.android.com/apk/res-auto"

    xmlns:tools="http://schemas.android.com/tools">



    <data>

        <variable

            name="data"

            type="net.julianonunes.myapp.RegisterData" />

    </data>



    ....

</layout>

And here's the build output:

Executing tasks: [clean, :app:assembleDebug]



Configuration on demand is an incubating feature.



> Configure project :app

app: 'annotationProcessor' dependencies won't be recognized as kapt annotation processors. Please change the configuration name to 'kapt' for these artifacts: 'androidx.databinding:databinding-compiler:3.2.0-alpha16'.



> Task :clean

> Task :app:clean

> Task :app:preBuild UP-TO-DATE

> Task :app:preDebugBuild

> Task :app:compileDebugAidl NO-SOURCE

> Task :app:compileDebugRenderscript

> Task :app:checkDebugManifest

> Task :app:generateDebugBuildConfig

> Task :app:prepareLintJar UP-TO-DATE

> Task :app:mainApkListPersistenceDebug

> Task :app:generateDebugResValues

> Task :app:generateDebugResources

> Task :app:mergeDebugResources

> Task :app:createDebugCompatibleScreenManifests

> Task :app:processDebugManifest

> Task :app:splitsDiscoveryTaskDebug

> Task :app:processDebugResources

> Task :app:generateDebugSources

> Task :app:dataBindingExportBuildInfoDebug

> Task :app:transformDataBindingBaseClassLogWithDataBindingMergeGenClassesForDebug

> Task :app:transformDataBindingWithDataBindingMergeArtifactsForDebug

> Task :app:dataBindingGenBaseClassesDebug

Download https://dl.google.com/dl/android/maven2/com/android/databinding/compiler/3.1.2/compiler-3.1.2.pom

Download https://dl.google.com/dl/android/maven2/com/android/databinding/compiler/3.1.2/compiler-3.1.2.jar

> Task :app:kaptGenerateStubsDebugKotlin

e: /home/juliano/Documents/Projetos/myapp/app/build/generated/data_binding_base_class_source_out/debug/dataBindingGenBaseClassesDebug/out/net/julianonunes/myapp/databinding/ActivityMainBinding.java:28: error: cannot find symbol

  protected ActivityMainBinding(DataBindingComponent _bindingComponent, View _root,

                                ^

  symbol:   class DataBindingComponent

  location: class ActivityMainBinding

e: /home/juliano/Documents/Projetos/myapp/app/build/generated/data_binding_base_class_source_out/debug/dataBindingGenBaseClassesDebug/out/net/julianonunes/myapp/databinding/ActivityMainBinding.java:46: error: cannot find symbol

      @Nullable ViewGroup root, boolean attachToRoot, @Nullable DataBindingComponent component) {

                                                                ^

  symbol:   class DataBindingComponent

  location: class ActivityMainBinding

e: /home/juliano/Documents/Projetos/myapp/app/build/generated/data_binding_base_class_source_out/debug/dataBindingGenBaseClassesDebug/out/net/julianonunes/myapp/databinding/ActivityMainBinding.java:57: error: cannot find symbol

      @Nullable DataBindingComponent component) {

                ^

  symbol:   class DataBindingComponent

  location: class ActivityMainBinding

e: /home/juliano/Documents/Projetos/myapp/app/build/generated/data_binding_base_class_source_out/debug/dataBindingGenBaseClassesDebug/out/net/julianonunes/myapp/databinding/ActivityMainBinding.java:68: error: cannot find symbol

      @Nullable DataBindingComponent component) {

                ^

  symbol:   class DataBindingComponent

  location: class ActivityMainBinding

e: [kapt] An exception occurred: java.lang.NullPointerException

    at java.io.File.<init>(File.java:277)

    at android.databinding.annotationprocessor.ProcessExpressions.onHandleStep(ProcessExpressions.java:77)

    at android.databinding.annotationprocessor.ProcessDataBinding$ProcessingStep.runStep(ProcessDataBinding.java:203)

    at android.databinding.annotationprocessor.ProcessDataBinding$ProcessingStep.access$000(ProcessDataBinding.java:188)

    at android.databinding.annotationprocessor.ProcessDataBinding.doProcess(ProcessDataBinding.java:90)

    at android.databinding.annotationprocessor.ProcessDataBinding.process(ProcessDataBinding.java:65)

    at org.jetbrains.kotlin.kapt3.ProcessorWrapper.process(annotationProcessing.kt:131)

    at com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:794)

    at com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:705)

    at com.sun.tools.javac.processing.JavacProcessingEnvironment.access$1800(JavacProcessingEnvironment.java:91)

    at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1035)

    at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1176)

    at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1170)

    at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1068)

    at org.jetbrains.kotlin.kapt3.AnnotationProcessingKt.doAnnotationProcessing(annotationProcessing.kt:87)

    at org.jetbrains.kotlin.kapt3.AnnotationProcessingKt.doAnnotationProcessing$default(annotationProcessing.kt:45)

    at org.jetbrains.kotlin.kapt3.AbstractKapt3Extension.runAnnotationProcessing(Kapt3Extension.kt:257)

    at org.jetbrains.kotlin.kapt3.AbstractKapt3Extension.analysisCompleted(Kapt3Extension.kt:212)

    at org.jetbrains.kotlin.kapt3.ClasspathBasedKapt3Extension.analysisCompleted(Kapt3Extension.kt:95)

    at org.jetbrains.kotlin.cli.jvm.compiler.TopDownAnalyzerFacadeForJVM$analyzeFilesWithJavaIntegration$2.invoke(TopDownAnalyzerFacadeForJVM.kt:97)

    at org.jetbrains.kotlin.cli.jvm.compiler.TopDownAnalyzerFacadeForJVM.analyzeFilesWithJavaIntegration(TopDownAnalyzerFacadeForJVM.kt:107)

    at org.jetbrains.kotlin.cli.jvm.compiler.TopDownAnalyzerFacadeForJVM.analyzeFilesWithJavaIntegration$default(TopDownAnalyzerFacadeForJVM.kt:84)

    at org.jetbrains.kotlin.cli.jvm.compiler.KotlinToJVMBytecodeCompiler$analyze$1.invoke(KotlinToJVMBytecodeCompiler.kt:374)

    at org.jetbrains.kotlin.cli.jvm.compiler.KotlinToJVMBytecodeCompiler$analyze$1.invoke(KotlinToJVMBytecodeCompiler.kt:64)

    at org.jetbrains.kotlin.cli.common.messages.AnalyzerWithCompilerReport.analyzeAndReport(AnalyzerWithCompilerReport.kt:101)

    at org.jetbrains.kotlin.cli.jvm.compiler.KotlinToJVMBytecodeCompiler.analyze(KotlinToJVMBytecodeCompiler.kt:365)

    at org.jetbrains.kotlin.cli.jvm.compiler.KotlinToJVMBytecodeCompiler.compileModules$cli(KotlinToJVMBytecodeCompiler.kt:130)

    at org.jetbrains.kotlin.cli.jvm.K2JVMCompiler.doExecute(K2JVMCompiler.kt:161)

    at org.jetbrains.kotlin.cli.jvm.K2JVMCompiler.doExecute(K2JVMCompiler.kt:63)

    at org.jetbrains.kotlin.cli.common.CLICompiler.execImpl(CLICompiler.java:107)

    at org.jetbrains.kotlin.cli.common.CLICompiler.execImpl(CLICompiler.java:51)

    at org.jetbrains.kotlin.cli.common.CLITool.exec(CLITool.kt:96)

    at org.jetbrains.kotlin.daemon.CompileServiceImpl$compile$1$1$2.invoke(CompileServiceImpl.kt:405)

    at org.jetbrains.kotlin.daemon.CompileServiceImpl$compile$1$1$2.invoke(CompileServiceImpl.kt:98)

    at org.jetbrains.kotlin.daemon.CompileServiceImpl$doCompile$$inlined$ifAlive$lambda$2.invoke(CompileServiceImpl.kt:920)

    at org.jetbrains.kotlin.daemon.CompileServiceImpl$doCompile$$inlined$ifAlive$lambda$2.invoke(CompileServiceImpl.kt:98)

    at org.jetbrains.kotlin.daemon.common.DummyProfiler.withMeasure(PerfUtils.kt:137)

    at org.jetbrains.kotlin.daemon.CompileServiceImpl.checkedCompile(CompileServiceImpl.kt:950)

    at org.jetbrains.kotlin.daemon.CompileServiceImpl.doCompile(CompileServiceImpl.kt:919)

    at org.jetbrains.kotlin.daemon.CompileServiceImpl.compile(CompileServiceImpl.kt:404)

    at sun.reflect.GeneratedMethodAccessor91.invoke(Unknown Source)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

    at java.lang.reflect.Method.invoke(Method.java:498)

    at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:346)

    at sun.rmi.transport.Transport$1.run(Transport.java:200)

    at sun.rmi.transport.Transport$1.run(Transport.java:197)

    at java.security.AccessController.doPrivileged(Native Method)

    at sun.rmi.transport.Transport.serviceCall(Transport.java:196)

    at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)

    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)

    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)

    at java.security.AccessController.doPrivileged(Native Method)

    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)

    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

    at java.lang.Thread.run(Thread.java:745)



> Task :app:kaptDebugKotlin FAILED



FAILURE: Build failed with an exception.



* What went wrong:

Execution failed for task ':app:kaptDebugKotlin'.

> Compilation error. See log for more details



* Try:

Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.



* Get more help at https://help.gradle.org



Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.

See https://docs.gradle.org/4.7/userguide/command_line_interface.html#sec:command_line_warnings



BUILD FAILED in 8s

20 actionable tasks: 19 executed, 1 up-to-date

What is wrong with my project?

PS: The problem also happens on Android Studio 3.1.2

edited May 30 '18 at 11:05

asked May 29 '18 at 23:49

Juliano Nunes Silva Oliveira

3,421941115

did you get any solution?

– Brijesh Joshi
Jul 25 '18 at 9:46

@BrijeshJoshi see my answer below

– Edijae Crusar
Aug 29 '18 at 12:40

For me the true error was actually printed after this. After fixing that error, this one goes away as well.

– Mygod
Sep 19 '18 at 12:42

1

In my case no other error was shown in log, but after reviewing my diffs I found an unimported annotation in some kt file. After fixing import, build works. Seems to be some problem in kapt processor.

– androidguy
Oct 16 '18 at 0:31

Cannot find symbol DataBindingComponent when build from command line using ./gradlew assembleDebug

– Chetan Chaudhari
Jan 10 at 10:09

|
show 1 more comment

Here's my project gradle:

// Top-level build file where you can add configuration options common to all sub-projects/modules.



buildscript {

    ext.kotlin_version = '1.2.41'

    ext.android_plugin_version = '3.2.0-alpha10'

    repositories {

        google()

        jcenter()

    }

    dependencies {

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

        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"



        // NOTE: Do not place your application dependencies here; they belong

        // in the individual module build.gradle files

    }

}



allprojects {

    repositories {

        google()

        jcenter()

    }

}



task clean(type: Delete) {

    delete rootProject.buildDir

}

My module gradle file:

apply plugin: 'com.android.application'



apply plugin: 'kotlin-android'



apply plugin: 'kotlin-kapt'



apply plugin: 'kotlin-android-extensions'



android {

    compileSdkVersion 27

    defaultConfig {

        applicationId "net.julianonunes.myapp"

        minSdkVersion 22

        targetSdkVersion 27

        versionCode 1

        versionName "1.0"

    }

    buildTypes {

        release {

            minifyEnabled false

            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'

        }

    }

    dataBinding {

        enabled = true

    }

}



dependencies {

    implementation fileTree(dir: 'libs', include: ['*.jar'])

    implementation"org.jetbrains.kotlin:kotlin-stdlib:$kotlin_version"

    implementation 'com.android.support:appcompat-v7:27.1.1'

    implementation 'com.android.support.constraint:constraint-layout:1.1.0'

    implementation 'com.squareup.okhttp3:okhttp:3.10.0'

    implementation 'com.android.support:design:27.1.1'

    kapt "com.android.databinding:compiler:3.1.2"

}

My activity's xml:

<?xml version="1.0" encoding="utf-8"?>

<layout xmlns:android="http://schemas.android.com/apk/res/android"

    xmlns:app="http://schemas.android.com/apk/res-auto"

    xmlns:tools="http://schemas.android.com/tools">



    <data>

        <variable

            name="data"

            type="net.julianonunes.myapp.RegisterData" />

    </data>



    ....

</layout>

And here's the build output:

Executing tasks: [clean, :app:assembleDebug]



Configuration on demand is an incubating feature.



> Configure project :app

app: 'annotationProcessor' dependencies won't be recognized as kapt annotation processors. Please change the configuration name to 'kapt' for these artifacts: 'androidx.databinding:databinding-compiler:3.2.0-alpha16'.



> Task :clean

> Task :app:clean

> Task :app:preBuild UP-TO-DATE

> Task :app:preDebugBuild

> Task :app:compileDebugAidl NO-SOURCE

> Task :app:compileDebugRenderscript

> Task :app:checkDebugManifest

> Task :app:generateDebugBuildConfig

> Task :app:prepareLintJar UP-TO-DATE

> Task :app:mainApkListPersistenceDebug

> Task :app:generateDebugResValues

> Task :app:generateDebugResources

> Task :app:mergeDebugResources

> Task :app:createDebugCompatibleScreenManifests

> Task :app:processDebugManifest

> Task :app:splitsDiscoveryTaskDebug

> Task :app:processDebugResources

> Task :app:generateDebugSources

> Task :app:dataBindingExportBuildInfoDebug

> Task :app:transformDataBindingBaseClassLogWithDataBindingMergeGenClassesForDebug

> Task :app:transformDataBindingWithDataBindingMergeArtifactsForDebug

> Task :app:dataBindingGenBaseClassesDebug

Download https://dl.google.com/dl/android/maven2/com/android/databinding/compiler/3.1.2/compiler-3.1.2.pom

Download https://dl.google.com/dl/android/maven2/com/android/databinding/compiler/3.1.2/compiler-3.1.2.jar

> Task :app:kaptGenerateStubsDebugKotlin

e: /home/juliano/Documents/Projetos/myapp/app/build/generated/data_binding_base_class_source_out/debug/dataBindingGenBaseClassesDebug/out/net/julianonunes/myapp/databinding/ActivityMainBinding.java:28: error: cannot find symbol

  protected ActivityMainBinding(DataBindingComponent _bindingComponent, View _root,

                                ^

  symbol:   class DataBindingComponent

  location: class ActivityMainBinding

e: /home/juliano/Documents/Projetos/myapp/app/build/generated/data_binding_base_class_source_out/debug/dataBindingGenBaseClassesDebug/out/net/julianonunes/myapp/databinding/ActivityMainBinding.java:46: error: cannot find symbol

      @Nullable ViewGroup root, boolean attachToRoot, @Nullable DataBindingComponent component) {

                                                                ^

  symbol:   class DataBindingComponent

  location: class ActivityMainBinding

e: /home/juliano/Documents/Projetos/myapp/app/build/generated/data_binding_base_class_source_out/debug/dataBindingGenBaseClassesDebug/out/net/julianonunes/myapp/databinding/ActivityMainBinding.java:57: error: cannot find symbol

      @Nullable DataBindingComponent component) {

                ^

  symbol:   class DataBindingComponent

  location: class ActivityMainBinding

e: /home/juliano/Documents/Projetos/myapp/app/build/generated/data_binding_base_class_source_out/debug/dataBindingGenBaseClassesDebug/out/net/julianonunes/myapp/databinding/ActivityMainBinding.java:68: error: cannot find symbol

      @Nullable DataBindingComponent component) {

                ^

  symbol:   class DataBindingComponent

  location: class ActivityMainBinding

e: [kapt] An exception occurred: java.lang.NullPointerException

    at java.io.File.<init>(File.java:277)

    at android.databinding.annotationprocessor.ProcessExpressions.onHandleStep(ProcessExpressions.java:77)

    at android.databinding.annotationprocessor.ProcessDataBinding$ProcessingStep.runStep(ProcessDataBinding.java:203)

    at android.databinding.annotationprocessor.ProcessDataBinding$ProcessingStep.access$000(ProcessDataBinding.java:188)

    at android.databinding.annotationprocessor.ProcessDataBinding.doProcess(ProcessDataBinding.java:90)

    at android.databinding.annotationprocessor.ProcessDataBinding.process(ProcessDataBinding.java:65)

    at org.jetbrains.kotlin.kapt3.ProcessorWrapper.process(annotationProcessing.kt:131)

    at com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:794)

    at com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:705)

    at com.sun.tools.javac.processing.JavacProcessingEnvironment.access$1800(JavacProcessingEnvironment.java:91)

    at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1035)

    at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1176)

    at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1170)

    at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1068)

    at org.jetbrains.kotlin.kapt3.AnnotationProcessingKt.doAnnotationProcessing(annotationProcessing.kt:87)

    at org.jetbrains.kotlin.kapt3.AnnotationProcessingKt.doAnnotationProcessing$default(annotationProcessing.kt:45)

    at org.jetbrains.kotlin.kapt3.AbstractKapt3Extension.runAnnotationProcessing(Kapt3Extension.kt:257)

    at org.jetbrains.kotlin.kapt3.AbstractKapt3Extension.analysisCompleted(Kapt3Extension.kt:212)

    at org.jetbrains.kotlin.kapt3.ClasspathBasedKapt3Extension.analysisCompleted(Kapt3Extension.kt:95)

    at org.jetbrains.kotlin.cli.jvm.compiler.TopDownAnalyzerFacadeForJVM$analyzeFilesWithJavaIntegration$2.invoke(TopDownAnalyzerFacadeForJVM.kt:97)

    at org.jetbrains.kotlin.cli.jvm.compiler.TopDownAnalyzerFacadeForJVM.analyzeFilesWithJavaIntegration(TopDownAnalyzerFacadeForJVM.kt:107)

    at org.jetbrains.kotlin.cli.jvm.compiler.TopDownAnalyzerFacadeForJVM.analyzeFilesWithJavaIntegration$default(TopDownAnalyzerFacadeForJVM.kt:84)

    at org.jetbrains.kotlin.cli.jvm.compiler.KotlinToJVMBytecodeCompiler$analyze$1.invoke(KotlinToJVMBytecodeCompiler.kt:374)

    at org.jetbrains.kotlin.cli.jvm.compiler.KotlinToJVMBytecodeCompiler$analyze$1.invoke(KotlinToJVMBytecodeCompiler.kt:64)

    at org.jetbrains.kotlin.cli.common.messages.AnalyzerWithCompilerReport.analyzeAndReport(AnalyzerWithCompilerReport.kt:101)

    at org.jetbrains.kotlin.cli.jvm.compiler.KotlinToJVMBytecodeCompiler.analyze(KotlinToJVMBytecodeCompiler.kt:365)

    at org.jetbrains.kotlin.cli.jvm.compiler.KotlinToJVMBytecodeCompiler.compileModules$cli(KotlinToJVMBytecodeCompiler.kt:130)

    at org.jetbrains.kotlin.cli.jvm.K2JVMCompiler.doExecute(K2JVMCompiler.kt:161)

    at org.jetbrains.kotlin.cli.jvm.K2JVMCompiler.doExecute(K2JVMCompiler.kt:63)

    at org.jetbrains.kotlin.cli.common.CLICompiler.execImpl(CLICompiler.java:107)

    at org.jetbrains.kotlin.cli.common.CLICompiler.execImpl(CLICompiler.java:51)

    at org.jetbrains.kotlin.cli.common.CLITool.exec(CLITool.kt:96)

    at org.jetbrains.kotlin.daemon.CompileServiceImpl$compile$1$1$2.invoke(CompileServiceImpl.kt:405)

    at org.jetbrains.kotlin.daemon.CompileServiceImpl$compile$1$1$2.invoke(CompileServiceImpl.kt:98)

    at org.jetbrains.kotlin.daemon.CompileServiceImpl$doCompile$$inlined$ifAlive$lambda$2.invoke(CompileServiceImpl.kt:920)

    at org.jetbrains.kotlin.daemon.CompileServiceImpl$doCompile$$inlined$ifAlive$lambda$2.invoke(CompileServiceImpl.kt:98)

    at org.jetbrains.kotlin.daemon.common.DummyProfiler.withMeasure(PerfUtils.kt:137)

    at org.jetbrains.kotlin.daemon.CompileServiceImpl.checkedCompile(CompileServiceImpl.kt:950)

    at org.jetbrains.kotlin.daemon.CompileServiceImpl.doCompile(CompileServiceImpl.kt:919)

    at org.jetbrains.kotlin.daemon.CompileServiceImpl.compile(CompileServiceImpl.kt:404)

    at sun.reflect.GeneratedMethodAccessor91.invoke(Unknown Source)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

    at java.lang.reflect.Method.invoke(Method.java:498)

    at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:346)

    at sun.rmi.transport.Transport$1.run(Transport.java:200)

    at sun.rmi.transport.Transport$1.run(Transport.java:197)

    at java.security.AccessController.doPrivileged(Native Method)

    at sun.rmi.transport.Transport.serviceCall(Transport.java:196)

    at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)

    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)

    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)

    at java.security.AccessController.doPrivileged(Native Method)

    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)

    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

    at java.lang.Thread.run(Thread.java:745)



> Task :app:kaptDebugKotlin FAILED



FAILURE: Build failed with an exception.



* What went wrong:

Execution failed for task ':app:kaptDebugKotlin'.

> Compilation error. See log for more details



* Try:

Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.



* Get more help at https://help.gradle.org



Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.

See https://docs.gradle.org/4.7/userguide/command_line_interface.html#sec:command_line_warnings



BUILD FAILED in 8s

20 actionable tasks: 19 executed, 1 up-to-date

What is wrong with my project?

PS: The problem also happens on Android Studio 3.1.2

edited May 30 '18 at 11:05

asked May 29 '18 at 23:49

Juliano Nunes Silva Oliveira

3,421941115

Here's my project gradle:

// Top-level build file where you can add configuration options common to all sub-projects/modules.



buildscript {

    ext.kotlin_version = '1.2.41'

    ext.android_plugin_version = '3.2.0-alpha10'

    repositories {

        google()

        jcenter()

    }

    dependencies {

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

        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"



        // NOTE: Do not place your application dependencies here; they belong

        // in the individual module build.gradle files

    }

}



allprojects {

    repositories {

        google()

        jcenter()

    }

}



task clean(type: Delete) {

    delete rootProject.buildDir

}

My module gradle file:

apply plugin: 'com.android.application'



apply plugin: 'kotlin-android'



apply plugin: 'kotlin-kapt'



apply plugin: 'kotlin-android-extensions'



android {

    compileSdkVersion 27

    defaultConfig {

        applicationId "net.julianonunes.myapp"

        minSdkVersion 22

        targetSdkVersion 27

        versionCode 1

        versionName "1.0"

    }

    buildTypes {

        release {

            minifyEnabled false

            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'

        }

    }

    dataBinding {

        enabled = true

    }

}



dependencies {

    implementation fileTree(dir: 'libs', include: ['*.jar'])

    implementation"org.jetbrains.kotlin:kotlin-stdlib:$kotlin_version"

    implementation 'com.android.support:appcompat-v7:27.1.1'

    implementation 'com.android.support.constraint:constraint-layout:1.1.0'

    implementation 'com.squareup.okhttp3:okhttp:3.10.0'

    implementation 'com.android.support:design:27.1.1'

    kapt "com.android.databinding:compiler:3.1.2"

}

My activity's xml:

<?xml version="1.0" encoding="utf-8"?>

<layout xmlns:android="http://schemas.android.com/apk/res/android"

    xmlns:app="http://schemas.android.com/apk/res-auto"

    xmlns:tools="http://schemas.android.com/tools">



    <data>

        <variable

            name="data"

            type="net.julianonunes.myapp.RegisterData" />

    </data>



    ....

</layout>

And here's the build output:

Executing tasks: [clean, :app:assembleDebug]



Configuration on demand is an incubating feature.



> Configure project :app

app: 'annotationProcessor' dependencies won't be recognized as kapt annotation processors. Please change the configuration name to 'kapt' for these artifacts: 'androidx.databinding:databinding-compiler:3.2.0-alpha16'.



> Task :clean

> Task :app:clean

> Task :app:preBuild UP-TO-DATE

> Task :app:preDebugBuild

> Task :app:compileDebugAidl NO-SOURCE

> Task :app:compileDebugRenderscript

> Task :app:checkDebugManifest

> Task :app:generateDebugBuildConfig

> Task :app:prepareLintJar UP-TO-DATE

> Task :app:mainApkListPersistenceDebug

> Task :app:generateDebugResValues

> Task :app:generateDebugResources

> Task :app:mergeDebugResources

> Task :app:createDebugCompatibleScreenManifests

> Task :app:processDebugManifest

> Task :app:splitsDiscoveryTaskDebug

> Task :app:processDebugResources

> Task :app:generateDebugSources

> Task :app:dataBindingExportBuildInfoDebug

> Task :app:transformDataBindingBaseClassLogWithDataBindingMergeGenClassesForDebug

> Task :app:transformDataBindingWithDataBindingMergeArtifactsForDebug

> Task :app:dataBindingGenBaseClassesDebug

Download https://dl.google.com/dl/android/maven2/com/android/databinding/compiler/3.1.2/compiler-3.1.2.pom

Download https://dl.google.com/dl/android/maven2/com/android/databinding/compiler/3.1.2/compiler-3.1.2.jar

> Task :app:kaptGenerateStubsDebugKotlin

e: /home/juliano/Documents/Projetos/myapp/app/build/generated/data_binding_base_class_source_out/debug/dataBindingGenBaseClassesDebug/out/net/julianonunes/myapp/databinding/ActivityMainBinding.java:28: error: cannot find symbol

  protected ActivityMainBinding(DataBindingComponent _bindingComponent, View _root,

                                ^

  symbol:   class DataBindingComponent

  location: class ActivityMainBinding

e: /home/juliano/Documents/Projetos/myapp/app/build/generated/data_binding_base_class_source_out/debug/dataBindingGenBaseClassesDebug/out/net/julianonunes/myapp/databinding/ActivityMainBinding.java:46: error: cannot find symbol

      @Nullable ViewGroup root, boolean attachToRoot, @Nullable DataBindingComponent component) {

                                                                ^

  symbol:   class DataBindingComponent

  location: class ActivityMainBinding

e: /home/juliano/Documents/Projetos/myapp/app/build/generated/data_binding_base_class_source_out/debug/dataBindingGenBaseClassesDebug/out/net/julianonunes/myapp/databinding/ActivityMainBinding.java:57: error: cannot find symbol

      @Nullable DataBindingComponent component) {

                ^

  symbol:   class DataBindingComponent

  location: class ActivityMainBinding

e: /home/juliano/Documents/Projetos/myapp/app/build/generated/data_binding_base_class_source_out/debug/dataBindingGenBaseClassesDebug/out/net/julianonunes/myapp/databinding/ActivityMainBinding.java:68: error: cannot find symbol

      @Nullable DataBindingComponent component) {

                ^

  symbol:   class DataBindingComponent

  location: class ActivityMainBinding

e: [kapt] An exception occurred: java.lang.NullPointerException

    at java.io.File.<init>(File.java:277)

    at android.databinding.annotationprocessor.ProcessExpressions.onHandleStep(ProcessExpressions.java:77)

    at android.databinding.annotationprocessor.ProcessDataBinding$ProcessingStep.runStep(ProcessDataBinding.java:203)

    at android.databinding.annotationprocessor.ProcessDataBinding$ProcessingStep.access$000(ProcessDataBinding.java:188)

    at android.databinding.annotationprocessor.ProcessDataBinding.doProcess(ProcessDataBinding.java:90)

    at android.databinding.annotationprocessor.ProcessDataBinding.process(ProcessDataBinding.java:65)

    at org.jetbrains.kotlin.kapt3.ProcessorWrapper.process(annotationProcessing.kt:131)

    at com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:794)

    at com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:705)

    at com.sun.tools.javac.processing.JavacProcessingEnvironment.access$1800(JavacProcessingEnvironment.java:91)

    at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1035)

    at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1176)

    at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1170)

    at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1068)

    at org.jetbrains.kotlin.kapt3.AnnotationProcessingKt.doAnnotationProcessing(annotationProcessing.kt:87)

    at org.jetbrains.kotlin.kapt3.AnnotationProcessingKt.doAnnotationProcessing$default(annotationProcessing.kt:45)

    at org.jetbrains.kotlin.kapt3.AbstractKapt3Extension.runAnnotationProcessing(Kapt3Extension.kt:257)

    at org.jetbrains.kotlin.kapt3.AbstractKapt3Extension.analysisCompleted(Kapt3Extension.kt:212)

    at org.jetbrains.kotlin.kapt3.ClasspathBasedKapt3Extension.analysisCompleted(Kapt3Extension.kt:95)

    at org.jetbrains.kotlin.cli.jvm.compiler.TopDownAnalyzerFacadeForJVM$analyzeFilesWithJavaIntegration$2.invoke(TopDownAnalyzerFacadeForJVM.kt:97)

    at org.jetbrains.kotlin.cli.jvm.compiler.TopDownAnalyzerFacadeForJVM.analyzeFilesWithJavaIntegration(TopDownAnalyzerFacadeForJVM.kt:107)

    at org.jetbrains.kotlin.cli.jvm.compiler.TopDownAnalyzerFacadeForJVM.analyzeFilesWithJavaIntegration$default(TopDownAnalyzerFacadeForJVM.kt:84)

    at org.jetbrains.kotlin.cli.jvm.compiler.KotlinToJVMBytecodeCompiler$analyze$1.invoke(KotlinToJVMBytecodeCompiler.kt:374)

    at org.jetbrains.kotlin.cli.jvm.compiler.KotlinToJVMBytecodeCompiler$analyze$1.invoke(KotlinToJVMBytecodeCompiler.kt:64)

    at org.jetbrains.kotlin.cli.common.messages.AnalyzerWithCompilerReport.analyzeAndReport(AnalyzerWithCompilerReport.kt:101)

    at org.jetbrains.kotlin.cli.jvm.compiler.KotlinToJVMBytecodeCompiler.analyze(KotlinToJVMBytecodeCompiler.kt:365)

    at org.jetbrains.kotlin.cli.jvm.compiler.KotlinToJVMBytecodeCompiler.compileModules$cli(KotlinToJVMBytecodeCompiler.kt:130)

    at org.jetbrains.kotlin.cli.jvm.K2JVMCompiler.doExecute(K2JVMCompiler.kt:161)

    at org.jetbrains.kotlin.cli.jvm.K2JVMCompiler.doExecute(K2JVMCompiler.kt:63)

    at org.jetbrains.kotlin.cli.common.CLICompiler.execImpl(CLICompiler.java:107)

    at org.jetbrains.kotlin.cli.common.CLICompiler.execImpl(CLICompiler.java:51)

    at org.jetbrains.kotlin.cli.common.CLITool.exec(CLITool.kt:96)

    at org.jetbrains.kotlin.daemon.CompileServiceImpl$compile$1$1$2.invoke(CompileServiceImpl.kt:405)

    at org.jetbrains.kotlin.daemon.CompileServiceImpl$compile$1$1$2.invoke(CompileServiceImpl.kt:98)

    at org.jetbrains.kotlin.daemon.CompileServiceImpl$doCompile$$inlined$ifAlive$lambda$2.invoke(CompileServiceImpl.kt:920)

    at org.jetbrains.kotlin.daemon.CompileServiceImpl$doCompile$$inlined$ifAlive$lambda$2.invoke(CompileServiceImpl.kt:98)

    at org.jetbrains.kotlin.daemon.common.DummyProfiler.withMeasure(PerfUtils.kt:137)

    at org.jetbrains.kotlin.daemon.CompileServiceImpl.checkedCompile(CompileServiceImpl.kt:950)

    at org.jetbrains.kotlin.daemon.CompileServiceImpl.doCompile(CompileServiceImpl.kt:919)

    at org.jetbrains.kotlin.daemon.CompileServiceImpl.compile(CompileServiceImpl.kt:404)

    at sun.reflect.GeneratedMethodAccessor91.invoke(Unknown Source)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

    at java.lang.reflect.Method.invoke(Method.java:498)

    at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:346)

    at sun.rmi.transport.Transport$1.run(Transport.java:200)

    at sun.rmi.transport.Transport$1.run(Transport.java:197)

    at java.security.AccessController.doPrivileged(Native Method)

    at sun.rmi.transport.Transport.serviceCall(Transport.java:196)

    at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)

    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)

    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)

    at java.security.AccessController.doPrivileged(Native Method)

    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)

    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

    at java.lang.Thread.run(Thread.java:745)



> Task :app:kaptDebugKotlin FAILED



FAILURE: Build failed with an exception.



* What went wrong:

Execution failed for task ':app:kaptDebugKotlin'.

> Compilation error. See log for more details



* Try:

Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.



* Get more help at https://help.gradle.org



Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.

See https://docs.gradle.org/4.7/userguide/command_line_interface.html#sec:command_line_warnings



BUILD FAILED in 8s

20 actionable tasks: 19 executed, 1 up-to-date

What is wrong with my project?

PS: The problem also happens on Android Studio 3.1.2

android-studio kotlin android-databinding

edited May 30 '18 at 11:05

asked May 29 '18 at 23:49

Juliano Nunes Silva Oliveira

3,421941115

edited May 30 '18 at 11:05

asked May 29 '18 at 23:49

Juliano Nunes Silva Oliveira

3,421941115

edited May 30 '18 at 11:05

asked May 29 '18 at 23:49

Juliano Nunes Silva Oliveira

3,421941115

asked May 29 '18 at 23:49

Juliano Nunes Silva Oliveira

3,421941115

asked May 29 '18 at 23:49

Juliano Nunes Silva Oliveira

3,421941115

did you get any solution?

– Brijesh Joshi
Jul 25 '18 at 9:46

@BrijeshJoshi see my answer below

– Edijae Crusar
Aug 29 '18 at 12:40

For me the true error was actually printed after this. After fixing that error, this one goes away as well.

– Mygod
Sep 19 '18 at 12:42

1

In my case no other error was shown in log, but after reviewing my diffs I found an unimported annotation in some kt file. After fixing import, build works. Seems to be some problem in kapt processor.

– androidguy
Oct 16 '18 at 0:31

Cannot find symbol DataBindingComponent when build from command line using ./gradlew assembleDebug

– Chetan Chaudhari
Jan 10 at 10:09

|
show 1 more comment

did you get any solution?

– Brijesh Joshi
Jul 25 '18 at 9:46

@BrijeshJoshi see my answer below

– Edijae Crusar
Aug 29 '18 at 12:40

For me the true error was actually printed after this. After fixing that error, this one goes away as well.

– Mygod
Sep 19 '18 at 12:42

1

In my case no other error was shown in log, but after reviewing my diffs I found an unimported annotation in some kt file. After fixing import, build works. Seems to be some problem in kapt processor.

– androidguy
Oct 16 '18 at 0:31

Cannot find symbol DataBindingComponent when build from command line using ./gradlew assembleDebug

– Chetan Chaudhari
Jan 10 at 10:09

did you get any solution?

– Brijesh Joshi
Jul 25 '18 at 9:46

@BrijeshJoshi see my answer below

– Edijae Crusar
Aug 29 '18 at 12:40

For me the true error was actually printed after this. After fixing that error, this one goes away as well.

– Mygod
Sep 19 '18 at 12:42

In my case no other error was shown in log, but after reviewing my diffs I found an unimported annotation in some kt file. After fixing import, build works. Seems to be some problem in kapt processor.

– androidguy
Oct 16 '18 at 0:31

Cannot find symbol DataBindingComponent when build from command line using ./gradlew assembleDebug

– Chetan Chaudhari
Jan 10 at 10:09

|
show 1 more comment

23 Answers
23

active

oldest

votes

Databinding libraries are being refactored as a part of androidx refactoring.

I found the databinding annotation processor dependency link from google's maven repository here.

I've constructed the actual gradle dependency from there.

kapt "androidx.databinding:databinding-compiler:3.2.0-alpha16"

Update
As of Android studio 3.2.0-beta01, databinding no longer needs its annotation processor dependency to be declared in the gradle file, since databinding is capable of resolving its dependency.

edited Nov 14 '18 at 4:34

answered Jun 1 '18 at 6:17

Samuel Robert

4,00552437

2

I have removed this dependency and tried all below solution but nothing seems to be working

– L-X
Sep 25 '18 at 10:11

What studio version are you using?

– Samuel Robert
Sep 25 '18 at 10:12

Android studio 3.3 Canary 11 with gradle 4.10

– L-X
Sep 25 '18 at 10:16

What is your error?

– Samuel Robert
Sep 25 '18 at 10:17

Error : cannot find symbol DataBindingComponent, I hava data binding enable to ture in gradle, I don't know what's the problem

– L-X
Sep 25 '18 at 10:19

|
show 7 more comments

With the following setup

Android Studio 3.2.1 Build #AI-181.5540.7.32.5056338, built on October
8, 2018 JRE: 1.8.0_152-release-1136-b06 x86_64 JVM: OpenJDK 64-Bit
Server VM by JetBrains s.r.o macOS 10.13.3

And DataBinding simply enable by having this in my app build.gradle

apply plugin: 'kotlin-kapt'

and then

    dataBinding {

        enabled = true

    }

and also this in my gradle.wrapper properties

android.databinding.enableV2=true

I had the same errors:

could not find the DataBindingComponent class.

I had more than 100 of them. It turned out that those errors were not important and that the true underlying error was not showed by the IDE. Therefore, I increased the number of errors that the Kotlin compiler can display by adding this in build.gradle:

dataBinding {

    enabled = true

}

kapt {

        javacOptions {

            // Increase the max count of errors from annotation processors.

            // Default is 100.

            option("-Xmaxerrs", 500)

        }

    }

An suddenly, right below all those fake errrors, I saw the real one caused by a failed merge conflict resolution 😔

answered Oct 31 '18 at 19:27

Hamady C.

57859

Hi, how do I do this in a java project?

– Tosin John
Nov 4 '18 at 14:29

1

This is helpful. Thanks!!!

– Ayokunle Paul
Nov 22 '18 at 6:34

1

You are a lifesaver... thank you!

– jordond
Dec 11 '18 at 20:17

bunch of fake errors initially to Do with DataBindingComponent. then when i increase error size. I saw it was an issue with me using the incorrect scope with dagger.

– filthy_wizard
Dec 19 '18 at 13:34

1

I spend days in my life to search errors without messages...! Thanks mate, you are the man of the year :-D

– m.zander
Feb 4 at 13:12

|
show 3 more comments

Just delete the compiler dependency (kapt "com.android.databinding:compiler:$gradleVersion), that worked for me. Apparently, it is provided with binding plugin from 3.2.0.

answered Jun 4 '18 at 13:12

Deividas Strioga

991617

that worked for me too!

– dark_ruby
Nov 6 '18 at 23:11

add a comment |

If You're already using Android Studio 3.2 stable version, Just remove the dependency, it's already included.

answered Sep 25 '18 at 10:51

Narek Hayrapetyan

295415

3

Solved it for me, thank you. They should have added a tooltip/autofix in the IDE.

– SpaceMonkey
Sep 29 '18 at 8:14

3

Double up for this. My error was a little different but this was the root cause. In case someone googles for it: Caused by: java.lang.NullPointerException at java.io.File.<init>(File.java:277) at android.databinding.annotationprocessor.ProcessExpressions.onHandleStep(ProcessExpressions.java:77) at android.databinding.annotationprocessor.ProcessDataBinding$ProcessingStep.runStep(ProcessDataBinding.java:203) at android.databinding.annotationprocessor.ProcessDataBinding$ProcessingStep.access$000(ProcessDataBinding.java:188) ...

– cayleyh
Oct 4 '18 at 23:36

add a comment |

In my case it was a bad dagger annotation. I put custom scope on a Module instead of putting it on a provides method.

¯_(ツ)_/¯

edited Oct 19 '18 at 19:46

CommonsWare

780k13918991947

answered Aug 30 '18 at 12:49

mbonnin

3,15422143

2

I had the same issue .. and fixed it the same way you did...

– Abdulmalek Dery
Oct 24 '18 at 11:47

I had a missing import statement for an annotation value and method parameter. With Dagger 2.19 I got the databinding nonsense above. Luckily Dagger 2.21 pointed me in the right direction.

– Eugen Pechanec
Feb 4 at 16:14

add a comment |

For what it’s worth, I had a similar issue and it was the result of a bad Room query that was related to a data binding.

answered Oct 12 '18 at 17:03

Bink

4141613

1

works for me, I disabled typeconverter for check and it worked

– Murat VAROL
Nov 1 '18 at 11:01

1

Thanks! I had an issue regarding Room too. I was using ArrayList as a return to a query where it has to be a List.

– Van
Dec 26 '18 at 11:11

add a comment |

I had the same issue.

Changing Kapt to annotationProcessor only for DataBinding fixed the problem for me.

answered May 30 '18 at 12:48

Saeed.re

626717

it worked also for me!

– user3471194
Jun 1 '18 at 17:10

add a comment |

i face this problem when updating to android studio 3.2 , i change gradle plugin from 3.2.0 to 3.1.4 and it works fine
--> i think it's a gradle problem , it will be updated for sure very soon

answered Sep 25 '18 at 11:28

B.mansouri

161210

I tried it, it didn't work for me

– L-X
Sep 25 '18 at 13:12

try to change the gradle and to remove kapt "com.android.databinding:compiler:3.1.2"

– B.mansouri
Sep 25 '18 at 15:59

I am not at all using kapt "com.android.databinding:compiler:3.1.2", but I figured out the problem, it was due to the wrong package structure and moving files from one folder to another

– L-X
Sep 27 '18 at 3:04

add a comment |

Same Error here on Android Studio 3.3.1, no Kotlin, pure Java, using androidx

build.gradle contains

    dataBinding {

        enabled true

    }

gradle.properties contains

android.useAndroidX=true

android.enableJetifier=true

android.databinding.enableV2=true

I've been fighting the issue for hours and then solved it as follows:

Temporarily declare an empty interface for DataBindingComponent in your Project (in src/main/java/androidx.databinding/DataBindingComponent.java)

package androidx.databinding;



public interface DataBindingComponent {

}

Let it compile and the error will be gone. But now the actual root error will be revealed. The one that was actually causing all the trouble but was somehow swallowed. In my case it was coming from AutoValue indicating that i was using it incorrectly

error: Parameter type java.lang.Boolean of setter method should be boolean to match getter

fixing that and then removing the dummy interface makes the compiler happy again.

answered Feb 12 at 13:32

Ginie

17333

Thanks a lot for this answer. I have struggled a lot because of this issue.

– Farooq Zaman
Mar 8 at 5:23

Thank you so much for this

– kkl260
Mar 26 at 20:05

add a comment |

Dagger may also be the cause. ~~Changing dagger version from 2.17 back to 2.16 can fix this problem for now.~~

Discussion: https://github.com/google/dagger/issues/1245

~~Update~~

~~Dagger 2.18 is out but unfortunately it still won't work after I tested(Have I missed something?).~~

~~Update2~~

~~Dagger 2.19 also won't work and the discussion is locked.~~

~~But in the google issuetracke, there're solutions/workarounds. I tested and they worked. Check it if you want to use the latest Dagger.~~

Update3

Dagger problem has been fixed in the Android Studio 3.3.

edited Jan 15 at 3:16

answered Sep 25 '18 at 13:41

Dewey Reed

1,2321616

I am also pretty sure that it is caused by Dagger2 in my/our case. The official documentation of DataBindingComponent even mentions dagger: "If using Dagger 2, the developer should extend this interface and annotate the extended interface as a Component." (source: developer.android.com/reference/android/databinding/…). But I don't understand exactly what to do here and if it will fix the error.

– muetzenflo
Oct 21 '18 at 20:55

@muetzenflo Your info seems promising. I'll try to extend that component and see if it can fix the error.

– Dewey Reed
Oct 22 '18 at 9:30

@muetzenflo I've tried the solution but it didn't work. I guess it only takes effects when the app is running but the problem happens in the compile time.

– Dewey Reed
Oct 24 '18 at 4:31

2.19 is out and the issue is still there

– Ernest Zamelczyk
Nov 8 '18 at 9:27

@ErnestZamelczyk You're right. But I found some workaround in the issuetracker. Check the updated answer if you're interested.

– Dewey Reed
Nov 8 '18 at 10:07

add a comment |

i finally fixed my problem because i was using Android Annotations and they released a new Version 4.5.1 1 Hour ago, where they support Grade Plugin 3.2.0.

I was searching for this bug for a week and i´m happy now. Hope this helps you, too!

answered Oct 15 '18 at 10:29

Sandra

312

You've just saved me a lot of time. AndroidAnnotations sucks!!!!

– Krzysztof Kubicki
Dec 11 '18 at 9:32

add a comment |

I have tried classpath 'com.android.tools.build:gradle:3.2.0-beta05'
with and without explicit dependency kapt "androidx.databinding:databinding-compiler:3.3.0-alpha06"

And still getting the same exception.

I have also tried 3.3.0-alpha06 but nothing changed.

UPDATE:
After 2 days, I resolved the issue.
What I did is, manually fixing all the files that had problems, because of Migration to AndroidX (wrong packages in imports and XMLs etc.). Additionally, I needed to update Glide from 4.7 to 4.8. When I fixed all red files the problem disappeared.

edited Aug 27 '18 at 16:28

answered Aug 16 '18 at 18:54

Stanislaw Baranski

30929

add a comment |

I fix it updating Android Studio to Canary 16 AND this in gradle.wrapper.properties distributionUrl=https://services.gradle.org/distributions/gradle-4.7-all.zip

answered May 30 '18 at 1:29

Eduardo Dornel

194

2

I'm already using Canary 16 and Gradle 4.7, but it is not working.

– Juliano Nunes Silva Oliveira
May 30 '18 at 9:03

I'm using Android studio 3.3 Canary 11 and Gradle 4.10, and I am getting the error, so this solution dosen't do for me

– L-X
Sep 25 '18 at 10:03

add a comment |

I solved the error by adding

android.useAndroidX=true

android.enableJetifier=true

in my project's gradle.properties file

answered Aug 29 '18 at 12:39

Edijae Crusar

1,4111652

Didn't work for me. What does the above do? Where did you find it?

– Amir Uval
Sep 17 '18 at 13:46

1

@auval android.useAndroidX: When set to true, this flag indicates that you want to start using AndroidX from now on. If the flag is absent, Android Studio behaves as if the flag were set to false. android.enableJetifier: When set to true, this flag indicates that you want to have tool support (from the Android Gradle plugin) to automatically convert existing third-party libraries as if they were written for AndroidX. If the flag is absent, Android Studio behaves as if the flag were set to false.

– Edijae Crusar
Sep 17 '18 at 14:25

Didn't work for me, I am using Android studio 3.3 these parameters are already present

– L-X
Sep 25 '18 at 10:04

This is definitely required if you migrate to Android X and use databinding etc. I migrated on one machine but the error appeared on a different one because gradle.properties is not in source control

– Daniel Wilson
Nov 26 '18 at 14:04

add a comment |

In my case the issue was resolved by changing:

androidExtensions.experimental = true

(i.e. gradle DSL as a one-liner)

androidExtensions {

    experimental = true

}

apart from could not find the DataBindingComponent class I also had error: incompatible types: NonExistentClass cannot be converted to Annotation associated with kotlinx.android.parcel.Parcelize annotation (@Parcelize)

Android Studio 3.3; gradle-4.10.1-all; tools.build:gradle 3.3.0

answered Jan 23 at 16:19

kosiara - Bartosz Kosarzycki

3,09413039

add a comment |

Just remove kapt "com.android.databinding..." dependency. If you are using Android Studio 3.2 or greater version.

answered Mar 14 at 7:07

Naimish Vinchhi

1769

add a comment |

Something else to try :) I was trying to get the GithubBrowserSample into Android Studio 3.2 (RC3). I kept getting lots of weird errors on databinding even though it doesn't specify data binding versions in the main build.gradle. The solution was to remove these two lines from the gradle.properties:

org.gradle.jvmargs=-Xmx4536m

android.databinding.enableV2=true

answered Sep 18 '18 at 18:04

Daniel Wilson

8,63285376

Tried it, still getting the same error

– L-X
Sep 25 '18 at 10:04

add a comment |

My situation:

Android Studio v3.2.1

com.android.tools.build:gradle:3.2.1

https://services.gradle.org/distributions/gradle-4.10.2-all.zip

I found that by removing databinding from my layout, recompiling the app and then adding the databinding back in it fixed this issue.

I changed the DataBindingUtil.setContentView(...) to just setContentView(...) and reduced my activity layout to the bare minimum:

<FrameLayout xmlns:android="http://schemas.android.com/apk/res/android"

    android:layout_width="match_parent"

    android:layout_height="match_parent">



    <TextView

        android:layout_width="wrap_content"

        android:layout_height="wrap_content"

        android:text="hello"/>



</FrameLayout>

Then add the databinding back in piece by piece.

answered Oct 29 '18 at 23:55

Taskmaster

686510

add a comment |

In my case there was an import error in one of the files. Simply opening that file made imports to happen automatically and thereafter project got built.

It's a pity, that AS gave zero indication to this, neither did error stacktrace.

In case nothing from posted answer helps - just surf through all the files in the project and seek for a file which has incorrect import statement.

answered Oct 30 '18 at 21:23

azizbekian

37.9k687148

add a comment |

It's a bug in jetifier. Here's a workaround for now until the next update. Put this in your project gradle:

buildscript {

    dependencies {

        classpath 'com.android.tools.build.jetifier:jetifier-processor:1.0.0-beta02'

    }

}

answered Nov 8 '18 at 9:31

Ernest Zamelczyk

624519

add a comment |

This is my most stupid mistake!
I have actually created a private variable for Databinding and that was causing this issue.

Just use a lateinit var binding and it Worked.

This could help someone!

answered Nov 27 '18 at 9:35

Kannan_SJD

4491323

add a comment |

My issue was that I tried to enable data binding for my Login module but not the App module. After adding:

dataBinding {

    enabled = true

}

to the App module and removed it from the Login module, it worked.

answered Jan 2 at 23:43

Aleksander Aleksic

456613

add a comment |

If you are using dataroom library, check @Dao annotation in your DAO classes.
In my case, I forgot to add @Dao to my interface of RoomDatabase'Dao.

answered Mar 19 at 14:07

bdpqchen

add a comment |

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

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f50594507%2fcannot-find-symbol-databindingcomponent-on-android-studio-3-2-canary-16-kotlin-p%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

23 Answers
23

active

oldest

votes

23 Answers
23

active

oldest

votes

Databinding libraries are being refactored as a part of androidx refactoring.

I found the databinding annotation processor dependency link from google's maven repository here.

I've constructed the actual gradle dependency from there.

kapt "androidx.databinding:databinding-compiler:3.2.0-alpha16"

edited Nov 14 '18 at 4:34

answered Jun 1 '18 at 6:17

Samuel Robert

4,00552437

2

I have removed this dependency and tried all below solution but nothing seems to be working

– L-X
Sep 25 '18 at 10:11

What studio version are you using?

– Samuel Robert
Sep 25 '18 at 10:12

Android studio 3.3 Canary 11 with gradle 4.10

– L-X
Sep 25 '18 at 10:16

What is your error?

– Samuel Robert
Sep 25 '18 at 10:17

Error : cannot find symbol DataBindingComponent, I hava data binding enable to ture in gradle, I don't know what's the problem

– L-X
Sep 25 '18 at 10:19

|
show 7 more comments

Databinding libraries are being refactored as a part of androidx refactoring.

I found the databinding annotation processor dependency link from google's maven repository here.

I've constructed the actual gradle dependency from there.

kapt "androidx.databinding:databinding-compiler:3.2.0-alpha16"

edited Nov 14 '18 at 4:34

answered Jun 1 '18 at 6:17

Samuel Robert

4,00552437

2

I have removed this dependency and tried all below solution but nothing seems to be working

– L-X
Sep 25 '18 at 10:11

What studio version are you using?

– Samuel Robert
Sep 25 '18 at 10:12

Android studio 3.3 Canary 11 with gradle 4.10

– L-X
Sep 25 '18 at 10:16

What is your error?

– Samuel Robert
Sep 25 '18 at 10:17

Error : cannot find symbol DataBindingComponent, I hava data binding enable to ture in gradle, I don't know what's the problem

– L-X
Sep 25 '18 at 10:19

|
show 7 more comments

Databinding libraries are being refactored as a part of androidx refactoring.

I found the databinding annotation processor dependency link from google's maven repository here.

I've constructed the actual gradle dependency from there.

kapt "androidx.databinding:databinding-compiler:3.2.0-alpha16"

edited Nov 14 '18 at 4:34

answered Jun 1 '18 at 6:17

Samuel Robert

4,00552437

Databinding libraries are being refactored as a part of androidx refactoring.

I found the databinding annotation processor dependency link from google's maven repository here.

I've constructed the actual gradle dependency from there.

kapt "androidx.databinding:databinding-compiler:3.2.0-alpha16"

edited Nov 14 '18 at 4:34

answered Jun 1 '18 at 6:17

Samuel Robert

4,00552437

edited Nov 14 '18 at 4:34

answered Jun 1 '18 at 6:17

Samuel Robert

4,00552437

answered Jun 1 '18 at 6:17

Samuel Robert

4,00552437

answered Jun 1 '18 at 6:17

Samuel Robert

4,00552437

2

I have removed this dependency and tried all below solution but nothing seems to be working

– L-X
Sep 25 '18 at 10:11

What studio version are you using?

– Samuel Robert
Sep 25 '18 at 10:12

Android studio 3.3 Canary 11 with gradle 4.10

– L-X
Sep 25 '18 at 10:16

What is your error?

– Samuel Robert
Sep 25 '18 at 10:17

Error : cannot find symbol DataBindingComponent, I hava data binding enable to ture in gradle, I don't know what's the problem

– L-X
Sep 25 '18 at 10:19

|
show 7 more comments

2

I have removed this dependency and tried all below solution but nothing seems to be working

– L-X
Sep 25 '18 at 10:11

What studio version are you using?

– Samuel Robert
Sep 25 '18 at 10:12

Android studio 3.3 Canary 11 with gradle 4.10

– L-X
Sep 25 '18 at 10:16

What is your error?

– Samuel Robert
Sep 25 '18 at 10:17

Error : cannot find symbol DataBindingComponent, I hava data binding enable to ture in gradle, I don't know what's the problem

– L-X
Sep 25 '18 at 10:19

I have removed this dependency and tried all below solution but nothing seems to be working

– L-X
Sep 25 '18 at 10:11

What studio version are you using?

– Samuel Robert
Sep 25 '18 at 10:12

Android studio 3.3 Canary 11 with gradle 4.10

– L-X
Sep 25 '18 at 10:16

What is your error?

– Samuel Robert
Sep 25 '18 at 10:17

Error : cannot find symbol DataBindingComponent, I hava data binding enable to ture in gradle, I don't know what's the problem

– L-X
Sep 25 '18 at 10:19

|
show 7 more comments

With the following setup

Android Studio 3.2.1 Build #AI-181.5540.7.32.5056338, built on October
8, 2018 JRE: 1.8.0_152-release-1136-b06 x86_64 JVM: OpenJDK 64-Bit
Server VM by JetBrains s.r.o macOS 10.13.3

And DataBinding simply enable by having this in my app build.gradle

apply plugin: 'kotlin-kapt'

and then

    dataBinding {

        enabled = true

    }

and also this in my gradle.wrapper properties

android.databinding.enableV2=true

I had the same errors:

could not find the DataBindingComponent class.

dataBinding {

    enabled = true

}

kapt {

        javacOptions {

            // Increase the max count of errors from annotation processors.

            // Default is 100.

            option("-Xmaxerrs", 500)

        }

    }

An suddenly, right below all those fake errrors, I saw the real one caused by a failed merge conflict resolution 😔

answered Oct 31 '18 at 19:27

Hamady C.

57859

Hi, how do I do this in a java project?

– Tosin John
Nov 4 '18 at 14:29

1

This is helpful. Thanks!!!

– Ayokunle Paul
Nov 22 '18 at 6:34

1

You are a lifesaver... thank you!

– jordond
Dec 11 '18 at 20:17

bunch of fake errors initially to Do with DataBindingComponent. then when i increase error size. I saw it was an issue with me using the incorrect scope with dagger.

– filthy_wizard
Dec 19 '18 at 13:34

1

I spend days in my life to search errors without messages...! Thanks mate, you are the man of the year :-D

– m.zander
Feb 4 at 13:12

|
show 3 more comments

With the following setup

Android Studio 3.2.1 Build #AI-181.5540.7.32.5056338, built on October
8, 2018 JRE: 1.8.0_152-release-1136-b06 x86_64 JVM: OpenJDK 64-Bit
Server VM by JetBrains s.r.o macOS 10.13.3

And DataBinding simply enable by having this in my app build.gradle

apply plugin: 'kotlin-kapt'

and then

    dataBinding {

        enabled = true

    }

and also this in my gradle.wrapper properties

android.databinding.enableV2=true

I had the same errors:

could not find the DataBindingComponent class.

dataBinding {

    enabled = true

}

kapt {

        javacOptions {

            // Increase the max count of errors from annotation processors.

            // Default is 100.

            option("-Xmaxerrs", 500)

        }

    }

An suddenly, right below all those fake errrors, I saw the real one caused by a failed merge conflict resolution 😔

answered Oct 31 '18 at 19:27

Hamady C.

57859

Hi, how do I do this in a java project?

– Tosin John
Nov 4 '18 at 14:29

1

This is helpful. Thanks!!!

– Ayokunle Paul
Nov 22 '18 at 6:34

1

You are a lifesaver... thank you!

– jordond
Dec 11 '18 at 20:17

bunch of fake errors initially to Do with DataBindingComponent. then when i increase error size. I saw it was an issue with me using the incorrect scope with dagger.

– filthy_wizard
Dec 19 '18 at 13:34

1

I spend days in my life to search errors without messages...! Thanks mate, you are the man of the year :-D

– m.zander
Feb 4 at 13:12

|
show 3 more comments

With the following setup

Android Studio 3.2.1 Build #AI-181.5540.7.32.5056338, built on October
8, 2018 JRE: 1.8.0_152-release-1136-b06 x86_64 JVM: OpenJDK 64-Bit
Server VM by JetBrains s.r.o macOS 10.13.3

And DataBinding simply enable by having this in my app build.gradle

apply plugin: 'kotlin-kapt'

and then

    dataBinding {

        enabled = true

    }

and also this in my gradle.wrapper properties

android.databinding.enableV2=true

I had the same errors:

could not find the DataBindingComponent class.

dataBinding {

    enabled = true

}

kapt {

        javacOptions {

            // Increase the max count of errors from annotation processors.

            // Default is 100.

            option("-Xmaxerrs", 500)

        }

    }

An suddenly, right below all those fake errrors, I saw the real one caused by a failed merge conflict resolution 😔

answered Oct 31 '18 at 19:27

Hamady C.

57859

With the following setup

Android Studio 3.2.1 Build #AI-181.5540.7.32.5056338, built on October
8, 2018 JRE: 1.8.0_152-release-1136-b06 x86_64 JVM: OpenJDK 64-Bit
Server VM by JetBrains s.r.o macOS 10.13.3

And DataBinding simply enable by having this in my app build.gradle

apply plugin: 'kotlin-kapt'

and then

    dataBinding {

        enabled = true

    }

and also this in my gradle.wrapper properties

android.databinding.enableV2=true

I had the same errors:

could not find the DataBindingComponent class.

dataBinding {

    enabled = true

}

kapt {

        javacOptions {

            // Increase the max count of errors from annotation processors.

            // Default is 100.

            option("-Xmaxerrs", 500)

        }

    }

An suddenly, right below all those fake errrors, I saw the real one caused by a failed merge conflict resolution 😔

answered Oct 31 '18 at 19:27

Hamady C.

57859

answered Oct 31 '18 at 19:27

Hamady C.

57859

answered Oct 31 '18 at 19:27

Hamady C.

57859

answered Oct 31 '18 at 19:27

Hamady C.

57859

Hi, how do I do this in a java project?

– Tosin John
Nov 4 '18 at 14:29

1

This is helpful. Thanks!!!

– Ayokunle Paul
Nov 22 '18 at 6:34

1

You are a lifesaver... thank you!

– jordond
Dec 11 '18 at 20:17

bunch of fake errors initially to Do with DataBindingComponent. then when i increase error size. I saw it was an issue with me using the incorrect scope with dagger.

– filthy_wizard
Dec 19 '18 at 13:34

1

I spend days in my life to search errors without messages...! Thanks mate, you are the man of the year :-D

– m.zander
Feb 4 at 13:12

|
show 3 more comments

Hi, how do I do this in a java project?

– Tosin John
Nov 4 '18 at 14:29

1

This is helpful. Thanks!!!

– Ayokunle Paul
Nov 22 '18 at 6:34

1

You are a lifesaver... thank you!

– jordond
Dec 11 '18 at 20:17

bunch of fake errors initially to Do with DataBindingComponent. then when i increase error size. I saw it was an issue with me using the incorrect scope with dagger.

– filthy_wizard
Dec 19 '18 at 13:34

1

I spend days in my life to search errors without messages...! Thanks mate, you are the man of the year :-D

– m.zander
Feb 4 at 13:12

Hi, how do I do this in a java project?

– Tosin John
Nov 4 '18 at 14:29

This is helpful. Thanks!!!

– Ayokunle Paul
Nov 22 '18 at 6:34

You are a lifesaver... thank you!

– jordond
Dec 11 '18 at 20:17

bunch of fake errors initially to Do with DataBindingComponent. then when i increase error size. I saw it was an issue with me using the incorrect scope with dagger.

– filthy_wizard
Dec 19 '18 at 13:34

I spend days in my life to search errors without messages...! Thanks mate, you are the man of the year :-D

– m.zander
Feb 4 at 13:12

|
show 3 more comments

Just delete the compiler dependency (kapt "com.android.databinding:compiler:$gradleVersion), that worked for me. Apparently, it is provided with binding plugin from 3.2.0.

answered Jun 4 '18 at 13:12

Deividas Strioga

991617

that worked for me too!

– dark_ruby
Nov 6 '18 at 23:11

add a comment |

Just delete the compiler dependency (kapt "com.android.databinding:compiler:$gradleVersion), that worked for me. Apparently, it is provided with binding plugin from 3.2.0.

answered Jun 4 '18 at 13:12

Deividas Strioga

991617

that worked for me too!

– dark_ruby
Nov 6 '18 at 23:11

add a comment |

Just delete the compiler dependency (kapt "com.android.databinding:compiler:$gradleVersion), that worked for me. Apparently, it is provided with binding plugin from 3.2.0.

answered Jun 4 '18 at 13:12

Deividas Strioga

991617

Just delete the compiler dependency (kapt "com.android.databinding:compiler:$gradleVersion), that worked for me. Apparently, it is provided with binding plugin from 3.2.0.

answered Jun 4 '18 at 13:12

Deividas Strioga

991617

answered Jun 4 '18 at 13:12

Deividas Strioga

991617

answered Jun 4 '18 at 13:12

Deividas Strioga

991617

answered Jun 4 '18 at 13:12

Deividas Strioga

991617

that worked for me too!

– dark_ruby
Nov 6 '18 at 23:11

add a comment |

that worked for me too!

– dark_ruby
Nov 6 '18 at 23:11

that worked for me too!

– dark_ruby
Nov 6 '18 at 23:11

add a comment |

If You're already using Android Studio 3.2 stable version, Just remove the dependency, it's already included.

answered Sep 25 '18 at 10:51

Narek Hayrapetyan

295415

3

Solved it for me, thank you. They should have added a tooltip/autofix in the IDE.

– SpaceMonkey
Sep 29 '18 at 8:14

3

Double up for this. My error was a little different but this was the root cause. In case someone googles for it: Caused by: java.lang.NullPointerException at java.io.File.<init>(File.java:277) at android.databinding.annotationprocessor.ProcessExpressions.onHandleStep(ProcessExpressions.java:77) at android.databinding.annotationprocessor.ProcessDataBinding$ProcessingStep.runStep(ProcessDataBinding.java:203) at android.databinding.annotationprocessor.ProcessDataBinding$ProcessingStep.access$000(ProcessDataBinding.java:188) ...

– cayleyh
Oct 4 '18 at 23:36

add a comment |

If You're already using Android Studio 3.2 stable version, Just remove the dependency, it's already included.

answered Sep 25 '18 at 10:51

Narek Hayrapetyan

295415

3

Solved it for me, thank you. They should have added a tooltip/autofix in the IDE.

– SpaceMonkey
Sep 29 '18 at 8:14

3

Double up for this. My error was a little different but this was the root cause. In case someone googles for it: Caused by: java.lang.NullPointerException at java.io.File.<init>(File.java:277) at android.databinding.annotationprocessor.ProcessExpressions.onHandleStep(ProcessExpressions.java:77) at android.databinding.annotationprocessor.ProcessDataBinding$ProcessingStep.runStep(ProcessDataBinding.java:203) at android.databinding.annotationprocessor.ProcessDataBinding$ProcessingStep.access$000(ProcessDataBinding.java:188) ...

– cayleyh
Oct 4 '18 at 23:36

add a comment |

If You're already using Android Studio 3.2 stable version, Just remove the dependency, it's already included.

answered Sep 25 '18 at 10:51

Narek Hayrapetyan

295415

If You're already using Android Studio 3.2 stable version, Just remove the dependency, it's already included.

answered Sep 25 '18 at 10:51

Narek Hayrapetyan

295415

answered Sep 25 '18 at 10:51

Narek Hayrapetyan

295415

answered Sep 25 '18 at 10:51

Narek Hayrapetyan

295415

answered Sep 25 '18 at 10:51

Narek Hayrapetyan

295415

3

Solved it for me, thank you. They should have added a tooltip/autofix in the IDE.

– SpaceMonkey
Sep 29 '18 at 8:14

3

Double up for this. My error was a little different but this was the root cause. In case someone googles for it: Caused by: java.lang.NullPointerException at java.io.File.<init>(File.java:277) at android.databinding.annotationprocessor.ProcessExpressions.onHandleStep(ProcessExpressions.java:77) at android.databinding.annotationprocessor.ProcessDataBinding$ProcessingStep.runStep(ProcessDataBinding.java:203) at android.databinding.annotationprocessor.ProcessDataBinding$ProcessingStep.access$000(ProcessDataBinding.java:188) ...

– cayleyh
Oct 4 '18 at 23:36

add a comment |

3

Solved it for me, thank you. They should have added a tooltip/autofix in the IDE.

– SpaceMonkey
Sep 29 '18 at 8:14

3

Double up for this. My error was a little different but this was the root cause. In case someone googles for it: Caused by: java.lang.NullPointerException at java.io.File.<init>(File.java:277) at android.databinding.annotationprocessor.ProcessExpressions.onHandleStep(ProcessExpressions.java:77) at android.databinding.annotationprocessor.ProcessDataBinding$ProcessingStep.runStep(ProcessDataBinding.java:203) at android.databinding.annotationprocessor.ProcessDataBinding$ProcessingStep.access$000(ProcessDataBinding.java:188) ...

– cayleyh
Oct 4 '18 at 23:36

Solved it for me, thank you. They should have added a tooltip/autofix in the IDE.

– SpaceMonkey
Sep 29 '18 at 8:14

Double up for this. My error was a little different but this was the root cause. In case someone googles for it:

Caused by: java.lang.NullPointerException   at java.io.File.<init>(File.java:277)   at android.databinding.annotationprocessor.ProcessExpressions.onHandleStep(ProcessExpressions.java:77)   at android.databinding.annotationprocessor.ProcessDataBinding$ProcessingStep.runStep(ProcessDataBinding.java:203)   at android.databinding.annotationprocessor.ProcessDataBinding$ProcessingStep.access$000(ProcessDataBinding.java:188) ...

– cayleyh
Oct 4 '18 at 23:36

Double up for this. My error was a little different but this was the root cause. In case someone googles for it:

Caused by: java.lang.NullPointerException   at java.io.File.<init>(File.java:277)   at android.databinding.annotationprocessor.ProcessExpressions.onHandleStep(ProcessExpressions.java:77)   at android.databinding.annotationprocessor.ProcessDataBinding$ProcessingStep.runStep(ProcessDataBinding.java:203)   at android.databinding.annotationprocessor.ProcessDataBinding$ProcessingStep.access$000(ProcessDataBinding.java:188) ...

– cayleyh
Oct 4 '18 at 23:36

add a comment |

In my case it was a bad dagger annotation. I put custom scope on a Module instead of putting it on a provides method.

¯_(ツ)_/¯

edited Oct 19 '18 at 19:46

CommonsWare

780k13918991947

answered Aug 30 '18 at 12:49

mbonnin

3,15422143

2

I had the same issue .. and fixed it the same way you did...

– Abdulmalek Dery
Oct 24 '18 at 11:47

I had a missing import statement for an annotation value and method parameter. With Dagger 2.19 I got the databinding nonsense above. Luckily Dagger 2.21 pointed me in the right direction.

– Eugen Pechanec
Feb 4 at 16:14

add a comment |

In my case it was a bad dagger annotation. I put custom scope on a Module instead of putting it on a provides method.

¯_(ツ)_/¯

edited Oct 19 '18 at 19:46

CommonsWare

780k13918991947

answered Aug 30 '18 at 12:49

mbonnin

3,15422143

2

I had the same issue .. and fixed it the same way you did...

– Abdulmalek Dery
Oct 24 '18 at 11:47

I had a missing import statement for an annotation value and method parameter. With Dagger 2.19 I got the databinding nonsense above. Luckily Dagger 2.21 pointed me in the right direction.

– Eugen Pechanec
Feb 4 at 16:14

add a comment |

In my case it was a bad dagger annotation. I put custom scope on a Module instead of putting it on a provides method.

¯_(ツ)_/¯

edited Oct 19 '18 at 19:46

CommonsWare

780k13918991947

answered Aug 30 '18 at 12:49

mbonnin

3,15422143

In my case it was a bad dagger annotation. I put custom scope on a Module instead of putting it on a provides method.

¯_(ツ)_/¯

edited Oct 19 '18 at 19:46

CommonsWare

780k13918991947

answered Aug 30 '18 at 12:49

mbonnin

3,15422143

edited Oct 19 '18 at 19:46

CommonsWare

780k13918991947

edited Oct 19 '18 at 19:46

CommonsWare

780k13918991947

edited Oct 19 '18 at 19:46

CommonsWare

780k13918991947

answered Aug 30 '18 at 12:49

mbonnin

3,15422143

answered Aug 30 '18 at 12:49

mbonnin

3,15422143

answered Aug 30 '18 at 12:49

mbonnin

3,15422143

2

I had the same issue .. and fixed it the same way you did...

– Abdulmalek Dery
Oct 24 '18 at 11:47

I had a missing import statement for an annotation value and method parameter. With Dagger 2.19 I got the databinding nonsense above. Luckily Dagger 2.21 pointed me in the right direction.

– Eugen Pechanec
Feb 4 at 16:14

add a comment |

2

I had the same issue .. and fixed it the same way you did...

– Abdulmalek Dery
Oct 24 '18 at 11:47

I had a missing import statement for an annotation value and method parameter. With Dagger 2.19 I got the databinding nonsense above. Luckily Dagger 2.21 pointed me in the right direction.

– Eugen Pechanec
Feb 4 at 16:14

I had the same issue .. and fixed it the same way you did...

– Abdulmalek Dery
Oct 24 '18 at 11:47

I had a missing import statement for an annotation value and method parameter. With Dagger 2.19 I got the databinding nonsense above. Luckily Dagger 2.21 pointed me in the right direction.

– Eugen Pechanec
Feb 4 at 16:14

add a comment |

For what it’s worth, I had a similar issue and it was the result of a bad Room query that was related to a data binding.

answered Oct 12 '18 at 17:03

Bink

4141613

1

works for me, I disabled typeconverter for check and it worked

– Murat VAROL
Nov 1 '18 at 11:01

1

Thanks! I had an issue regarding Room too. I was using ArrayList as a return to a query where it has to be a List.

– Van
Dec 26 '18 at 11:11

add a comment |

For what it’s worth, I had a similar issue and it was the result of a bad Room query that was related to a data binding.

answered Oct 12 '18 at 17:03

Bink

4141613

1

works for me, I disabled typeconverter for check and it worked

– Murat VAROL
Nov 1 '18 at 11:01

1

Thanks! I had an issue regarding Room too. I was using ArrayList as a return to a query where it has to be a List.

– Van
Dec 26 '18 at 11:11

add a comment |

For what it’s worth, I had a similar issue and it was the result of a bad Room query that was related to a data binding.

answered Oct 12 '18 at 17:03

Bink

4141613

For what it’s worth, I had a similar issue and it was the result of a bad Room query that was related to a data binding.

answered Oct 12 '18 at 17:03

Bink

4141613

answered Oct 12 '18 at 17:03

Bink

4141613

answered Oct 12 '18 at 17:03

Bink

4141613

answered Oct 12 '18 at 17:03

Bink

4141613

1

works for me, I disabled typeconverter for check and it worked

– Murat VAROL
Nov 1 '18 at 11:01

1

Thanks! I had an issue regarding Room too. I was using ArrayList as a return to a query where it has to be a List.

– Van
Dec 26 '18 at 11:11

add a comment |

1

works for me, I disabled typeconverter for check and it worked

– Murat VAROL
Nov 1 '18 at 11:01

1

Thanks! I had an issue regarding Room too. I was using ArrayList as a return to a query where it has to be a List.

– Van
Dec 26 '18 at 11:11

works for me, I disabled typeconverter for check and it worked

– Murat VAROL
Nov 1 '18 at 11:01

Thanks! I had an issue regarding Room too. I was using ArrayList as a return to a query where it has to be a List.

– Van
Dec 26 '18 at 11:11

add a comment |

I had the same issue.

Changing Kapt to annotationProcessor only for DataBinding fixed the problem for me.

answered May 30 '18 at 12:48

Saeed.re

626717

it worked also for me!

– user3471194
Jun 1 '18 at 17:10

add a comment |

I had the same issue.

Changing Kapt to annotationProcessor only for DataBinding fixed the problem for me.

answered May 30 '18 at 12:48

Saeed.re

626717

it worked also for me!

– user3471194
Jun 1 '18 at 17:10

add a comment |

I had the same issue.

Changing Kapt to annotationProcessor only for DataBinding fixed the problem for me.

answered May 30 '18 at 12:48

Saeed.re

626717

I had the same issue.

Changing Kapt to annotationProcessor only for DataBinding fixed the problem for me.

answered May 30 '18 at 12:48

Saeed.re

626717

answered May 30 '18 at 12:48

Saeed.re

626717

answered May 30 '18 at 12:48

Saeed.re

626717

answered May 30 '18 at 12:48

Saeed.re

626717

it worked also for me!

– user3471194
Jun 1 '18 at 17:10

add a comment |

it worked also for me!

– user3471194
Jun 1 '18 at 17:10

it worked also for me!

– user3471194
Jun 1 '18 at 17:10

add a comment |

i face this problem when updating to android studio 3.2 , i change gradle plugin from 3.2.0 to 3.1.4 and it works fine
--> i think it's a gradle problem , it will be updated for sure very soon

answered Sep 25 '18 at 11:28

B.mansouri

161210

I tried it, it didn't work for me

– L-X
Sep 25 '18 at 13:12

try to change the gradle and to remove kapt "com.android.databinding:compiler:3.1.2"

– B.mansouri
Sep 25 '18 at 15:59

I am not at all using kapt "com.android.databinding:compiler:3.1.2", but I figured out the problem, it was due to the wrong package structure and moving files from one folder to another

– L-X
Sep 27 '18 at 3:04

add a comment |

i face this problem when updating to android studio 3.2 , i change gradle plugin from 3.2.0 to 3.1.4 and it works fine
--> i think it's a gradle problem , it will be updated for sure very soon

answered Sep 25 '18 at 11:28

B.mansouri

161210

I tried it, it didn't work for me

– L-X
Sep 25 '18 at 13:12

try to change the gradle and to remove kapt "com.android.databinding:compiler:3.1.2"

– B.mansouri
Sep 25 '18 at 15:59

I am not at all using kapt "com.android.databinding:compiler:3.1.2", but I figured out the problem, it was due to the wrong package structure and moving files from one folder to another

– L-X
Sep 27 '18 at 3:04

add a comment |

i face this problem when updating to android studio 3.2 , i change gradle plugin from 3.2.0 to 3.1.4 and it works fine
--> i think it's a gradle problem , it will be updated for sure very soon

answered Sep 25 '18 at 11:28

B.mansouri

161210

i face this problem when updating to android studio 3.2 , i change gradle plugin from 3.2.0 to 3.1.4 and it works fine
--> i think it's a gradle problem , it will be updated for sure very soon

answered Sep 25 '18 at 11:28

B.mansouri

161210

answered Sep 25 '18 at 11:28

B.mansouri

161210

answered Sep 25 '18 at 11:28

B.mansouri

161210

answered Sep 25 '18 at 11:28

B.mansouri

161210

I tried it, it didn't work for me

– L-X
Sep 25 '18 at 13:12

try to change the gradle and to remove kapt "com.android.databinding:compiler:3.1.2"

– B.mansouri
Sep 25 '18 at 15:59

I am not at all using kapt "com.android.databinding:compiler:3.1.2", but I figured out the problem, it was due to the wrong package structure and moving files from one folder to another

– L-X
Sep 27 '18 at 3:04

add a comment |

I tried it, it didn't work for me

– L-X
Sep 25 '18 at 13:12

try to change the gradle and to remove kapt "com.android.databinding:compiler:3.1.2"

– B.mansouri
Sep 25 '18 at 15:59

I am not at all using kapt "com.android.databinding:compiler:3.1.2", but I figured out the problem, it was due to the wrong package structure and moving files from one folder to another

– L-X
Sep 27 '18 at 3:04

I tried it, it didn't work for me

– L-X
Sep 25 '18 at 13:12

try to change the gradle and to remove kapt "com.android.databinding:compiler:3.1.2"

– B.mansouri
Sep 25 '18 at 15:59

I am not at all using kapt "com.android.databinding:compiler:3.1.2", but I figured out the problem, it was due to the wrong package structure and moving files from one folder to another

– L-X
Sep 27 '18 at 3:04

add a comment |

Same Error here on Android Studio 3.3.1, no Kotlin, pure Java, using androidx

build.gradle contains

    dataBinding {

        enabled true

    }

gradle.properties contains

android.useAndroidX=true

android.enableJetifier=true

android.databinding.enableV2=true

I've been fighting the issue for hours and then solved it as follows:

Temporarily declare an empty interface for DataBindingComponent in your Project (in src/main/java/androidx.databinding/DataBindingComponent.java)

package androidx.databinding;



public interface DataBindingComponent {

}

error: Parameter type java.lang.Boolean of setter method should be boolean to match getter

fixing that and then removing the dummy interface makes the compiler happy again.

answered Feb 12 at 13:32

Ginie

17333

Thanks a lot for this answer. I have struggled a lot because of this issue.

– Farooq Zaman
Mar 8 at 5:23

Thank you so much for this

– kkl260
Mar 26 at 20:05

add a comment |

Same Error here on Android Studio 3.3.1, no Kotlin, pure Java, using androidx

build.gradle contains

    dataBinding {

        enabled true

    }

gradle.properties contains

android.useAndroidX=true

android.enableJetifier=true

android.databinding.enableV2=true

I've been fighting the issue for hours and then solved it as follows:

Temporarily declare an empty interface for DataBindingComponent in your Project (in src/main/java/androidx.databinding/DataBindingComponent.java)

package androidx.databinding;



public interface DataBindingComponent {

}

error: Parameter type java.lang.Boolean of setter method should be boolean to match getter

fixing that and then removing the dummy interface makes the compiler happy again.

answered Feb 12 at 13:32

Ginie

17333

Thanks a lot for this answer. I have struggled a lot because of this issue.

– Farooq Zaman
Mar 8 at 5:23

Thank you so much for this

– kkl260
Mar 26 at 20:05

add a comment |

Same Error here on Android Studio 3.3.1, no Kotlin, pure Java, using androidx

build.gradle contains

    dataBinding {

        enabled true

    }

gradle.properties contains

android.useAndroidX=true

android.enableJetifier=true

android.databinding.enableV2=true

I've been fighting the issue for hours and then solved it as follows:

Temporarily declare an empty interface for DataBindingComponent in your Project (in src/main/java/androidx.databinding/DataBindingComponent.java)

package androidx.databinding;



public interface DataBindingComponent {

}

error: Parameter type java.lang.Boolean of setter method should be boolean to match getter

fixing that and then removing the dummy interface makes the compiler happy again.

answered Feb 12 at 13:32

Ginie

17333

Same Error here on Android Studio 3.3.1, no Kotlin, pure Java, using androidx

build.gradle contains

    dataBinding {

        enabled true

    }

gradle.properties contains

android.useAndroidX=true

android.enableJetifier=true

android.databinding.enableV2=true

I've been fighting the issue for hours and then solved it as follows:

Temporarily declare an empty interface for DataBindingComponent in your Project (in src/main/java/androidx.databinding/DataBindingComponent.java)

package androidx.databinding;



public interface DataBindingComponent {

}

error: Parameter type java.lang.Boolean of setter method should be boolean to match getter

fixing that and then removing the dummy interface makes the compiler happy again.

answered Feb 12 at 13:32

Ginie

17333

answered Feb 12 at 13:32

Ginie

17333

answered Feb 12 at 13:32

Ginie

17333

answered Feb 12 at 13:32

Ginie

17333

Thanks a lot for this answer. I have struggled a lot because of this issue.

– Farooq Zaman
Mar 8 at 5:23

Thank you so much for this

– kkl260
Mar 26 at 20:05

add a comment |

Thanks a lot for this answer. I have struggled a lot because of this issue.

– Farooq Zaman
Mar 8 at 5:23

Thank you so much for this

– kkl260
Mar 26 at 20:05

Thanks a lot for this answer. I have struggled a lot because of this issue.

– Farooq Zaman
Mar 8 at 5:23

Thank you so much for this

– kkl260
Mar 26 at 20:05

add a comment |

Dagger may also be the cause. ~~Changing dagger version from 2.17 back to 2.16 can fix this problem for now.~~

Discussion: https://github.com/google/dagger/issues/1245

~~Update~~

~~Dagger 2.18 is out but unfortunately it still won't work after I tested(Have I missed something?).~~

~~Update2~~

~~Dagger 2.19 also won't work and the discussion is locked.~~

~~But in the google issuetracke, there're solutions/workarounds. I tested and they worked. Check it if you want to use the latest Dagger.~~

Update3

Dagger problem has been fixed in the Android Studio 3.3.

edited Jan 15 at 3:16

answered Sep 25 '18 at 13:41

Dewey Reed

1,2321616

I am also pretty sure that it is caused by Dagger2 in my/our case. The official documentation of DataBindingComponent even mentions dagger: "If using Dagger 2, the developer should extend this interface and annotate the extended interface as a Component." (source: developer.android.com/reference/android/databinding/…). But I don't understand exactly what to do here and if it will fix the error.

– muetzenflo
Oct 21 '18 at 20:55

@muetzenflo Your info seems promising. I'll try to extend that component and see if it can fix the error.

– Dewey Reed
Oct 22 '18 at 9:30

@muetzenflo I've tried the solution but it didn't work. I guess it only takes effects when the app is running but the problem happens in the compile time.

– Dewey Reed
Oct 24 '18 at 4:31

2.19 is out and the issue is still there

– Ernest Zamelczyk
Nov 8 '18 at 9:27

@ErnestZamelczyk You're right. But I found some workaround in the issuetracker. Check the updated answer if you're interested.

– Dewey Reed
Nov 8 '18 at 10:07

add a comment |

Dagger may also be the cause. ~~Changing dagger version from 2.17 back to 2.16 can fix this problem for now.~~

Discussion: https://github.com/google/dagger/issues/1245

~~Update~~

~~Dagger 2.18 is out but unfortunately it still won't work after I tested(Have I missed something?).~~

~~Update2~~

~~Dagger 2.19 also won't work and the discussion is locked.~~

~~But in the google issuetracke, there're solutions/workarounds. I tested and they worked. Check it if you want to use the latest Dagger.~~

Update3

Dagger problem has been fixed in the Android Studio 3.3.

edited Jan 15 at 3:16

answered Sep 25 '18 at 13:41

Dewey Reed

1,2321616

I am also pretty sure that it is caused by Dagger2 in my/our case. The official documentation of DataBindingComponent even mentions dagger: "If using Dagger 2, the developer should extend this interface and annotate the extended interface as a Component." (source: developer.android.com/reference/android/databinding/…). But I don't understand exactly what to do here and if it will fix the error.

– muetzenflo
Oct 21 '18 at 20:55

@muetzenflo Your info seems promising. I'll try to extend that component and see if it can fix the error.

– Dewey Reed
Oct 22 '18 at 9:30

@muetzenflo I've tried the solution but it didn't work. I guess it only takes effects when the app is running but the problem happens in the compile time.

– Dewey Reed
Oct 24 '18 at 4:31

2.19 is out and the issue is still there

– Ernest Zamelczyk
Nov 8 '18 at 9:27

@ErnestZamelczyk You're right. But I found some workaround in the issuetracker. Check the updated answer if you're interested.

– Dewey Reed
Nov 8 '18 at 10:07

add a comment |

Dagger may also be the cause. ~~Changing dagger version from 2.17 back to 2.16 can fix this problem for now.~~

Discussion: https://github.com/google/dagger/issues/1245

~~Update~~

~~Dagger 2.18 is out but unfortunately it still won't work after I tested(Have I missed something?).~~

~~Update2~~

~~Dagger 2.19 also won't work and the discussion is locked.~~

~~But in the google issuetracke, there're solutions/workarounds. I tested and they worked. Check it if you want to use the latest Dagger.~~

Update3

Dagger problem has been fixed in the Android Studio 3.3.

edited Jan 15 at 3:16

answered Sep 25 '18 at 13:41

Dewey Reed

1,2321616

Dagger may also be the cause. ~~Changing dagger version from 2.17 back to 2.16 can fix this problem for now.~~

Discussion: https://github.com/google/dagger/issues/1245

~~Update~~

~~Dagger 2.18 is out but unfortunately it still won't work after I tested(Have I missed something?).~~

~~Update2~~

~~Dagger 2.19 also won't work and the discussion is locked.~~

~~But in the google issuetracke, there're solutions/workarounds. I tested and they worked. Check it if you want to use the latest Dagger.~~

Update3

Dagger problem has been fixed in the Android Studio 3.3.

edited Jan 15 at 3:16

answered Sep 25 '18 at 13:41

Dewey Reed

1,2321616

edited Jan 15 at 3:16

answered Sep 25 '18 at 13:41

Dewey Reed

1,2321616

answered Sep 25 '18 at 13:41

Dewey Reed

1,2321616

answered Sep 25 '18 at 13:41

Dewey Reed

1,2321616

I am also pretty sure that it is caused by Dagger2 in my/our case. The official documentation of DataBindingComponent even mentions dagger: "If using Dagger 2, the developer should extend this interface and annotate the extended interface as a Component." (source: developer.android.com/reference/android/databinding/…). But I don't understand exactly what to do here and if it will fix the error.

– muetzenflo
Oct 21 '18 at 20:55

@muetzenflo Your info seems promising. I'll try to extend that component and see if it can fix the error.

– Dewey Reed
Oct 22 '18 at 9:30

@muetzenflo I've tried the solution but it didn't work. I guess it only takes effects when the app is running but the problem happens in the compile time.

– Dewey Reed
Oct 24 '18 at 4:31

2.19 is out and the issue is still there

– Ernest Zamelczyk
Nov 8 '18 at 9:27

@ErnestZamelczyk You're right. But I found some workaround in the issuetracker. Check the updated answer if you're interested.

– Dewey Reed
Nov 8 '18 at 10:07

add a comment |

I am also pretty sure that it is caused by Dagger2 in my/our case. The official documentation of DataBindingComponent even mentions dagger: "If using Dagger 2, the developer should extend this interface and annotate the extended interface as a Component." (source: developer.android.com/reference/android/databinding/…). But I don't understand exactly what to do here and if it will fix the error.

– muetzenflo
Oct 21 '18 at 20:55

@muetzenflo Your info seems promising. I'll try to extend that component and see if it can fix the error.

– Dewey Reed
Oct 22 '18 at 9:30

@muetzenflo I've tried the solution but it didn't work. I guess it only takes effects when the app is running but the problem happens in the compile time.

– Dewey Reed
Oct 24 '18 at 4:31

2.19 is out and the issue is still there

– Ernest Zamelczyk
Nov 8 '18 at 9:27

@ErnestZamelczyk You're right. But I found some workaround in the issuetracker. Check the updated answer if you're interested.

– Dewey Reed
Nov 8 '18 at 10:07

I am also pretty sure that it is caused by Dagger2 in my/our case. The official documentation of DataBindingComponent even mentions dagger: "If using Dagger 2, the developer should extend this interface and annotate the extended interface as a Component." (source: developer.android.com/reference/android/databinding/…). But I don't understand exactly what to do here and if it will fix the error.

– muetzenflo
Oct 21 '18 at 20:55

@muetzenflo Your info seems promising. I'll try to extend that component and see if it can fix the error.

– Dewey Reed
Oct 22 '18 at 9:30

@muetzenflo I've tried the solution but it didn't work. I guess it only takes effects when the app is running but the problem happens in the compile time.

– Dewey Reed
Oct 24 '18 at 4:31

2.19 is out and the issue is still there

– Ernest Zamelczyk
Nov 8 '18 at 9:27

@ErnestZamelczyk You're right. But I found some workaround in the issuetracker. Check the updated answer if you're interested.

– Dewey Reed
Nov 8 '18 at 10:07

add a comment |

i finally fixed my problem because i was using Android Annotations and they released a new Version 4.5.1 1 Hour ago, where they support Grade Plugin 3.2.0.

I was searching for this bug for a week and i´m happy now. Hope this helps you, too!

answered Oct 15 '18 at 10:29

Sandra

312

You've just saved me a lot of time. AndroidAnnotations sucks!!!!

– Krzysztof Kubicki
Dec 11 '18 at 9:32

add a comment |

i finally fixed my problem because i was using Android Annotations and they released a new Version 4.5.1 1 Hour ago, where they support Grade Plugin 3.2.0.

I was searching for this bug for a week and i´m happy now. Hope this helps you, too!

answered Oct 15 '18 at 10:29

Sandra

312

You've just saved me a lot of time. AndroidAnnotations sucks!!!!

– Krzysztof Kubicki
Dec 11 '18 at 9:32

add a comment |

i finally fixed my problem because i was using Android Annotations and they released a new Version 4.5.1 1 Hour ago, where they support Grade Plugin 3.2.0.

I was searching for this bug for a week and i´m happy now. Hope this helps you, too!

answered Oct 15 '18 at 10:29

Sandra

312

i finally fixed my problem because i was using Android Annotations and they released a new Version 4.5.1 1 Hour ago, where they support Grade Plugin 3.2.0.

I was searching for this bug for a week and i´m happy now. Hope this helps you, too!

answered Oct 15 '18 at 10:29

Sandra

312

answered Oct 15 '18 at 10:29

Sandra

312

answered Oct 15 '18 at 10:29

Sandra

312

answered Oct 15 '18 at 10:29

Sandra

312

You've just saved me a lot of time. AndroidAnnotations sucks!!!!

– Krzysztof Kubicki
Dec 11 '18 at 9:32

add a comment |

You've just saved me a lot of time. AndroidAnnotations sucks!!!!

– Krzysztof Kubicki
Dec 11 '18 at 9:32

You've just saved me a lot of time. AndroidAnnotations sucks!!!!

– Krzysztof Kubicki
Dec 11 '18 at 9:32

add a comment |

I have tried classpath 'com.android.tools.build:gradle:3.2.0-beta05'
with and without explicit dependency kapt "androidx.databinding:databinding-compiler:3.3.0-alpha06"

And still getting the same exception.

I have also tried 3.3.0-alpha06 but nothing changed.

edited Aug 27 '18 at 16:28

answered Aug 16 '18 at 18:54

Stanislaw Baranski

30929

add a comment |

I have tried classpath 'com.android.tools.build:gradle:3.2.0-beta05'
with and without explicit dependency kapt "androidx.databinding:databinding-compiler:3.3.0-alpha06"

And still getting the same exception.

I have also tried 3.3.0-alpha06 but nothing changed.

edited Aug 27 '18 at 16:28

answered Aug 16 '18 at 18:54

Stanislaw Baranski

30929

add a comment |

I have tried classpath 'com.android.tools.build:gradle:3.2.0-beta05'
with and without explicit dependency kapt "androidx.databinding:databinding-compiler:3.3.0-alpha06"

And still getting the same exception.

I have also tried 3.3.0-alpha06 but nothing changed.

edited Aug 27 '18 at 16:28

answered Aug 16 '18 at 18:54

Stanislaw Baranski

30929

I have tried classpath 'com.android.tools.build:gradle:3.2.0-beta05'
with and without explicit dependency kapt "androidx.databinding:databinding-compiler:3.3.0-alpha06"

And still getting the same exception.

I have also tried 3.3.0-alpha06 but nothing changed.

edited Aug 27 '18 at 16:28

answered Aug 16 '18 at 18:54

Stanislaw Baranski

30929

edited Aug 27 '18 at 16:28

answered Aug 16 '18 at 18:54

Stanislaw Baranski

30929

answered Aug 16 '18 at 18:54

Stanislaw Baranski

30929

answered Aug 16 '18 at 18:54

Stanislaw Baranski

30929

add a comment |

I fix it updating Android Studio to Canary 16 AND this in gradle.wrapper.properties distributionUrl=https://services.gradle.org/distributions/gradle-4.7-all.zip

answered May 30 '18 at 1:29

Eduardo Dornel

194

2

I'm already using Canary 16 and Gradle 4.7, but it is not working.

– Juliano Nunes Silva Oliveira
May 30 '18 at 9:03

I'm using Android studio 3.3 Canary 11 and Gradle 4.10, and I am getting the error, so this solution dosen't do for me

– L-X
Sep 25 '18 at 10:03

add a comment |

I fix it updating Android Studio to Canary 16 AND this in gradle.wrapper.properties distributionUrl=https://services.gradle.org/distributions/gradle-4.7-all.zip

answered May 30 '18 at 1:29

Eduardo Dornel

194

2

I'm already using Canary 16 and Gradle 4.7, but it is not working.

– Juliano Nunes Silva Oliveira
May 30 '18 at 9:03

I'm using Android studio 3.3 Canary 11 and Gradle 4.10, and I am getting the error, so this solution dosen't do for me

– L-X
Sep 25 '18 at 10:03

add a comment |

I fix it updating Android Studio to Canary 16 AND this in gradle.wrapper.properties distributionUrl=https://services.gradle.org/distributions/gradle-4.7-all.zip

answered May 30 '18 at 1:29

Eduardo Dornel

194

I fix it updating Android Studio to Canary 16 AND this in gradle.wrapper.properties distributionUrl=https://services.gradle.org/distributions/gradle-4.7-all.zip

answered May 30 '18 at 1:29

Eduardo Dornel

194

answered May 30 '18 at 1:29

Eduardo Dornel

194

answered May 30 '18 at 1:29

Eduardo Dornel

194

answered May 30 '18 at 1:29

Eduardo Dornel

194

2

I'm already using Canary 16 and Gradle 4.7, but it is not working.

– Juliano Nunes Silva Oliveira
May 30 '18 at 9:03

I'm using Android studio 3.3 Canary 11 and Gradle 4.10, and I am getting the error, so this solution dosen't do for me

– L-X
Sep 25 '18 at 10:03

add a comment |

2

I'm already using Canary 16 and Gradle 4.7, but it is not working.

– Juliano Nunes Silva Oliveira
May 30 '18 at 9:03

I'm using Android studio 3.3 Canary 11 and Gradle 4.10, and I am getting the error, so this solution dosen't do for me

– L-X
Sep 25 '18 at 10:03

I'm already using Canary 16 and Gradle 4.7, but it is not working.

– Juliano Nunes Silva Oliveira
May 30 '18 at 9:03

I'm using Android studio 3.3 Canary 11 and Gradle 4.10, and I am getting the error, so this solution dosen't do for me

– L-X
Sep 25 '18 at 10:03

add a comment |

I solved the error by adding

android.useAndroidX=true

android.enableJetifier=true

in my project's gradle.properties file

answered Aug 29 '18 at 12:39

Edijae Crusar

1,4111652

Didn't work for me. What does the above do? Where did you find it?

– Amir Uval
Sep 17 '18 at 13:46

1

@auval android.useAndroidX: When set to true, this flag indicates that you want to start using AndroidX from now on. If the flag is absent, Android Studio behaves as if the flag were set to false. android.enableJetifier: When set to true, this flag indicates that you want to have tool support (from the Android Gradle plugin) to automatically convert existing third-party libraries as if they were written for AndroidX. If the flag is absent, Android Studio behaves as if the flag were set to false.

– Edijae Crusar
Sep 17 '18 at 14:25

Didn't work for me, I am using Android studio 3.3 these parameters are already present

– L-X
Sep 25 '18 at 10:04

This is definitely required if you migrate to Android X and use databinding etc. I migrated on one machine but the error appeared on a different one because gradle.properties is not in source control

– Daniel Wilson
Nov 26 '18 at 14:04

add a comment |

I solved the error by adding

android.useAndroidX=true

android.enableJetifier=true

in my project's gradle.properties file

answered Aug 29 '18 at 12:39

Edijae Crusar

1,4111652

Didn't work for me. What does the above do? Where did you find it?

– Amir Uval
Sep 17 '18 at 13:46

1

@auval android.useAndroidX: When set to true, this flag indicates that you want to start using AndroidX from now on. If the flag is absent, Android Studio behaves as if the flag were set to false. android.enableJetifier: When set to true, this flag indicates that you want to have tool support (from the Android Gradle plugin) to automatically convert existing third-party libraries as if they were written for AndroidX. If the flag is absent, Android Studio behaves as if the flag were set to false.

– Edijae Crusar
Sep 17 '18 at 14:25

Didn't work for me, I am using Android studio 3.3 these parameters are already present

– L-X
Sep 25 '18 at 10:04

This is definitely required if you migrate to Android X and use databinding etc. I migrated on one machine but the error appeared on a different one because gradle.properties is not in source control

– Daniel Wilson
Nov 26 '18 at 14:04

add a comment |

I solved the error by adding

android.useAndroidX=true

android.enableJetifier=true

in my project's gradle.properties file

answered Aug 29 '18 at 12:39

Edijae Crusar

1,4111652

I solved the error by adding

android.useAndroidX=true

android.enableJetifier=true

in my project's gradle.properties file

answered Aug 29 '18 at 12:39

Edijae Crusar

1,4111652

answered Aug 29 '18 at 12:39

Edijae Crusar

1,4111652

answered Aug 29 '18 at 12:39

Edijae Crusar

1,4111652

answered Aug 29 '18 at 12:39

Edijae Crusar

1,4111652

Didn't work for me. What does the above do? Where did you find it?

– Amir Uval
Sep 17 '18 at 13:46

1

@auval android.useAndroidX: When set to true, this flag indicates that you want to start using AndroidX from now on. If the flag is absent, Android Studio behaves as if the flag were set to false. android.enableJetifier: When set to true, this flag indicates that you want to have tool support (from the Android Gradle plugin) to automatically convert existing third-party libraries as if they were written for AndroidX. If the flag is absent, Android Studio behaves as if the flag were set to false.

– Edijae Crusar
Sep 17 '18 at 14:25

Didn't work for me, I am using Android studio 3.3 these parameters are already present

– L-X
Sep 25 '18 at 10:04

This is definitely required if you migrate to Android X and use databinding etc. I migrated on one machine but the error appeared on a different one because gradle.properties is not in source control

– Daniel Wilson
Nov 26 '18 at 14:04

add a comment |

Didn't work for me. What does the above do? Where did you find it?

– Amir Uval
Sep 17 '18 at 13:46

1

@auval android.useAndroidX: When set to true, this flag indicates that you want to start using AndroidX from now on. If the flag is absent, Android Studio behaves as if the flag were set to false. android.enableJetifier: When set to true, this flag indicates that you want to have tool support (from the Android Gradle plugin) to automatically convert existing third-party libraries as if they were written for AndroidX. If the flag is absent, Android Studio behaves as if the flag were set to false.

– Edijae Crusar
Sep 17 '18 at 14:25

Didn't work for me, I am using Android studio 3.3 these parameters are already present

– L-X
Sep 25 '18 at 10:04

This is definitely required if you migrate to Android X and use databinding etc. I migrated on one machine but the error appeared on a different one because gradle.properties is not in source control

– Daniel Wilson
Nov 26 '18 at 14:04

Didn't work for me. What does the above do? Where did you find it?

– Amir Uval
Sep 17 '18 at 13:46

@auval android.useAndroidX: When set to true, this flag indicates that you want to start using AndroidX from now on. If the flag is absent, Android Studio behaves as if the flag were set to false. android.enableJetifier: When set to true, this flag indicates that you want to have tool support (from the Android Gradle plugin) to automatically convert existing third-party libraries as if they were written for AndroidX. If the flag is absent, Android Studio behaves as if the flag were set to false.

– Edijae Crusar
Sep 17 '18 at 14:25

Didn't work for me, I am using Android studio 3.3 these parameters are already present

– L-X
Sep 25 '18 at 10:04

This is definitely required if you migrate to Android X and use databinding etc. I migrated on one machine but the error appeared on a different one because gradle.properties is not in source control

– Daniel Wilson
Nov 26 '18 at 14:04

add a comment |

In my case the issue was resolved by changing:

androidExtensions.experimental = true

(i.e. gradle DSL as a one-liner)

androidExtensions {

    experimental = true

}

Android Studio 3.3; gradle-4.10.1-all; tools.build:gradle 3.3.0

answered Jan 23 at 16:19

kosiara - Bartosz Kosarzycki

3,09413039

add a comment |

In my case the issue was resolved by changing:

androidExtensions.experimental = true

(i.e. gradle DSL as a one-liner)

androidExtensions {

    experimental = true

}

Android Studio 3.3; gradle-4.10.1-all; tools.build:gradle 3.3.0

answered Jan 23 at 16:19

kosiara - Bartosz Kosarzycki

3,09413039

add a comment |

In my case the issue was resolved by changing:

androidExtensions.experimental = true

(i.e. gradle DSL as a one-liner)

androidExtensions {

    experimental = true

}

Android Studio 3.3; gradle-4.10.1-all; tools.build:gradle 3.3.0

answered Jan 23 at 16:19

kosiara - Bartosz Kosarzycki

3,09413039

In my case the issue was resolved by changing:

androidExtensions.experimental = true

(i.e. gradle DSL as a one-liner)

androidExtensions {

    experimental = true

}

Android Studio 3.3; gradle-4.10.1-all; tools.build:gradle 3.3.0

answered Jan 23 at 16:19

kosiara - Bartosz Kosarzycki

3,09413039

answered Jan 23 at 16:19

kosiara - Bartosz Kosarzycki

3,09413039

answered Jan 23 at 16:19

kosiara - Bartosz Kosarzycki

3,09413039

answered Jan 23 at 16:19

kosiara - Bartosz Kosarzycki

3,09413039

add a comment |

Just remove kapt "com.android.databinding..." dependency. If you are using Android Studio 3.2 or greater version.

answered Mar 14 at 7:07

Naimish Vinchhi

1769

add a comment |

Just remove kapt "com.android.databinding..." dependency. If you are using Android Studio 3.2 or greater version.

answered Mar 14 at 7:07

Naimish Vinchhi

1769

add a comment |

Just remove kapt "com.android.databinding..." dependency. If you are using Android Studio 3.2 or greater version.

answered Mar 14 at 7:07

Naimish Vinchhi

1769

Just remove kapt "com.android.databinding..." dependency. If you are using Android Studio 3.2 or greater version.

answered Mar 14 at 7:07

Naimish Vinchhi

1769

answered Mar 14 at 7:07

Naimish Vinchhi

1769

answered Mar 14 at 7:07

Naimish Vinchhi

1769

answered Mar 14 at 7:07

Naimish Vinchhi

1769

add a comment |

org.gradle.jvmargs=-Xmx4536m

android.databinding.enableV2=true

answered Sep 18 '18 at 18:04

Daniel Wilson

8,63285376

Tried it, still getting the same error

– L-X
Sep 25 '18 at 10:04

add a comment |

org.gradle.jvmargs=-Xmx4536m

android.databinding.enableV2=true

answered Sep 18 '18 at 18:04

Daniel Wilson

8,63285376

Tried it, still getting the same error

– L-X
Sep 25 '18 at 10:04

add a comment |

org.gradle.jvmargs=-Xmx4536m

android.databinding.enableV2=true

answered Sep 18 '18 at 18:04

Daniel Wilson

8,63285376

org.gradle.jvmargs=-Xmx4536m

android.databinding.enableV2=true

answered Sep 18 '18 at 18:04

Daniel Wilson

8,63285376

answered Sep 18 '18 at 18:04

Daniel Wilson

8,63285376

answered Sep 18 '18 at 18:04

Daniel Wilson

8,63285376

answered Sep 18 '18 at 18:04

Daniel Wilson

8,63285376

Tried it, still getting the same error

– L-X
Sep 25 '18 at 10:04

add a comment |

Tried it, still getting the same error

– L-X
Sep 25 '18 at 10:04

Tried it, still getting the same error

– L-X
Sep 25 '18 at 10:04

add a comment |

My situation:

Android Studio v3.2.1

com.android.tools.build:gradle:3.2.1

https://services.gradle.org/distributions/gradle-4.10.2-all.zip

I found that by removing databinding from my layout, recompiling the app and then adding the databinding back in it fixed this issue.

I changed the DataBindingUtil.setContentView(...) to just setContentView(...) and reduced my activity layout to the bare minimum:

<FrameLayout xmlns:android="http://schemas.android.com/apk/res/android"

    android:layout_width="match_parent"

    android:layout_height="match_parent">



    <TextView

        android:layout_width="wrap_content"

        android:layout_height="wrap_content"

        android:text="hello"/>



</FrameLayout>

Then add the databinding back in piece by piece.

answered Oct 29 '18 at 23:55

Taskmaster

686510

add a comment |

My situation:

Android Studio v3.2.1

com.android.tools.build:gradle:3.2.1

https://services.gradle.org/distributions/gradle-4.10.2-all.zip

I found that by removing databinding from my layout, recompiling the app and then adding the databinding back in it fixed this issue.

I changed the DataBindingUtil.setContentView(...) to just setContentView(...) and reduced my activity layout to the bare minimum:

<FrameLayout xmlns:android="http://schemas.android.com/apk/res/android"

    android:layout_width="match_parent"

    android:layout_height="match_parent">



    <TextView

        android:layout_width="wrap_content"

        android:layout_height="wrap_content"

        android:text="hello"/>



</FrameLayout>

Then add the databinding back in piece by piece.

answered Oct 29 '18 at 23:55

Taskmaster

686510

add a comment |

My situation:

Android Studio v3.2.1

com.android.tools.build:gradle:3.2.1

https://services.gradle.org/distributions/gradle-4.10.2-all.zip

I found that by removing databinding from my layout, recompiling the app and then adding the databinding back in it fixed this issue.

I changed the DataBindingUtil.setContentView(...) to just setContentView(...) and reduced my activity layout to the bare minimum:

<FrameLayout xmlns:android="http://schemas.android.com/apk/res/android"

    android:layout_width="match_parent"

    android:layout_height="match_parent">



    <TextView

        android:layout_width="wrap_content"

        android:layout_height="wrap_content"

        android:text="hello"/>



</FrameLayout>

Then add the databinding back in piece by piece.

answered Oct 29 '18 at 23:55

Taskmaster

686510

My situation:

Android Studio v3.2.1

com.android.tools.build:gradle:3.2.1

https://services.gradle.org/distributions/gradle-4.10.2-all.zip

I found that by removing databinding from my layout, recompiling the app and then adding the databinding back in it fixed this issue.

I changed the DataBindingUtil.setContentView(...) to just setContentView(...) and reduced my activity layout to the bare minimum:

<FrameLayout xmlns:android="http://schemas.android.com/apk/res/android"

    android:layout_width="match_parent"

    android:layout_height="match_parent">



    <TextView

        android:layout_width="wrap_content"

        android:layout_height="wrap_content"

        android:text="hello"/>



</FrameLayout>

Then add the databinding back in piece by piece.

answered Oct 29 '18 at 23:55

Taskmaster

686510

answered Oct 29 '18 at 23:55

Taskmaster

686510

answered Oct 29 '18 at 23:55

Taskmaster

686510

answered Oct 29 '18 at 23:55

Taskmaster

686510

add a comment |

In my case there was an import error in one of the files. Simply opening that file made imports to happen automatically and thereafter project got built.

It's a pity, that AS gave zero indication to this, neither did error stacktrace.

In case nothing from posted answer helps - just surf through all the files in the project and seek for a file which has incorrect import statement.

answered Oct 30 '18 at 21:23

azizbekian

37.9k687148

add a comment |

In my case there was an import error in one of the files. Simply opening that file made imports to happen automatically and thereafter project got built.

It's a pity, that AS gave zero indication to this, neither did error stacktrace.

In case nothing from posted answer helps - just surf through all the files in the project and seek for a file which has incorrect import statement.

answered Oct 30 '18 at 21:23

azizbekian

37.9k687148

add a comment |

In my case there was an import error in one of the files. Simply opening that file made imports to happen automatically and thereafter project got built.

It's a pity, that AS gave zero indication to this, neither did error stacktrace.

In case nothing from posted answer helps - just surf through all the files in the project and seek for a file which has incorrect import statement.

answered Oct 30 '18 at 21:23

azizbekian

37.9k687148

In my case there was an import error in one of the files. Simply opening that file made imports to happen automatically and thereafter project got built.

It's a pity, that AS gave zero indication to this, neither did error stacktrace.

In case nothing from posted answer helps - just surf through all the files in the project and seek for a file which has incorrect import statement.

answered Oct 30 '18 at 21:23

azizbekian

37.9k687148

answered Oct 30 '18 at 21:23

azizbekian

37.9k687148

answered Oct 30 '18 at 21:23

azizbekian

37.9k687148

answered Oct 30 '18 at 21:23

azizbekian

37.9k687148

add a comment |

It's a bug in jetifier. Here's a workaround for now until the next update. Put this in your project gradle:

buildscript {

    dependencies {

        classpath 'com.android.tools.build.jetifier:jetifier-processor:1.0.0-beta02'

    }

}

answered Nov 8 '18 at 9:31

Ernest Zamelczyk

624519

add a comment |

It's a bug in jetifier. Here's a workaround for now until the next update. Put this in your project gradle:

buildscript {

    dependencies {

        classpath 'com.android.tools.build.jetifier:jetifier-processor:1.0.0-beta02'

    }

}

answered Nov 8 '18 at 9:31

Ernest Zamelczyk

624519

add a comment |

It's a bug in jetifier. Here's a workaround for now until the next update. Put this in your project gradle:

buildscript {

    dependencies {

        classpath 'com.android.tools.build.jetifier:jetifier-processor:1.0.0-beta02'

    }

}

answered Nov 8 '18 at 9:31

Ernest Zamelczyk

624519

It's a bug in jetifier. Here's a workaround for now until the next update. Put this in your project gradle:

buildscript {

    dependencies {

        classpath 'com.android.tools.build.jetifier:jetifier-processor:1.0.0-beta02'

    }

}

answered Nov 8 '18 at 9:31

Ernest Zamelczyk

624519

answered Nov 8 '18 at 9:31

Ernest Zamelczyk

624519

answered Nov 8 '18 at 9:31

Ernest Zamelczyk

624519

answered Nov 8 '18 at 9:31

Ernest Zamelczyk

624519

add a comment |

This is my most stupid mistake!
I have actually created a private variable for Databinding and that was causing this issue.

Just use a lateinit var binding and it Worked.

This could help someone!

answered Nov 27 '18 at 9:35

Kannan_SJD

4491323

add a comment |

This is my most stupid mistake!
I have actually created a private variable for Databinding and that was causing this issue.

Just use a lateinit var binding and it Worked.

This could help someone!

answered Nov 27 '18 at 9:35

Kannan_SJD

4491323

add a comment |

This is my most stupid mistake!
I have actually created a private variable for Databinding and that was causing this issue.

Just use a lateinit var binding and it Worked.

This could help someone!

answered Nov 27 '18 at 9:35

Kannan_SJD

4491323

This is my most stupid mistake!
I have actually created a private variable for Databinding and that was causing this issue.

Just use a lateinit var binding and it Worked.

This could help someone!

answered Nov 27 '18 at 9:35

Kannan_SJD

4491323

answered Nov 27 '18 at 9:35

Kannan_SJD

4491323

answered Nov 27 '18 at 9:35

Kannan_SJD

4491323

answered Nov 27 '18 at 9:35

Kannan_SJD

4491323

add a comment |

My issue was that I tried to enable data binding for my Login module but not the App module. After adding:

dataBinding {

    enabled = true

}

to the App module and removed it from the Login module, it worked.

answered Jan 2 at 23:43

Aleksander Aleksic

456613

add a comment |

My issue was that I tried to enable data binding for my Login module but not the App module. After adding:

dataBinding {

    enabled = true

}

to the App module and removed it from the Login module, it worked.

answered Jan 2 at 23:43

Aleksander Aleksic

456613

add a comment |

My issue was that I tried to enable data binding for my Login module but not the App module. After adding:

dataBinding {

    enabled = true

}

to the App module and removed it from the Login module, it worked.

answered Jan 2 at 23:43

Aleksander Aleksic

456613

My issue was that I tried to enable data binding for my Login module but not the App module. After adding:

dataBinding {

    enabled = true

}

to the App module and removed it from the Login module, it worked.

answered Jan 2 at 23:43

Aleksander Aleksic

456613

answered Jan 2 at 23:43

Aleksander Aleksic

456613

answered Jan 2 at 23:43

Aleksander Aleksic

456613

answered Jan 2 at 23:43

Aleksander Aleksic

456613

add a comment |

If you are using dataroom library, check @Dao annotation in your DAO classes.
In my case, I forgot to add @Dao to my interface of RoomDatabase'Dao.

answered Mar 19 at 14:07

bdpqchen

add a comment |

If you are using dataroom library, check @Dao annotation in your DAO classes.
In my case, I forgot to add @Dao to my interface of RoomDatabase'Dao.

answered Mar 19 at 14:07

bdpqchen

add a comment |

If you are using dataroom library, check @Dao annotation in your DAO classes.
In my case, I forgot to add @Dao to my interface of RoomDatabase'Dao.

answered Mar 19 at 14:07

bdpqchen

If you are using dataroom library, check @Dao annotation in your DAO classes.
In my case, I forgot to add @Dao to my interface of RoomDatabase'Dao.

answered Mar 19 at 14:07

bdpqchen

answered Mar 19 at 14:07

bdpqchen

answered Mar 19 at 14:07

bdpqchen

answered Mar 19 at 14:07

bdpqchen

add a comment |

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

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

Search This Blog

Ufyukyu