Accessibility services stops when running appium tests on android device

[vivek978]

The problem

I am automating an android application which uses accessibility services to function. As soon as I use appium with the app accessibility services stops.

Environment

• Appium version (or git revision) that exhibits the issue: 1.4.0
• Last Appium version that did not exhibit the issue (if applicable):
• Desktop OS/version used to run Appium: Mac OS X Yosomite
• Node.js version (unless using Appium.app|exe):
• Mobile platform/version under test: Android 4.4.4
• Real device or emulator/simulator: Real Device
• Appium CLI or Appium.app|exe: Appium.app

Details

Describe in more detail the problem you have been experiencing, if necessary.

Link to Appium logs

Create a gist which is a paste of your full Appium logs, and link them here. Do not paste your full Appium logs here, as it will make this issue very long and hard to read! If you are reporting a bug, always include Appium logs!

[scottdixon-zz]

@vivek978 - please try with a more recent version of Appium:
npm install -g appium

Let me know if the issue persists and I'll investigate further.

[vivek978]

@scottdixon I checked with more recent version of Appium i.e 1.5, but issue still persist.

[nikhil969]

any updates

[adarliu]

I also met this issue. After some investigation, I think this issue was not caused by Appium, but a limitation of Android uiautomator. It seems when ui automator is running, the other app accessibility services will be stopped.

To prove this, you can:
1 enable the accessibility "TalkBack", or any other third-party apps.
2 start uiautomator process: adb shell uiautomator events (This will just print the accessibility events)
3 The "TalkBack" service (or any other apps) stops working even the accessibility switch is shown on in the Settings.

[ghost]

Hi Guys,
I am also facing the same issue with Appium 1.6.5 version. Is there any update on this ???

[dpgraham]

Duplicate of: #4910

This is a third party problem.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.