Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[iOS] Appium returns wrong element attribute value

See original GitHub issue

The problem

I am trying to get elements attribute “value” value. At first, I print page source (pasting here just one element I am interested in):

<XCUIElementTypeSwitch type="XCUIElementTypeSwitch" value="1" name="s_settings_online_switch_value" label="Use online shopping" enabled="true" visible="true" x="349" y="385" width="51" height="32"/>

Here I clearly see that value=1. Next, I am calling GetAttribute method to find attributes “value” value. I get that value=0. Appium server log’s shows:

2019-10-23 09:27:02:394 [MJSONWP (d360e76d)] Calling AppiumDriver.getAttribute() with args: ["value","32010000-0000-0000-3607-000000000000","d360e76d-af5e-4883-87c8-4c6663172511"]
2019-10-23 09:27:02:394 [XCUITest] Executing command 'getAttribute'
2019-10-23 09:27:02:396 [WD Proxy] Matched '/element/32010000-0000-0000-3607-000000000000/attribute/value' to command name 'getAttribute'
2019-10-23 09:27:02:396 [WD Proxy] Proxying [GET /element/32010000-0000-0000-3607-000000000000/attribute/value] to [GET http://localhost:8103/session/1253BD09-66C2-47A6-91DA-FC8EEB3D47E3/element/32010000-0000-0000-3607-000000000000/attribute/value] with no body
2019-10-23 09:27:03:025 [WD Proxy] Got response with status 200: {
2019-10-23 09:27:03:026 [WD Proxy]   "value" : "0",
2019-10-23 09:27:03:026 [WD Proxy]   "sessionId" : "1253BD09-66C2-47A6-91DA-FC8EEB3D47E3"
2019-10-23 09:27:03:026 [WD Proxy] }
2019-10-23 09:27:03:026 [MJSONWP (d360e76d)] Responding to client with driver.getAttribute() result: "0"

I have encountered this after updating Appium from 1.14.2 to 1.15.1.

Environment

Appium version (or git revision) that exhibits the issue: 1.15.1
Last Appium version that did not exhibit the issue (if applicable): 1.14.2
Desktop OS/version used to run Appium: macOS Mojave 10.14.6
Node.js version (unless using Appium.app|exe): 10.16.3
Npm or Yarn package manager: 6.9.0
Mobile platform/version under test: iOS 11.0.3
Real device or emulator/simulator: real device iPhone 6s+
Appium CLI or Appium.app|exe: 1.15.1

Code To Reproduce Issue [ Good To Have ]

Something like this:

var state = element.GetAttribute("value");

Issue Analytics

State:
Created 4 years ago
Reactions:2
Comments:8

Top GitHub Comments

2reactions

hyungmin-steve-youcommented, Oct 29, 2019

In case someone is not aware, to get around this issue you can install both xcode 11.1 (for iOS 13 automation only) and xcode 10.x (for iOS 12 and below) on your machine. So depending on which automation to run you can switch the context on which xcode SDK to use. Please see below link:

http://appium.io/docs/en/advanced-concepts/multiple-xcode-versions/

0reactions

mykola-mokhnachcommented, Nov 1, 2019

Closed as third party value