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

when device is locked by pin or password we might have NoSuchElementException with occupied hub/stf #1548

Open
vdelendik opened this issue Dec 6, 2021 · 0 comments
Labels

Comments

@vdelendik
Copy link
Contributor

let's investigate how we can handle such use-case when device is occupied in grid/stf but driver fail on startup, i.e. in carina it is null!

2021-12-06 14:12:30 MobileFactory [TestNG-test=Mobile test-1-34] [ERROR] Driver started but display seems locked!
org.openqa.selenium.NoSuchElementException: An element could not be located on the page using the given search parameters.
For documentation on this error, please visit: https://www.seleniumhq.org/exceptions/no_such_element.html
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:17:03'
System info: host: 'DELENDIK-XPS', ip: '192.168.2.99', os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '11.0.11'
Driver info: driver.version: AndroidDriver
remote stacktrace: NoSuchElementError: An element could not be located on the page using the given search parameters.
    at AndroidUiautomator2Driver.findElOrEls (/usr/lib/node_modules/appium/node_modules/appium-android-driver/lib/commands/find.js:75:11)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Todo
Development

No branches or pull requests

1 participant