Error when start appium session after upgrading to nightwatch 2.0 #3143
Victoria0214
started this conversation in
General
Replies: 1 comment
-
fixed with adding "@nightwatch/selenium-server": "^4.1.2", and default_path_prefix: '/', |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi all
I am upgrading nightwatch from 1.7.9 to "^2.0.9", and we faced an error while start winAppDriver
Error winAppDriver:
`POST /wd/hub/session HTTP/1.1
Connection: close
Content-Length: 180
Content-Type: application/json; charset=utf-8
Host: localhost:4723
User-Agent: nightwatch.js/2.1.0 (windows)
{"desiredCapabilities":{"browserName":"","platformName":"windows","deviceName":"WindowsPC","app":"Root"},"capabilities":{"alwaysMatch":{"browserName":"","platformName":"windows"}}}
HTTP/1.1 404 Not Found`
Nightwatch throw following error:
WebDriverError: Unable to parse new session response: {} at Executor.execute (node_modules\selenium-webdriver\lib\http.js:478:15) at processTicksAndRejections (node:internal/process/task_queues:96:5) { remoteStacktrace: '' }
New sesssion was created like:
const { driver, By2, windowsAppDriverCapabilities } = require("selenium-appium"); const capabilites = windowsAppDriverCapabilities("Root");
Or you can reproduced with:
try{
const webdriver = await new Builder()
.usingServer("http://localhost:4723")
.withCapabilities(windowsAppDriverCapabilities("Root"))
.build();
console.log(webdriver)
}catch (e) {
console.log(e)
}
Beta Was this translation helpful? Give feedback.
All reactions