webdriverio: Standalone server and point to a wrong path. Please set `path: '/wd/hub'` in your wdio.conf.js

Environment (please complete the following information):

  • WebdriverIO version: 6.1.20
  • Mode: [Standalone mode or WDIO Testrunner]
  • If WDIO Testrunner, running sync/async: sync
  • Node.js version: 12.16.1
  • NPM version: 6.13.4
  • Browser name and version: 83
  • Platform name and version: ubuntu 20.04LTS
  • Additional wdio packages used (if applicable):
    "@wdio/allure-reporter": "^6.1.14", "@wdio/appium-service": "^6.1.16", "@wdio/dot-reporter": "^6.1.14", "@wdio/local-runner": "^6.1.20", "@wdio/mocha-framework": "^6.1.19", "@wdio/selenium-standalone-service": "^6.1.14", "@wdio/spec-reporter": "^6.1.14", "@wdio/sync": "^6.1.14", "chai": "^4.2.0", "chromedriver": "^83.0.0", "wdio-chromedriver-service": "^6.0.3"

Config of WebdriverIO you can find it in the url provided below

Describe the bug Unable to trigger certain capabilities when using multi-remote feature as it seems ports are overlapping each other and throws an error as shown in the screenshot attached below

To Reproduce

  • Pull the code in the repo
  • git checkout to master (example branch is the default)
  • run ‘npm i’
  • run ‘npm run test’

https://github.com/Amrkamel1/wdExample/tree/master

Expected behavior I should be able to run certain capabilities separately

Log image

Additional context Add any other context about the problem here.

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 39 (39 by maintainers)

Most upvoted comments

@christian-bromann

Good news!! 😄 its working now with config below.

`  capabilities: {
myChromeBrowser: {
  port: 4444,
  path: '/wd/hub',
  capabilities: {
      browserName: 'chrome',
      acceptInsecureCerts: true
  }
},
androidClient: {
  port: 4728,
  path: '/',
  capabilities: {
    platformName: 'Android',
    browserName: 'chrome',
    'appium:deviceName': 'pixel2',
    'appium:avd': 'pixel2',
    'appium:platformVersion': '10',
    'appium:avdLaunchTimeout': 120000,
    'appium:avdReadyTimeout': 120000,
    'appium:uiautomator2ServerInstallTimeout' :120000,
    'appium:appWaitForLaunch': true,
    'appium:ensureWebviewsHavePages': true,
    'appium:disableWindowAnimation': true,
    'appium:autoGrantPermissions': true,
    'appium:clearSystemFiles': true,
    'appium:nativeWebScreenshot': true,
  }
  }
       },
        services: [
      ['selenium-standalone', {
         args: {
           seleniumArgs: ['-port', '4444']
         },
     }],  
     ['appium',{
       command : 'appium',
       args: {
           debugLogSpacing: true,
           sessionOverride: true,
           port: 4728,
       },
     }]
   ],`

note: I have upgraded all the json package to latest

2020-09-02_10h19_18

Yeah, this is a different story. Glad it works now.

Enjoy your vacation!

The test show a correct behavior.

That sounds great, i will try this caps that you have posted and let you know once i return back from vacation (next week) since i dont have access for any laptop now

@Amrkamel1 any help on this would be appreciated!

Is it correct that this is your intention to do so?

@hieuxlu yes. Users still can set the path properly in the config to run both services together. Unfortunately the selenium-standalone server requires the path to be on /wd/hub. Your suggestion should work. If you have a better solution how to handle this, please let us know. Cheers!

Hey, thanks for filing the issue. This seems indeed like bug. We would appreciate any help on this so please help us out! Have a look at our contributing guidelines and reach out if you have any questions. Cheers!