Fixed
Status Update
No update yet.
Comments
uc...@google.com
This was broken by 3bca759a5ff08352de831bb1e9b61b1ec2b3362d.
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
yb...@google.com
Almost 2 months later and this is still broken
yb...@google.com
Since there is no progression, I wanted to share our quick-fix for the issue.
#sdkmanager --package_file=${PATH_WORKSPACE}/packages
while read p; do echo "y" | sdkmanager "${p}"; done <${PATH_WORKSPACE}/packages
#sdkmanager --package_file=${PATH_WORKSPACE}/packages
while read p; do echo "y" | sdkmanager "${p}"; done <${PATH_WORKSPACE}/packages
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.