Skip to content
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

Braintree drop-in-ui appium automation issue in appium #11176

Closed
kadir-calvid opened this issue Aug 13, 2018 · 2 comments
Closed

Braintree drop-in-ui appium automation issue in appium #11176

kadir-calvid opened this issue Aug 13, 2018 · 2 comments
Labels
Needs Info typically non-actionable; needs author to respond Question

Comments

@kadir-calvid
Copy link

The problem

I want to do appium automation for Braintree drop-in-ui but unable to inspect the elements to automate
is there any way to inspect elements for find there ids or class name

Environment

  • Appium version (or git revision) that exhibits the issue: 18.2
  • Desktop OS/version used to run Appium: Ubuntu
  • Node.js version (unless using Appium.app|exe): 9.5
  • Mobile platform/version under test: Android
  • Real device or emulator/simulator:Real device

Details

Hello,
I want to do appium automation for Braintree drop-in-ui but unable to inspect the elements to automate
is there any way to inspect elements for find there ids or class name
Any suggestion and solution would be appreciated

Link to Appium logs

[elementByAndroidUIAutomator("new UiSelector().textContains("Expiration Date")")] Error response status: 7, , NoSuchElement - An element could not be located on the page using the given search parameters. Selenium error: An element could not be located on the page using the given search parameters.

Thanks
kadir khan

@mykola-mokhnach
Copy link
Collaborator

Appium just reflects what the application itself provides to accessibility framework. This means that there is nothing to be done on our side if some element is not present in the tree.

However, it is possible that the element itself is a part of web context and you're trying to interact with it being in native context. then switching the context would help to resolve the issue.

@mykola-mokhnach mykola-mokhnach added Question Needs Info typically non-actionable; needs author to respond labels Aug 13, 2018
@lock
Copy link

lock bot commented Aug 16, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Aug 16, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Needs Info typically non-actionable; needs author to respond Question
Projects
None yet
Development

No branches or pull requests

2 participants