AccessibilityService is Destroyed when uiautomator is run

Question

I am new to android and I am trying to explore the AccessibilityService. I have extended the AccessibilityService class, which gets the AccessibilityEvents and I am able to use the events.

I see a problem when I run "uiautomator dump". My AccessibilityService gets destroyed and I do not get any Accessibility Events. Is there a way to work around this problem?

Any help or suggestion appreciated. Thank you very much in advance.

The stack trace is attached below:

W/System.err( 3832):    at com.example.myservice.MyAccessibilityService.onUnbind(MyAccessibilityService.java:185)
W/System.err( 3832):    at android.app.ActivityThread.handleUnbindService(ActivityThread.java:2629)
W/System.err( 3832):    at android.app.ActivityThread.access$1800(ActivityThread.java:141)
W/System.err( 3832):    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1348)
W/System.err( 3832):    at android.os.Handler.dispatchMessage(Handler.java:99)
W/System.err( 3832):    at android.os.Looper.loop(Looper.java:137)
W/System.err( 3832):    at android.app.ActivityThread.main(ActivityThread.java:5103)
W/System.err( 3832):    at java.lang.reflect.Method.invokeNative(Native Method)
W/System.err( 3832):    at java.lang.reflect.Method.invoke(Method.java:525)
W/System.err( 3832):    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:737)
W/System.err( 3832):    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
W/System.err( 3832):    at dalvik.system.NativeStart.main(Native Method)

Did you find a workaround for this? – dazza5000 Apr 10 '19 at 17:15 — dazza5000, Apr 10 '19 at 17:15

score 0 · Answer 1 · answered May 21 '15 at 11:50

0

UiAutomator can't be used along with an AccessibilityService. When you turn on the service the uiAutomator will crash.

However, as UiAutomator 2.0 is based on instrumentation you will probably be able to access the information you need without the service.

answered May 21 '15 at 11:50

Inês

882
3
13
28

Is the UIAutomatorViewer updated to use UiAutomator 2.0? – dazza5000 Apr 10 '19 at 17:23

score 0 · Answer 2 · answered Aug 07 '19 at 04:01

I faced the same problem & just found out the solution from here.

The answer was written in Kotlin so I modified mine here as I am writing in Java:

 int flags = UiAutomation.FLAG_DONT_SUPPRESS_ACCESSIBILITY_SERVICES;
 Configurator.getInstance().setUiAutomationFlags(flags);

 mDevice = UiDevice.getInstance(getInstrumentation());

score 0 · Answer 3 · answered Jul 13 '21 at 18:11

0

Please try with uiautomator2 having version above 18 and make disable supress accessibility service flag as true, which ll run accessibility service as well as driver seamlessly without terminating.

answered Jul 13 '21 at 18:11

Shailaja Parida

1

Giving a code sample would be highly recommended – Marcel Hofgesang Jul 14 '21 at 11:40

Xiao · Answer 4 · 2022-08-23T03:05:11.133

You could switch to UiAutmator2 with following code from appium-uiautomator2-server:

    private void setAccessibilityServiceState() {
        if (Build.VERSION.SDK_INT < Build.VERSION_CODES.N) {
            return;
        }
        Configurator.getInstance().setUiAutomationFlags(
            UiAutomation.FLAG_DONT_SUPPRESS_ACCESSIBILITY_SERVICES);
        } else {
            // We can disable UiAutomation.FLAG_DONT_SUPPRESS_ACCESSIBILITY_SERVICES
            // only when we set the value as zero
            Configurator.getInstance().setUiAutomationFlags(0);
        }
    }

AccessibilityService is Destroyed when uiautomator is run

4 Answers4