I am using Data Binding in my project, when using <layout> and <data> in my xml binding class is not generated.
For example i have activity_main.xml
<?xml version="1.0" encoding="utf-8"?>
<layout xmlns:android="http://schemas.android.com/apk/res/android">
<data> </data>
<RelativeLayout
android:layout_width="match_parent"
android:layout_height="match_parent">
</RelativeLayout>
</layout>
Now if i am writing ActivityMainBinding in my activity/fragment it shows error that class is not available. But after including <variable> in my xml file, it is able to generate ActivityMainBinding class.
Android Studio : 2.1.3
Classpath : com.android.tools.build:gradle:2.1.3
minSdkVersion 16
targetSdkVersion 24
buildToolsVersion 24.0.0
I did not get any satisfying answers. So here are the tips which are summary of my data binding knowledge.
Tips For Solving DataBinding Issues
Update
To get more accurate errors and suggestions, I strongly recommend to update Android Studio and Gradle plugin version to the latest. Because I am not facing many issues after AS 3.2 version.
See Latest Android Studio, and Latest Gradle Plugin.
Orignal Solution
After reading this answer, you will not get stuck in data binding auto generation issues for both Classes and Data Variables.
Check these points one by one. Any of these can make your work done. Point 3 to last are really important, so don't miss them.
1. Check if data-binding enabled
You should have data binding enabled in build.gradle. If not then add this and Sync.
android {
...
buildFeatures {
dataBinding true
}
}
2. Check layout is converted in binding layout
Now if you want data binding class to be generated then you should wrap xml layout with data binding (<layout tag). Something like this.
<?xml version="1.0" encoding="utf-8"?>
<layout xmlns:android="http://schemas.android.com/apk/res/android">
<android.support.constraint.ConstraintLayout
android:layout_width="match_parent"
android:layout_height="match_parent">
</android.support.constraint.ConstraintLayout>
</layout>
Along with this check whether the binding variable names are correct as in the view model class
3. Auto-generated Binding class name?
Your data binding class should be generated after creating binding layout.
If your layout name is in snake case activity_main.xml then data binding class
will be generated in camel case like ActivityMainBinding.
4. Can't See Import Suggestion?
Sometimes when you type ActivityMai..., then it does not show suggestion, in that case import manually.
import <yourpackage>databinding.ActivityMainBinding;
5. Read Build Fail Logcat
Your binding class and new variables in layout will not be generated if your build fails. So first Make project by Ctrl + F9 (Build > Make project).
If a build fails then see what is an error, usually we have errors in layout fields. Error logs will point out the error line number with the issue.
Binding may fail cause some stupid error, like syntax error or missing import. In that case, you will get logcat full of errors of binding classes. But you should read complete logcat to find appropriate issue.
6. Close and open project from recent
I always do this because it takes much less time than Rebuild / Make project.
Close project from File > Close Project
Open again from recent
Note that I prefer Close and Open from Recent because it takes much less time than Rebuild / Restart IDE.
7. Rebuild Project
If still your class is not generated. (Some time when we paste layout file, then it happens). Then Rebuild Project from Build> Rebuild (Not Build or Make project). It will generate your data binding class. (Rebuild does Magic for me.)
8. Have latest Android Studio
After updating AS to Android Studio 3.2, I felt many bugs fix in data binding auto generation. So you should also have the latest AS.
#Solution for <variables
<data>
<variable
name="item"
type="com.package.Model"/>
</data>
Usually, when we put a variable in layout, it creates a getter and setter of it. And we can use binding.setItem(item); and binding.getItem();, but if you can't see those methods then read the below information.
1. Close and open project from recent
If you have created a data variable - <variable in your layout and it does not show up its setter and getter in data binding class, then Close and Open from Recent your project.
2. Clean project after changing the type
If you changed the type of some <variable in your layout and getter setter type is not changing then Clean project (Build> Clean Project)
Final words
Finally if still your binding class is not generated, then we have our most powerful weapon. - Restart Android Studio
First, try just restart, this always generates variables of my binding layout after restart.
If it does not work then Invalidate Cache & Restart.
This is all that i do to solve my data binding errors. If you get any further issues, you can comment here.
DataBinding class generated automatically.
if your xml name is activity_test then the Binding class will be ActivityTestBinding.
but,
dataBinding {
enabled = true
}
layout should have layout as root
<layout xmlns:android="http://schemas.android.com/apk/res/android">
</layout>
I had the same issue. After reading over the android sdk docs, there is only the expected file name to be created but nothing about what to do if it does not happen. I noticed after some more research that after removing the namespace to the layout element like below (using your example), it worked for me.
<?xml version="1.0" encoding="utf-8"?>
<layout>
<data> </data>
<RelativeLayout
xmlns:android="http://schemas.android.com/apk/res/android"
android:layout_width="match_parent"
android:layout_height="match_parent">
</RelativeLayout>
</layout>
In my case, the Binding class was generated and in place ( but I thought it wasn't) ... but it does not automatically add import of said class to the activity/fragment import section... so... OPTION + ENTER :)
dataBinding {
enabled = true
}
To enable the new data binding compiler, add the following option to your gradle.properties file:
android.databinding.enableV2=true
Update:
To enable databinding please use,
android {
...
buildFeatures {
dataBinding true
}
}
Please follow this link:
https://developer.android.com/jetpack/androidx/releases/databinding
if you do base job, for enable databainding in your project, like use enable in gradle and use layout tag in xml, when you change xml code and did not generat new databinding class for those xml you can use a fast way for generation only data binding class in gradle->other->databindinggenbaseclassesDebug it fast more than bulid whole project. its generate only databinding class.
After having set up it properly (including xml namespace and wrapping everything into <layout>), the one which worked for me was doing Build -> Make project. Nor Clean Project or Rebuild Project did. I'm in Android Studio 2.3.1, using 26.0.2 build tools. There's no need for <data> tags.
My solution was to take as a suffix FragmentBinding in the class name.
A binding class is generated for each layout file. By default, the name of the class is based on the name of the layout file, converting it to Pascal case and adding the Binding suffix to it. The above layout filename is activity_main.xml so the corresponding generated class is ActivityMainBinding. This class holds all the bindings from the layout properties (for example, the user variable) to the layout's views and knows how to assign values for the binding expressions.
The nomenclature of the name of the activity or fragment class may vary in terms of prefixes. Because the suffix is always Binding.
After following the response of Khemraj and Invalidate Caches / Restart, you should rewrite ActivityBinding or FragmentBinding to get the IDE suggestions of the classes that were already generated and DO NOT hardcode the import.
In my case I was trying to import the name of the class backwards be FragmentCompetitionsBinding instead of CompetitionsFragmentBinding.
GL
Source
I had the same problem. I made a mistake while I refactored.
The autogen binding class has its name from the xml layout file.
fragment_name.xml -> FragmentNameBinding
Most of time it just need to rebuild. not build not make project . and it will be better if you first of all do invalid Caches and restart Android studio then clean and rebuild it .
Data binding classes are generated during the build so after you enable data binding in the Gradle build of the app and surround your xml with the layout tag you should rebuild your app. If that doesn't help, delete your build folder and do it again.
I do not know it will work for you or not. Just rename the layout XML file name. Like suppose your layout name is activity_main.xml just change rename it to anything like main.xml and again rename it to activity_main.xml. Then you can able to see the import option on ActivityMainBinding.
Hope it works for you.
Thanks to this answer here - it looks like the "layout namespace" needs to either be cleared out, or you need a new unique name.
Here are the options that worked for me:
Create a fresh name for the layout to make sure it can be generated. This solved my issue, where I had a layout that was first created, without data binding - let's call it fragment_abc.xml. When I tried to add data binding to it, it was not recognized - even after multiple clear cache & restart calls. However, soon as I made a copy of the layout fragment_abc2.xml, immediately I got the generated data-binding .java/.class object.
After seeing the above work, I tried to just remove the /build folder from the module, and rebuilt the project - this worked to get data binding for the original layout.
When you work with a multimodule Android application check your binding class path. Maybe you should use:
import com.yourcompany.app.android.modulename.databinding.FragmentABCtBinding
insted of:
import com.yourcompany.app.android.databinding.FragmentABCtBinding
In my case, I thought that generated class had to appear with my usual classes in src folder. In addition, I thought that the name of the generated class should be slightly different. It all was my mistake. The generated class can be found in build folder, build -> generated -> ... path. If there is no import of the generated class in your activity, add the import
import com.yourcompany.app.databinding.ActivityMainBinding;"
Delete layouts and undo, and make sure the generated binding classes are imported correctly after that.
Make sure data binding enabled
android {
...
dataBinding {
enabled = true
}
...
}
dan click the button (Sync project with Gradle)
If answer did not work for you, then my recommendation is simple but effective.
The idea is to determine which is the component that is generating the problem. To do this, comment on all the lines of your custom_fragment.xml and its uses in the CustomFragment.kt and leave something minimalist like the following.
<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">
<androidx.constraintlayout.widget.ConstraintLayout
android:id="#+id/test"
android:layout_width="match_parent"
android:layout_height="match_parent"/>
</layout>
Then run the app and add component to component while you Apply Code Changes (Ctrl+Alt+F10) to the execution of the app until the app crashes, that is when you found the fault.
Data binding logs are sometimes not so descriptive and this is a generic strategy to find the faulty component.
GL
The only thing I can imagine if possible is if you don't have
dataBinding {
enabled true
}
in your gradle file. If not just add it to the gradle file.
i.e
android {
......
dataBinding {
enabled true
}
}
then sync your project. If it still fail, you may need to do Invalidate/Restart of your android studio
I had same problem. Everything you done correct. Thing is you need add variable inside data tag in xml. For that you should create a sample model class and add it as variable in data tag.
Until that you won't get to see generated ActivityMainBinding.
1.Add Below in app gradle
dataBinding {
enabled = true
}
2.In xml layout write below code
<layout
xmlns:android="http://schemas.android.com/apk/res/android">
<data></data>
</layout>if you don't get data binding class just rename the layout file name and you will get data binding class.
I had a similar issue where I had the layout wrapped and my data binding enabled in the gradle file. Main activity still couldn't intellisense or see my classes. What fixed it for me was adding the binding variable and importing the binding anyway. From there I just built the solution and then it seemed to know what the class was. From there I was able to import my camel case classes that were generated.
I got the issue and the problem was in the layout the field used was not a String, it was a Date.
Looks that all field got to be text to work, at least with the TexView component.
If you build with the command
./gradlew build --stacktrace
This show better the errors.
In case you get the following error in DataBindingUtil.setContentView
Unresolved reference: activity_main
all you need to do is remove the following import statement
import android.R
I found the solution on another forum. Source
If Recently any one migrated existing project into androidx then you need to replace your import from
import com.yourpackagename.BR;
to
import androidx.databinding.library.baseAdapters.BR;
After Google 2 days finally got solution, which one work for me.
There are cases when you won't see a file under generated directory, you might be binding a property that is not declared in viewmodel. It doesn't essentially give you a lint error if you do so in xml.
If you are implement the Serializable -> you must implement the Serializable
else you will get this error. Hope it will help someone in future
In my case I use the Parcel library. I missed to annotate #Parcel in my sub class
In addition to the above steps, you can also check the variable type. Make sure it's String for TextView or the same as defined in the BindingAdapter.
For example:
data class MyDataObject(val name: String, val age: Int)
and in XML:
android:text="#{dataobject.age}"
This will cause the above error. To fix you can either make the age variable of type String or you can import String in your XML and use String.valueOf(age) as following:
<data>
<import type="String" />
...
</data>
And in your TextView:
android:text="#{String.valueOf(dataobject.age)}"
In my case, data binding classes were not generated because I had deleted the mipmap Android Resource Directory. I recreated the res/mipmap/ directory and the data binding classes were reinstated.
I encountered a similar issue where DataBinding failed to generate the BindingImpl class.
In my case was an issue from a method in the data class where the name was used wrong:
The model contained a method onSignInCliked() and in the layout I used onSigninCliked(). Notice the SignIn vs Signin.
The error message wasn't enough and I discovered the issue only when I used the build script with the stack-trace option.
Related
I have added to my build script
buildFeatures {
dataBinding true
}
But when I want to use Binding class it is not recognized.
I have tried with clean and rebuild, but it doesnt work.
I tried making new xml files and trying to create for them Binding instance but nothing worked.
Did I miss some dependency, or what is going on?
Thanks!
You are using Data Binding which binds the whole layout file with the Activities , Fragments and Adapters and it doesn't generates Automatically you have to explicitly tell the Android Studio ( I don't know who does all this stuff under the hood ) by adding this Tag in your XML File.
<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">
This will just tell Android Studio to generate the Binding File for this layout because generally we don't want to generate the Binding Files for all the layouts if we have a very large project because it increase Build time.
You can use any Layout under this Tag Like,
<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">
<androidx.constraintlayout.widget.ConstraintLayout
android:layout_width="match_parent"
android:layout_height="match_parent"
android:background="#color/backgroundColor"
tools:context=".presentation.ui.activity.FullImageViewActivity">
</androidx.constraintlayout.widget.ConstraintLayout>
</layout>
Remember layout Tag just tells the Android Studio that yes we want to generate Binding File for this layout but this will not be your Root View, Like for example,
binding.root
will refer to Contraint Layout in my case.
If you are only planning to use view references like you do by using
Kotlin synthetics (Deprecated)
findViewById (very bad for performance, especially if you are not storing the references)
ButterKnife (let's just call it old)
you can use view binding (a lite version of data binding). This way you don't have to add a layout tag and the binding will be generated for all the XML files.
Answering #VaibhavGoyal - Who does all the stuff under the hood ?
Check DataBinderMapperImpl located at app/build/generated/source which is generated by the annotation processor for each module. When you define an XML file with a layout tag, an entry is added to this mapper. When you call bind in DataBindingUtil,
static <T extends ViewDataBinding> T bind(DataBindingComponent bindingComponent, View root,
int layoutId) {
return (T) sMapper.getDataBinder(bindingComponent, root, layoutId);
}
getDataBinder called on that mapper returns the particular ViewDataBinding.
Error ScreenShot
XML Layout
I keep getting these errors when I try to implement data binding in my project, not sure what is causing it . I've checked all my xml classes and the are pointing to the appropriate viewModel. Any help would be appreciated. Thanks
According to java convention, Package names should be written in all lower case to avoid conflict with the names of classes. And it creates problem in Data Binding. So change all your package names to lower case.
I'm trying to bind an android SDK for voice chat (zoom sdk).
They have two .aar files (zoomcoomonlib.aar and zoomsdk.aar)
I know I have to create separate binding project for each .aar and then reference them.
While binding zoomsdk.aar I'm getting the below error
The type `Com.Zipow.Videobox.Onedrive.ErrorEventArgs' already contains a definition for `P0' (CS0102) (B14)
In the .aar file I navigated to the package com.zipow.videobox.onedrive; to the interface IODFoldLoaderListener
And below are the contents of it
So it seems parameter String var1 of method onError is causing the issue.
And xamarin studio generated obj/debug/api.xml confirms it (below screenshot) that onError will have first parameter named p0:
So in this scenario I change the metadata.xml to give this parameter a meaningful name.
Like below screenshot:
But even after doing that I am getting same error. That error didn't resolve.
Moreover now if I see the obj/debug/api/.xml file I see the contents for the class IODFoldLoaderListener remains the same.
So changing the metadata.xml has no effect it seems.
Your definition needs to be changed quite a bit. Here is an example that solves the same problem:
<attr path="/api/package[#name='com.emarsys.mobileengage.inbox']/interface[#name='ResetBadgeCountResultListener']/method[#name='onError' and count(parameter)=1 and parameter[1][#type='java.lang.Exception']]" name="argsType">ResetBadgeCountResultListenerOnErrorArgs</attr>
Please note the /interface and argsType items here as your initial definition is incorrect. You would then change the parameters to strings instead of java.lang.Exception from my example.
Can anyone please tell me how can I debug or find the generated code from data binding. From this link I found out it generates the required code.
I guess you are looking for the auto-generated binding java files.
I was searching them too. And finally I found them in this path:
/app/build/intermediates/classes/debug/{your package}/databinding/ActivityMainBinding.java
i.e.
/app/build/intermediates/classes/debug/com/example/databindingdtest/databinding/ActivityMainBinding.java
Please note that this auto-generated java file is named after your layout's name according to Google's guide:
Custom Binding Class Names
By default, a Binding class is generated based on the name of the layout file, starting it with upper-case, removing underscores ( _ ) and
capitalizing the following letter and then suffixing “Binding”. This class
will be placed in a databinding package under the module package. For example, the layout file contact_item.xml will generate ContactItemBinding. If the module package is com.example.my.app, then it will be placed in com.example.my.app.databinding.
Hope this can help you :-)
You can't debug it because it generates necessary code only at the compile time.
I'm trying to learn how to program android applications, so I downloaded the ADT bundle that google supplied, and I tried following the tutorial that allowed me to create a simple application. However, during the procedures, there are several instructions telling me to open up the fragment_main.xml file, but my layout/res/ directory did not have this file, only the activity_main.xml file. Furthermore, when creating new Android activities, there was never an option to name my fragment layout, indicating that eclipse just doesn't create it for some reason. I didn't think this would be an issue at first (I just edited activity_main instead), until I realized that the tutorial wanted us to use the some information from the fragment class or xml file.
Does anyone know why my Eclipse IDE is not creating a fragment_main.xml? I will try to supply more details if necessary.
While creating the new Android Project in one of the panels select "Blank activity with Fragment" instead of default selection "Blank Activity". The Android Developer tutorial does not say anything about it. Doing so will create the file fragment_main.xml in res/layout/ which is needed to continue subsequent steps.
Based on the versions you indicated in the comment response, I think updating to the later versions (22.6+) would help, as discussed in https://code.google.com/p/android/issues/detail?id=67421
Try creating a new project with "Blank Activity with Fragment". I hope this is helpful.
Open MainActivity.java from the src/(package name file)/ directory. Then inside the java file there is a method called OnCreate() that has setContentView(R.layout.activity_main) as default.
Change that to R.layout.activity_main to R.layout.fragment_main
so instead of having
setContentView(R.layout.activity_main)
you'll have
setContentView(R.layout.fragment.main)
Once that's done change the name of the activity_main.xml file under the /res/layout/ directory to fragment_main.xml
Thanks for that Onik!