You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
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!
The text was updated successfully, but these errors were encountered: