-
-
Notifications
You must be signed in to change notification settings - Fork 765
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
findelement byname does not work with appium 1.9.1 #1050
Comments
@jlipps do you aware any issue related to? thanks |
name was deprecated in favor of accessiblity id |
so, for ios, we should use by.accessibilityid or by.id? where we can find the info on change for search property support ? @saikrishna321 |
@helenren this was very old change which went through, may be in version 5.0.0 BETAX not sure though.. But for sure this change was done long back. |
Hmm, the change that you mentioned is for page object tools. While in my test, I use By.Name directly instead of @findby annotation. I am kind lost. @saikrishna321 |
Did more try. Instead of using by.name, switch to use the xpath to find an element on a native page. Compared with java_client 6.1.0 + appium 1.8.1 and java_client 6.1.0 + appium 1.9.1, the test app, ios version are same. Successfully fin the element for java_client 6.1.0 + appium 1.8.1 , while fail to find it for java_client 6.1.0 + appium 1.9.1. One thing cannot understand is, for java_client 6.1.0 + appium 1.9.1, after finding the element, call element/sync instead of element/displayed? @saikrishna321 Here is detail logs: With java_client 6.1.0 + appium 1.9.1, fail to find it. Here is the appium logs: 2018-10-26 00:07:49:765 - [HTTP] --> GET /wd/hub/session/3ee94005-3eee-44f8-93cd-e66d78f6cf90/context While for java_client 6.1.0 + appium 1.8.1, successfully find the element: 2018-10-26 00:13:47:460 - [HTTP] --> GET /wd/hub/session/ae8b670d-e4d4-4652-8982-e8ead579b404/context |
I have the similiar issue on this like this : NotImplementedError: Method is not implemented anyone have the simliar issue as well ? |
after configure via using capability: MobileCapabilityType.FORCE_MJSONWP to true to still use OSS instead of the default W3C, this issue has been gone for me. @ndeztea |
@michaeljohndamo1 The xpath locator is invalid. It only supports double quotes as string separators. |
Hi @mykola-mokhnach sorry, i am still newbie please be patient on me. Can you please explain more? coz i really don't understand. I am still learning, btw this runs on browser but when i have changed the setup to mobile chrome. I am facing this error. I've been searching and trying all the stuff that i've searched on the internet but still no luck. |
What exactly is not understandable? |
@mykola-mokhnach sorry i cannot understand why i am facing this error. The answer that it only supports double quotes as string separators. I've tried to comment out the xpath / button if it will still continue to send keys. But i still face the error even without the xpath |
Hi @michaeljohndamo1 could you please go with xpath instead of id. Let's have a try. |
Okay sir will try now, thank you :) |
@michaeljohndamo1 I can see the id is "username" but in code you have written "_username" please change it. |
@shibupanda oh sir it works! thank you so much. This is my first time participating here in github i am really desperate and thanks to you, you have solved my problem. Sir may i know why id doesn't work earlier? and have to change to xpath? is it good to ask following question here? |
On a native page, my test tries to find an element via byname: command passed into driver is: findElement(By.name: EULA.agree), while I saw the command executed to the appium server is:
2018-10-25 03:23:24:329 - info: [HTTP] --> POST /wd/hub/session/22bd911d-ed10-47f6-bd77-f327b5562c48/elements
2018-10-25 03:23:24:329 - info: [HTTP] {"value":"*[name='EULA.agree']","using":"css selector"}
The same test works fine against appium 1.8.1
Environment
The text was updated successfully, but these errors were encountered: