Hi everyone,
To perform automation on the Kepler app, we are using the Kepler automation driver (JSON‑RPC) through Appium. Below are the capabilities used:
{
“platformName”: “Kepler”,
“appium:automationName”: “automation-toolkit/JSON-RPC”,
“kepler:device”: “vda://{{device_id}}”
}
Issue: Appium Inspector returns random View IDs and highlights hidden UI elements
While identifying elements, Appium Inspector always returns random/dynamic test_id, even though the development team confirmed that views have been assigned stable Test IDs in this format:
Plain Text
<PackageName>{test_id}
Additionally, Appium Inspector highlights hidden/non-visible UI elements instead of the visible element on the screen. This makes element identification unreliable.
Environment
-
App: Kepler
-
Automation Tool: Appium Inspector using Kepler automation driver (JSON‑RPC)
-
Platform: Vega OS
-
Build: Latest internal build
Description
During UI automation inspection:
-
Returned
test_iddo not match the assigned Test IDs. -
IDs appear random and change between sessions and builds.
-
Appium Inspector often hovers over invisible UI elements instead of the visible ones.
This leads to inconsistent or incorrect element identification.
Steps to Reproduce
-
Launch the Kepler app.
-
Navigate to any screen with assigned Test IDs.
-
Open Appium Inspector and inspect visible UI elements.
-
Observe the returned
test_idand highlighted element.
Expected Result
- The automation driver should return the assigned Test ID:
<PackageName>{test_id}
- Appium Inspector should highlight the actual visible UI element being inspected.
Actual Result
-
View IDs are random/dynamic, not the assigned Test IDs.
-
Appium Inspector highlights hidden elements instead of the visible ones.
Impact
-
Automation scripts fail across runs due to unstable IDs.
-
Element inspection is inaccurate, blocking reliable automation.
Note: Steps are followed as per developer doc link https://developer.amazon.com/docs/vega/0.22/appium-inspector.html