I downloaded an Android project, but I am getting this error:
Error:(42, 42) error: cannot find symbol class DataBindingComponent
Sample Import:
import android.databinding.DataBindingComponent; // no code-time error
import android.databinding.DataBindingUtil;
import android.databinding.ViewDataBinding;
Sample Usage:
public FragmentFantasyPointsSingleBinding(DataBindingComponent bindingComponent, View root) {
super(bindingComponent, root, 0);
Object[] bindings = ViewDataBinding.mapBindings(bindingComponent, root, 4, sIncludes, sViewsWithIds);
this.animationView = (LottieAnimationView) bindings[3];
this.mboundView0 = (FrameLayout) bindings[0];
this.mboundView0.setTag(null);
this.progressView = (LinearLayout) bindings[2];
this.recyclerView = (RecyclerView) bindings[1];
setRootTag(root);
invalidateAll();
}
There is no error on code-time, but on compile-time I get the error that I mentioned.
When I try to go to definition on Android Studio, I can't.
App level build.gradle:
apply plugin: 'com.android.application'
android {
compileSdkVersion 26
defaultConfig {
applicationId "com.esports.flank"
minSdkVersion 19
targetSdkVersion 26
versionCode 1
versionName "1.0"
testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
vectorDrawables.useSupportLibrary = true
}
buildTypes {
release {
minifyEnabled false
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
}
}
dataBinding {
enabled = true
}
}
dependencies {
implementation fileTree(dir: 'libs', include: ['*.jar'])
implementation 'com.android.support:appcompat-v7:26.1.0'
implementation 'com.android.support.constraint:constraint-layout:1.1.2'
testImplementation 'junit:junit:4.12'
androidTestImplementation 'com.android.support.test:runner:1.0.2'
androidTestImplementation 'com.android.support.test.espresso:espresso-core:3.0.2'
compile 'com.android.support:support-annotations:26.1.0'
compile "com.android.support:appcompat-v7:26.1.0"
compile "com.android.support:recyclerview-v7:26.1.0"
implementation 'com.android.support:cardview-v7:26.1.0'
implementation 'com.github.bumptech.glide:glide:4.7.1'
annotationProcessor 'com.github.bumptech.glide:compiler:4.7.1'
implementation 'de.hdodenhof:circleimageview:2.2.0'
compile('com.twitter.sdk.android:twitter:3.3.0@aar') {
transitive = true
}
compile 'com.microsoft.azure:azure-mobile-android:3.4.0@aar'
implementation 'com.airbnb.android:lottie:2.5.5'
compile 'com.github.ybq:Android-SpinKit:1.1.0'
compile 'uk.co.chrisjenx:calligraphy:2.3.0'
compile 'com.romandanylyk:pageindicatorview:1.0.1@aar'
api 'com.google.guava:guava:26.0-android'
compile 'com.android.support:design:26.1.0'
implementation 'com.wajahatkarim3.EasyFlipView:EasyFlipView:2.1.0'
}
I tried cleaning and rebuilding project, no luck yet.
Thanks for help.
Build errors for generated interfaces like DataBindingComponent are usually misleading. Try to look for any other build errors and fix those first, then recompile. Even though its weird issue, Just try to remove to un necessary imports, it should work.
The cannot find symbol error, also found under the names of symbol not found and cannot resolve symbol, is a Java compile-time error which emerges whenever there is an identifier in the source code which the compiler is unable to work out what it refers to.
If you are getting cryptic errors like error: cannot find symbol import, the following methods may help you figure out what is wrong. 1. View All of the Build Output Android Studio has two different ways to view the build output. The default tree view tries to condense the build output into an easy-to-view hierarchy.
Three Methods for Solving Android Data Binding Errors 1 View All of the Build Output#N#Android Studio has two different ways to view the build output. The default tree view... 2 Fall Back to the Old Data Binding Compiler Temporarily#N#Starting in version 3.2.1 of Android Studio, the second... 3 Invalidate Caches More ...
This answer helped me in a similar case: https://stackoverflow.com/a/52550118/8655667
android.enableExperimentalFeatureDatabinding=true
and android.databinding.enableV2=false
to gradle.properties
After rebuild it should give you the actual compilation failure reason.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With