IssueTracker

Hello

I'm trying to instrument an AccessibilityService.
My idea is to perform some actions on a dummy Activity.

However I noticed my AccessibilityService gets disabled as soon as I start my Espresso test with the dummy Activity.

I tried to hack around it by assembling the APK and test-APK myself.

./gradlew assembleDebug
./gradlew assembleDebugAndroidTest

adb install "app/build/outputs/apk/androidTest/debug/app-debug-androidTest.apk"
adb install "app/build/outputs/apk/debug/app-debug.apk"

Enabling the service with

adb shell settings put secure enabled_accessibility_services <package-name>/<AccessibilityService-packagename>

And starting the test with

adb shell am instrument -w -m <package-name>.test/androidx.test.runner.AndroidJUnitRunner

I put a Toast in my AccessibilityService#onServiceConnected, AccessibilityService#onInterrupt and AccessibilityService#onUnbindfunctions like this.

override fun onServiceConnected() {
    Toast.makeText(this, "Enabled!", Toast.LENGTH_SHORT).show()
}

I can clearly see the Enabled Toast However none of my other Toast's are visible, but as soon as the test starts the service is disabled as I can see in the System Settings app. (See attached screenshot)

Is this intended behaviour?
If so, can this be disabled?
Or what other alternatives are there to instrumentation test an Accessibility Service?

Thanks in advance