Fixed
Status Update
No update yet.
Comments
uc...@google.com
al...@google.com
je...@google.com
hu...@google.com
That seems quite bad :/ weird.
We have fairly large test projects which do not take anywhere close to it, maybe your code is triggering some bad code path.
Can you provide a sample or share your project with us? It is impossible to do something here unless we have a reproduction case. Might also possibly be related to your machine configuration.
We have fairly large test projects which do not take anywhere close to it, maybe your code is triggering some bad code path.
Can you provide a sample or share your project with us? It is impossible to do something here unless we have a reproduction case. Might also possibly be related to your machine configuration.
Gi...@iiitd.ac.in
Let me see what I can do on the reproduction as I am anyways blocked on this. I will try to extract out the DB module in a new project and see if it reproduces the issue.
hu...@google.com
Attaching the sample project. When I run the project through the android studio or even command line, I see the described issue.
Try uncommenting room-compiler dependency from app's build.gradle, it does not have the issue because room compiler is not at work.
Try uncommenting room-compiler dependency from app's build.gradle, it does not have the issue because room compiler is not at work.
hu...@google.com
Did you get a chance to look at it?
am...@google.com
am...@google.com
FYI. I see that if I comment out applying google-services plugin (at the end of the app's build.gradle file), that fixes the issue too. Hence, you may need to apply a google-services plugin with a json file to reproduce the issue.
Not sure what is going on but certainly, somethings are not playing well together.
Not sure what is going on but certainly, somethings are not playing well together.
hu...@google.com
Above comment is NOT TRUE, it seems I did not do a code change after commenting out apply google-services plugin. That's why the build passed.
Description
AI-171.4182969, JRE 1.8.0_152-release-884-b01x64 JetBrains s.r.o, OS Mac OS X(x86_64) v10.12.4 unknown, screens 1366x768, 1280x800
IMPORTANT: Please read
When data binding is enabled and there is an error in an layout XML file and I try to build the app, the build fails and the messages view shows which files have the problem. In case of a layout file, the file shown there points to an autogenerated version of the file at path "<app module>/build/intermediates/data-binding-layout-out/<build variant>/layout/<filename>" instead of the original one. Consecutively, double clicking it takes me to that same autogenerated file which should not be edited.
It would be great if it could point to the original file here.