Fixed
Status Update
No update yet.
Comments
ma...@gmail.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).
ma...@gmail.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?
nk...@google.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
Version used: 0.4.1
What steps will reproduce the problem?
0. enable strict mode (StrictMode.setVmPolicy(new StrictMode.VmPolicy.Builder().detectAll().penaltyLog().penaltyDeath().build());)
1. run a test using ActivityTestRule
2. do an orientation change during test
How are you running your tests (via Android Studio, Gradle, adb, etc.)?
android studio and gradle
What is the expected output? What do you see instead?
the problem is that the ActivityTestRule keeps a reference to the first activity and after orientation change a new one is created. this causes a penalty for violation of VmPolicies.