Data Binding:- Binding classes are no longer resolved when using source sets to define custom resource directories [150278876]

Duplicate

of 147609508

Bug

Status Update

No update yet.

Description

ma...@thisisaim.com

created issue #1

Feb 26, 2020 08:44PM

As of Android Studio release 3.6.0 binding classes will no longer resolve within the IDE when using a custom resource directory by adding to source sets i.e

sourceSets {
main {
res.srcDirs += [
'src/main/res/layout/activity',
'src/main/res/layout/fragment',
'src/main/res/layout/adapter',
'src/main/res/layout/view'
]
}
}

When the layout files are moved outside of these directories and into the root "res/layout" directory the binding classes are resolved again.

Studio Build: 3.6
Version of Gradle Plugin: 3.6.0
Version of Gradle: 5.6.4
Version of Java: 1.8
OS: Windows 10

Steps to Reproduce:
1. Specify custom resource directories i.e src/main/res/layout/activity as shown above
2. Add data binding layout "foo_bar.xml" to resource directory "src/main/res/layout/activity/layout/"
3. Rebuild project
4. Note FooBarBinding cannot be resolved within IDE, however the app will build successfully and run.

Comments

uc...@google.com <uc...@google.com> Feb 26, 2020 08:44PM

Assigned to an...@google.com.

xa...@google.com <xa...@google.com> #2Mar 4, 2020 10:35PM

I'm guessing the light classes created for data-binding don't go look into these folders.

da...@google.com <da...@google.com> #3Mar 5, 2020 01:24AM

Status: Duplicate of

147609508

Sorry for the trouble. This is a known issue which has been fixed in 4.0+. We're working to cherry pick a fix into an upcoming 3.6 patch.

ma...@thisisaim.com <ma...@thisisaim.com> #4Mar 5, 2020 09:24AM

Awesome. Thanks for addressing this, looking forward to the patch.

Message last modified on Mar 5, 2020 09:25AM

da...@google.com <da...@google.com> #5Mar 5, 2020 10:00PM

Thanks for being so understanding. I've added this bug to a list of bugs I'll try to ping when 3.6.2 goes out.

da...@google.com <da...@google.com> #6Mar 31, 2020 10:45PM

3.6.2 patch is out. Hopefully you'll find with latest that your issue is fixed. Please let me know if you're still seeing this problem. Thanks!

ma...@thisisaim.com <ma...@thisisaim.com> #7Apr 1, 2020 04:24PM

Looks to have done the trick. Many thanks