[Appium 1.15] - getting wrong attribute value for 'XCUIElementTypeSwitch' element

DanK · October 3, 2019, 3:37pm

Hi, I’m using real iOS devices for testing and i have several ‘XCUIElementTypeSwitch’ toggles in my app, to change state of these toggles I’ve used next method: driver.findElement(MobileBy.AccesibilityId(‘toggleId’)).getAttrinute(‘value’), if it’s equals to 1 then toggle is enabled and vice versa. But now I’m always getting 0, it doesn’t depend on toggle state, therefore, when I’m trying to check this element using Appium desktop or getting page source I can see correct value!

It used to work before update to Appiun 1.15 and iOS 13, this is important!

Can someone help me to solve this ‘getAttribute()’ method issue please???

KazuCocoa · October 4, 2019, 4:21pm

Does includeNonModalElements help in your case?

github.com

appium/appium/blob/master/docs/en/advanced-concepts/settings.md

## Settings

Settings are a new concept introduced by appium. They are currently not a part of the Mobile JSON Wire Protocol, or the Webdriver spec.

Settings are a way to specify the behavior of the appium server.

Settings are:
 - Mutable, they can be changed during a session
 - Only relevant during the session they are applied. They are reset for each new session.
 - Control the way the appium server behaves during test automation. They do not apply to controlling the app or device under test.

An example of a setting would be `ignoreUnimportantViews` for Android. Android can be set to ignore elements in the View Hierarchy which it deems irrelevant. Setting this can cause tests to run faster. A user who *wants* to access the ignored elements however, would want to disable `ignoreUnimportantViews`, and reenable it afterwards.

Another example of a use-case for settings would be telling appium to ignore elements which are not visible.

Settings are implemented via the following API endpoints:

**POST** /session/:sessionId/appium/settings

>Expects a JSON hash of settings, where keys correspond to setting names, and values to the value of the setting.

This file has been truncated. show original

If it works Appium 1.15, Xcode 10.3 and iOS 12, the root cause could be iOS 13 or Xcode 11’s XCTest framework side.

CrashTestDummy · October 8, 2019, 9:44am

I have similar issue. I can not get “value” from found element. I wait when test application will be released on xcode 11. Now i have workaround, before i want to get value from element i have to finds all textfilde elements

driver.findElements(By.className(“XCUIElementTypeTextField”));
element.getAttribute(“value”);

what is xcode version, your ios developers, use to release application? I do not know why but there is any connection between xcod use to release application and xcode you are use to tests.

lagolas · October 22, 2019, 12:02pm

Same issue here.

our page source shows value = 1 and when we try: find_element_by_ios_predicate(‘wdName =“Wi-Fi” and wdType=“XCUIElementTypeSwitch”’).get_attribute(‘value’)

we get 0

Shy · November 20, 2019, 9:56am

Have the same issue.
loginScreen.setUpFeatureFlagsForm().mainScreenViper().getValue() always gets 0 value.
mainScreenViper locator is MobileBy.iOSNsPredicateString("type = 'XCUIElementTypeSwitch' AND name = 'mainScreenVIPER'")
getValue() always returns 0 value despite of switcher position (turn on or turn off). Problem came after Appium version update to 15.1 version.
Can someone provide any solution for this issue?