appium / appium/java-client

What causes AccessibilityNodeInfoError?

Open
#1,248 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
1.3k
Forks
752
Avg merge
6d 21h
Merged PRs (30d)
8

Description

Description

I am trying to test an activity that is essentially a "book" with a table of contents composed of multiple sections including texts, videos, and pictures. Whenever I try to browse/scroll through this book via the table of contents, Appium would give error:

io.appium.uiautomator2.common.exceptions.UiAutomator2Exception: Timed out after 10000 milliseconds waiting for root AccessibilityNodeInfo

Sometimes even after loading in the activity, the test would be unable to access any of the UI Elements and would give the same error. I've also tried to view the book via the UIAutomatorViewer and it appeared to have worked for an arbitrary book, and was unable to view other books afterwards.

Environment

  • java client build version or git revision if you use some shapshot: 7.0.0
  • Appium server version or git revision if you use some shapshot: 1.13.0
  • Desktop OS/version used to run Appium if necessary: Mac OS
  • Node.js version (unless using Appium.app|exe) or Appium CLI or Appium.app|exe:
  • Mobile platform/version under test:
  • Real device or emulator/simulator: Real Device

Details

Here are some screenshots of when I am using UIAutomatorViewer:

Book with content in it
image

Table of Contents
image

Error after clicking on a section:
image

Code To Reproduce Issue [ Good To Have ]

Exception stacktraces

https://gist.github.com/thv92/0bd9150d5b4073d49d98f5594e887459

Link to Appium logs

https://gist.github.com/thv92/431e8b71c3558ff2bf8b38d6320a1fd9

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked exception stacktrace and Appium logs, then compare them with the supplied Java client, Appium server, and real-device environment details. The issue provides no reproduction code or project files; done would require identifying a reproducible cause for the AccessibilityNodeInfo timeout and documenting the relevant conditions or resolution.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.