Fixed
Status Update
No update yet.
Comments
[Deleted User] <[Deleted User]>
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).
[Deleted User] <[Deleted User]>
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
sl...@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 :(
Description
Version used:0.5
What steps will reproduce the problem?
1. Have a test wtih @RequiresDevice in the suite
2. Create an emulator with x86_64 ABI
3. Run suite from step #1 on emulator from #2
How are you running your tests (via Android Studio, Gradle, adb, etc.)?
Android Studio, but I don't think it matters
Expected output: @RequiresDevice test is not executed
Actual output: @RequiresDevice test IS executed
TestRequestBuilder$RequiresDeviceFilter checks for "goldfish" value on Build.HARDWARE which is correct for ABI x86, but not for ABI x86_64 - value is "ranchu" there.