-
-
Notifications
You must be signed in to change notification settings - Fork 758
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
Java-client will throw exceptions - GridException: Cannot extract a capabilities xxx with webdriver 3.x #655
Comments
@fionazj Could you describe how do run hub/node?
Do you mean Selenium server? Or do you use another Selenium client dependency? |
@TikhomirovSergey , I mean the selenium server And here's how I start hub and node: The hub started by following command: For the node, just a config file, and Appium will load the config file appium_node_config_ios.json:
|
@TikhomirovSergey issue is still there with BETA9 as well. @fionazj any workaround you found ? |
The bug was fixed at #682. For now it is recommended to use older selenium server. The fix is going to be available in 5.0.0 soon. |
Hi, I am asking because I see "GridException: Cannot extract a capabilities" for a combination of appium java-client 6.1.0 and selenium 3.6.0. I assume the nature of the issue is the same as described in this thread. |
One should always use the selenium version, which is set in the gradle config: Line 53 in 3c05402
|
Description
Before the session of the simulator is started, some errors will show up in hub log as follow.
Environment
Details
Since webdriver3.x is released, so we need to do a trail run on that, so I updated the webdriver in both our project and hub, also java-client in the project, and start the hub to execute cases. But when a session start, exception occurs, and seemed like the Appium is fine, but java-client 5.x with webdriver3.x is not, did i miss something?
And it was totally fine when I change back webdriver to 2.53.0
Code To Reproduce Issue [ Good To Have ]
Hub startup command line:
Node configuration of Appium
Ecxeption stacktraces
Link to Appium logs
The text was updated successfully, but these errors were encountered: