Fixed
Status Update
No update yet.
Comments
uc...@google.com
Reproduced in
Android Studio 3.1
Build #AI-173.4670197, built on March 21, 2018
JRE: 1.8.0_152-release-1024-b01 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 4.9.0-6-amd64
Android Studio 3.1
Build #AI-173.4670197, built on March 21, 2018
JRE: 1.8.0_152-release-1024-b01 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 4.9.0-6-amd64
yb...@google.com
this is a problem in data binding and how it handles dependencies.
It is a bit tricky for it to work well w/ API vs Implementation.
You can work around this by using API for now (i know it is slower :/).
It is a bit tricky for it to work well w/ API vs Implementation.
You can work around this by using API for now (i know it is slower :/).
yb...@google.com
yb...@google.com
yb...@google.com
this is fixed, should be available in 3.2, canary 19. (only works with V2 which is on by default in 3.2)
Description
Version of Gradle Plugin: 3.1.0
Version of Gradle: 4.4
Version of Java: 1.8
OS: MacOS 10.13.3
source of sample:
In sample app three modules:
Application module that has implementation project(':featurelevel1')
Level1 Module that has implementation project(':featurelevel2')
Level2 Module with main launcher activity
All modules have databinding enabled and compiler v2 is enabled
To reproduce crash:
Just compile and start app and then there will be crash:
NPE com.github.nekdenis.featurelevel2.databinding.ActivityLevel2Binding.setUser
This happens because DataBinderMapperImpl does not know about com.github.nekdenis.featurelevel2.DataBinderMapperImpl()
If uncomment this line app will work:
But in this case application module should now about EVERY gradle-module of app that is unacceptable.