Fixed
Status Update
No update yet.
Comments
sl...@google.com
this would be nice but given Compose and all other priorities, we are not planning to make any big investments in data binding (support KSP is a very big task).
nk...@google.com
Makes sense. And is there any way to trigger data binding without kapt plugin, assuming there are no custom binding adapters in given module?
pa...@mv-nordic.com
unfortunately no. data binding still needs to be able to read your code and annotation processing is the only API that allows us to do it :(
sl...@google.com
nk...@google.com
It's a very disappointing decision for many projects who heavily depend on data binding, which will never be able to get rid of all bindings code and especially rewrite all UI to Compose.
It means that bindings are essentially deprecated
Description
// classpath 'com.android.tools.build:gradle:2.0.0-alpha9'
testCompile 'junit:junit:4.12'
compile 'com.android.support:appcompat-v7:23.1.1'
androidTestCompile('com.android.support.test:runner:0.4.1') {
exclude module: 'support-annotations'
}
androidTestCompile('com.android.support.test:rules:0.4.1') {
exclude module: 'support-annotations'
}
What steps will reproduce the problem?
1. Setup example project with a FooService that returns itself via its LocalBinder (see attached sample project for easy setup).
2. Setup a test case using a ServiceTestRule that has 5 methods. Each of these methods call activityRule.bindService() and get the service via the returned 'LocalBinder.getService()' method.
3. Run the androidTest. First test will pass, 4 next tests will fail.
How are you running your tests (via Android Studio, Gradle, adb, etc.)?
Results are the same when running via Android Studio as well as `./gradlew connectedAndroidTest`.
What is the expected output? What do you see instead?
Expected: All 5 tests green. The service should always be shutdown at the end of each test by the ServiceTestRule.
Actual: First test green, other tests red - caused by a NullPointerException at LocalBinder.getService()).
Overall, this means we can't write more than one @Test method for a single service, because all following tests might fail.