Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Appium 2.0 Windows Driver Session Routing

See original GitHub issue

The problem

Windows driver installed via ‘appium driver install windows’ (windows@1.18.0)

When attempting to create new session it fails.

Environment

Appium CLI version - 2.0.0-beta9
Desktop OS - Windows 10
Node.js - v14.15.4
Npm - 6.14.11
Mobile platform/version under test: Windows/UWP

More Info

[debug] [HTTP] Request idempotency key: a6f5f6b8-b828-419f-9dc4-c5f04f2bdc60
[HTTP] --> POST /wd/hub/session
[HTTP] {"platformName":"WINDOWS","deviceName":"WINDOWS" ... desiredCapabilities Logged here but redacted}
[debug] [HTTP] No route found for /wd/hub/session
[HTTP] <-- POST /wd/hub/session 404 17 ms - 211
[HTTP]

Issue Analytics

State:
Created 3 years ago
Comments:22 (8 by maintainers)

Top GitHub Comments

3reactions

KazuCocoacommented, Jan 27, 2021

The error is expected. Appium 2.0 requires W3C spec capabilities, but probably your request does not have it. So, wdaLocalPort should be appium:wdaLocalPort.

Appium clients add appium: for non-standard capabilities, but probably your grid does not have such behavior.

0reactions

KazuCocoacommented, Apr 18, 2022

we’re still working on documentation, but you can find it in https://github.com/appium/appium/blob/2.0/docs/en/advanced-concepts/migrating-to-appium-2.0.md#bangbang-capabilities