-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Appium server node browser is not available #5163
Comments
Which version of appium is the node running? |
Please run the hub and the node with -debug CLI option and attach the hub and the node logs here. |
Same here with selenium 3.8.1, is there still a solution for this? |
Same for me for v3.8.1.
But when I open /grid/api/proxy?id=.... endpoint I saw that Appium version is 1.7.1 P.S. I have the similar config but without 'platform' which is deprecated:
|
I suggest to rename topic of the issue to "Cannot register node(slot) with platform/platformName = iOS" |
Appium 1.7.1 Grid hub console output: 02:58:28.976 INFO - Selenium build info: version: '3.8.1', revision: '6e95a6684b 02:58:52.594 DEBUG - http-outgoing-0 << "Access-Control-Allow-Methods: GET,POST, 02:58:52.603 DEBUG - http-outgoing-0 << Date: Mon, 11 Dec 2017 08:00:18 GMT 02:58:57.612 DEBUG - Closing connections idle longer than 100 MILLISECONDS 02:58:57.658 DEBUG - http-outgoing-1 << "Access-Control-Allow-Methods: GET,POST, 02:58:57.670 DEBUG - http-outgoing-1 << Date: Mon, 11 Dec 2017 08:00:24 GMT Appium node console output: appium --nodeconfig /path/to/nodeconfig.json --debug |
@kool79 |
I think I know what causes this issue, it's a side effect of the commit dcb4792 |
- META
OS: Windows Server 2012 R2
Selenium Standalone Server: 3.8.0
## Expected Behavior -
Appium server node should be present in the list of nodes with one Safari browser slot
## Actual Behavior -
Appium server node is present, but Safari slot is not available. Additional capabilities present in configuration.
## Steps to reproduce -
nodeconfig.json
node configuration (from hub console):
Please note, node works as expected with 3.7.1 standalone server.
The text was updated successfully, but these errors were encountered: