Fixed
Status Update
No update yet.
Comments
sl...@google.com
pr...@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).
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?
dn...@google.com
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 :(
Description
Version used: Espresso(3.0.1), Runner and Rules (1.0.1)
What steps will reproduce the problem?
1. Install orchestrator-1.0.1.apk and test-services-1.0.1.apk
2. Build App under Test and Test apk and install on device
3. execute below command for Test Orchestration
adb shell 'CLASSPATH=$(pm path android.support.test.services) app_process / \android.support.test.services.shellexecutor.ShellMain am instrument -w -e \
targetInstrumentation com.package.test/com.package.espressoTests.Instrumentation \android.support.test.orchestrator/.AndroidTestOrchestrator'
After executing above command, it starts execution on device (Samsung Marshmallow) with below log output
MdfppReflectionUtils isMdfEnforced encountered an exception. Cause: java.lang.UnsatisfiedLinkError: No implementation found for boolean com.samsung.android.security.CCManager.isMdfEnforced() (tried Java_com_samsung_android_security_CCManager_isMdfEnforced and Java_com_samsung_android_security_CCManager_isMdfEnforced__) Message: null
MdfppReflectionUtils isMdfEnforced encountered an exception. Cause: java.lang.UnsatisfiedLinkError: No implementation found for boolean com.samsung.android.security.CCManager.isMdfEnforced() (tried Java_com_samsung_android_security_CCManager_isMdfEnforced and Java_com_samsung_android_security_CCManager_isMdfEnforced__) Message: null
If we execute only one/few test case, it shows below output when execution is complete
-Final result — OK (0 tests)
If we execute batch of tests, execution stopped because of process crash due to out of memory.
How are you running your tests (via Android Studio, Gradle, adb, etc.)?
Using adb command
What is the expected output? What do you see instead?
Expected output is to continue execution of next test if there is any crash due to memory issue or due to application crash due to some other reason. I have attached few screenshots which shows memory usage when process crashed and Instrumentation file. Please let me know if you need any other details.