Fixed
Status Update
No update yet.
Comments
uc...@google.com
yb...@google.com
it does look like a problem where not all errors are shown in the ide.
For the first example, what happens is that compilation fails for a layout file and data binding does not generate the binding code but still generates another class that looks for the missing generated class (hence you get another error).
I would expect both to be visible, I'm not sure why.
xa...@google.com
ok thanks, I'll move this to the output window. I don't think we should need --stacktrace to get the proper cause. We'll see what we can do.
yb...@google.com
these two seems related though i'm not sure if it is a dupe:
Description
Version of Gradle Plugin:
Version of Gradle: 5.6.4
Version of Java:
OS: macosx 10.15.4
Steps to Reproduce:
1. create simple project which using DataBinding feature (
2. make some simple error at markup (like referencing undefined property android:text="@{viewModel.wrongProperty}" )
3. try "Make project"
4. gradle build will fail with _completely_ unrelated to real error text:
import com.example.myapplication.databinding.MainFragmentBindingImpl;
^
symbol: class MainFragmentBindingImpl
5. open Preference->Build,Execution,Deployment->Compiler and add Command-line options: --stacktrace --debug
6. try "Make project"
7. gradle build will fail with _right_ error message:
Could not find accessor com.example.myapplication.ui.main.MainViewModel.wrongProperty
It's obvious that --stacktrace and -debug slows down build process.
Please display right java file generation error without these options.
canary Android Studio 4.1 + gradle 6.3 has same problem