[🐛 Bug]: Unable to run tests on Firefox using Selenium Standalone Service · Issue #8282

link管理
链接快照平台
输入网页链接，自动生成快照
标签化管理网页链接
Have you read the Contributing Guidelines on issues?

I have read the Contributing Guidelines on issues .
WebdriverIO Version

7.19.6
Node.js Version

17.4.0
WDIO Testrunner
Which capabilities are you using?

browserName : 'firefox' ,
What happened?

When setting up new project using standalone service and setting up firefox as the browser, it's not running the tests. Keeps throwing the following error -
webdriver: Request timed out! Consider increasing the "connectionRetryTimeout" option
Dependencies:
    "devDependencies": {
        "@wdio/cli": "^7.19.6",
        "@wdio/local-runner": "^7.19.5",
        "@wdio/mocha-framework": "^7.19.5",
        "@wdio/selenium-standalone-service": "^7.19.5",
        "@wdio/spec-reporter": "^7.19.5"
What is your expected behavior?
Should be able to run tests on Firefox
How to reproduce the bug.
Setup a new project using the wdio cli and in service select selenium-standalone-service and update the capabilities to add browserName as firefox. Then, try running the project with npx wdio
   browserName: 'firefox',
Relevant log output
Execution of 1 workers started at 2022-04-28T17:00:49.658Z
2022-04-28T17:00:49.760Z INFO @wdio/cli:launcher: Run onPrepare hook
2022-04-28T17:00:56.931Z INFO @wdio/cli:launcher: Run onWorkerStart hook
2022-04-28T17:00:56.932Z INFO @wdio/local-runner: Start worker 0-0 with arg: 
[0-0] 2022-04-28T17:00:57.664Z INFO @wdio/local-runner: Run worker command: run
[0-0] RUNNING in firefox - /test/specs/example.e2e.js
[0-0] 2022-04-28T17:00:58.506Z INFO webdriver: Initiate new session using the WebDriver protocol
[0-0] 2022-04-28T17:00:58.510Z INFO webdriver: [POST] http://localhost:4444/wd/hub/session
[0-0] 2022-04-28T17:00:58.510Z INFO webdriver: DATA {
[0-0]   capabilities: { alwaysMatch: { browserName: 'firefox' }, firstMatch: [ {} ] },
[0-0]   desiredCapabilities: { browserName: 'firefox' }
[0-0] }
[0-0] 2022-04-28T17:02:58.536Z WARN webdriver: Request timed out! Consider increasing the "connectionRetryTimeout" option.
[0-0] 2022-04-28T17:02:58.537Z INFO webdriver: Retrying 1/3
[0-0] 2022-04-28T17:02:58.537Z INFO webdriver: [POST] http://localhost:4444/wd/hub/session
[0-0]




    
 2022-04-28T17:02:58.537Z INFO webdriver: DATA {
[0-0]   capabilities: { alwaysMatch: { browserName: 'firefox' }, firstMatch: [ {} ] },
[0-0]   desiredCapabilities: { browserName: 'firefox' }
[0-0] }
[0-0] 2022-04-28T17:04:58.543Z WARN webdriver: Request timed out! Consider increasing the "connectionRetryTimeout" option.
[0-0] 2022-04-28T17:04:58.544Z INFO webdriver: Retrying 2/3
[0-0] 2022-04-28T17:04:58.544Z INFO webdriver: [POST] http://localhost:4444/wd/hub/session
[0-0] 2022-04-28T17:04:58.544Z INFO webdriver: DATA {
[0-0]   capabilities: { alwaysMatch: { browserName: 'firefox' }, firstMatch: [ {} ] },
[0-0]   desiredCapabilities: { browserName: 'firefox' }
[0-0] }
[0-0] 2022-04-28T17:06:58.550Z WARN webdriver: Request timed out! Consider increasing the "connectionRetryTimeout" option.
[0-0] 2022-04-28T17:06:58.550Z INFO webdriver: Retrying 3/3
[0-0] 2022-04-28T17:06:58.551Z INFO webdriver: [POST] http://localhost:4444/wd/hub/session
[0-0] 2022-04-28T17:06:58.551Z INFO webdriver: DATA {
[0-0]   capabilities: { alwaysMatch: { browserName: 'firefox' }, firstMatch: [ {} ] },
[0-0]   desiredCapabilities: { browserName: 'firefox' }
[0-0] }
[0-0] 2022-04-28T17:08:58.536Z ERROR webdriver: Request failed with status undefined due to TimeoutError: Timeout awaiting 'request' for 120000ms when running "http://localhost:4444/wd/hub/session" with method "POST" and args "{"capabilities":{"alwaysMatch":{"browserName":"firefox"},"firstMatch":[{}]},"desiredCapabilities":{"browserName":"firefox"}}"
[0-0] 2022-04-28T17:08:58.537Z ERROR webdriver: TimeoutError: Timeout awaiting 'request' for 120000ms when running "http://localhost:4444/wd/hub/session" with method "POST" and args "{"capabilities":{"alwaysMatch":{"browserName":"firefox"},"firstMatch":[{}]},"desiredCapabilities":{"browserName":"firefox"}}"
[0-0]     at getTimeoutError (/Users/sam/Desktop/automation/wdio-standalone/node_modules/webdriver/build/utils.js:320:24)
[0-0]     at NodeJSRequest._request (/Users/sam/Desktop/automation/wdio-standalone/node_modules/webdriver/build/request/index.js:147:59)
[0-0]     at processTicksAndRejections (node:internal/process/task_queues:96:5)
[0-0]     at startWebDriverSession (/Users/sam/Desktop/automation/wdio-standalone/node_modules/webdriver/build/utils.js:67:20)
[0-0]     at Function.newSession (/Users/sam/Desktop/automation/wdio-standalone/node_modules/webdriver/build/index.js:46:45)
[0-0]     at remote (/Users/sam/Desktop/automation/wdio-standalone/node_modules/webdriverio/build/index.js:77:22)
[0-0]     at Runner._startSession (/Users/sam/Desktop/automation/wdio-standalone/node_modules/@wdio/runner/build/index.js:223:56)
[0-0]     at Runner._initSession (/Users/sam/Desktop/automation/wdio-standalone/node_modules/@wdio/runner/build/index.js:176:25)
[0




    
-0]     at Runner.run (/Users/sam/Desktop/automation/wdio-standalone/node_modules/@wdio/runner/build/index.js:88:19)
[0-0] 2022-04-28T17:08:58.543Z ERROR @wdio/runner: Error: Failed to create session.
[0-0] Timeout awaiting 'request' for 120000ms when running "http://localhost:4444/wd/hub/session" with method "POST" and args "{"capabilities":{"alwaysMatch":{"browserName":"firefox"},"firstMatch":[{}]},"desiredCapabilities":{"browserName":"firefox"}}"
[0-0]     at startWebDriverSession (/Users/sam/Desktop/automation/wdio-standalone/node_modules/webdriver/build/utils.js:72:15)
[0-0]     at processTicksAndRejections (node:internal/process/task_queues:96:5)
[0-0]     at Function.newSession (/Users/sam/Desktop/automation/wdio-standalone/node_modules/webdriver/build/index.js:46:45)
[0-0]     at remote (/Users/sam/Desktop/automation/wdio-standalone/node_modules/webdriverio/build/index.js:77:22)
[0-0]     at Runner._startSession (/Users/sam/Desktop/automation/wdio-standalone/node_modules/@wdio/runner/build/index.js:223:56)
[0-0]     at Runner._initSession (/Users/sam/Desktop/automation/wdio-standalone/node_modules/@wdio/runner/build/index.js:176:25)
[0-0]     at Runner.run (/Users/sam/Desktop/automation/wdio-standalone/node_modules/@wdio/runner/build/index.js:88:19)
[0-0] FAILED in firefox - /test/specs/example.e2e.js
2022-04-28T17:08:58.671Z INFO @wdio/cli:launcher: Run onWorkerEnd hook
2022-04-28T17:08:58.674Z INFO @wdio/cli:launcher: Run onComplete hook
2022-04-28T17:08:58.675Z INFO @wdio/selenium-standalone-service: shutting down all browsers
Spec Files:      0 passed, 1 failed, 1 total (100% completed) in 00:08:09 
2022-04-28T17:08:58.676Z INFO @wdio/local-runner: Shutting down spawned worker
2022-04-28T17:08:58.933Z INFO @wdio/local-runner: Waiting for 0 to shut down gracefully
2022-04-28T17:08:58.933Z INFO @wdio/local-runner: shutting down
Code of Conduct
 I agree to follow this project's Code of Conduct
Is there an existing issue for this?
 I have searched the existing issues
          I am having this same issue with selenium-standalone-service for both firefox and chrome. The browsers do not even open.
My setup

MacOS Monterey 12.3.1

Chrome Version 101.0.4951.41
Using this configuration from wdio tutorial also hits the issue
? Where is your automation backend located? On my local machine
? Which framework do you want to use? jasmine
? Do you want to use a compiler? No!
? Where are your test specs located? ./test/specs/**/*.js
? Do you want WebdriverIO to autogenerate some test files? Yes
? Do you want to use page objects (https://martinfowler.com/bliki/PageObject.html)? No
? Which reporter do you want to use? dot
? Do you want to add a plugin to your test setup? 
? Do you want to add a service to your test setup? selenium-standalone
? What is the base url? http://localhost
? Do you want me to run `npm install` Yes
The run output:
npx wdio run wdio.conf.js
Execution of 1 workers started at 2022-04-29T16:23:23.171Z
2022-04-29T16:23:23.256Z INFO @wdio/cli:launcher: Run onPrepare hook
2022-04-29T16:23:28.071Z INFO @wdio/cli:launcher: Run onWorkerStart hook
2022-04-29T16:23:28.073Z INFO @wdio/local-runner: Start worker 0-0 with arg: run,wdio.conf.js
[0-0] 2022-04-29T16:23:28.623Z INFO @wdio/local-runner: Run worker command: run
[0-0] RUNNING in chrome - /test/specs/example.e2e.js
[0-0] 2022-04-29T16:23:28.850Z INFO webdriver: Initiate new session using the WebDriver protocol
[0-0] 2022-04-29T16:23:28.855Z INFO webdriver: [POST] http://localhost:4444/wd/hub/session
[0-0] 2022-04-29T16:23:28.855Z INFO webdriver: DATA {
[0-0]   capabilities: {
[0-0]     alwaysMatch: { browserName: 'chrome', acceptInsecureCerts: true },
[0-0]     firstMatch: [ {} ]
[0-0]   },
[0-0]   desiredCapabilities: { browserName: 'chrome', acceptInsecureCerts: true }
[0-0] }
[0-0] 2022-04-29T16:25:28.877Z WARN webdriver: Request timed out! Consider increasing the "connectionRetryTimeout" option.
Additional notes:
WORKS with chromedriver instead of selenium-standalone, I haven't tried geckodriver.
Also does NOT work in an ubuntu container that I use to run tests.
          Seeing a similar issue trying local muti-remote with selenium standalone and firefox:
ERROR webdriver: WebDriver Error: Could not start a new session. Error while creating session with the driver service. Stopping driver service: Could not start a new session. Response code 400. Message: Argument --remote-debugging-port can't be set via capabilities
Build info: version: '4.0.0', revision: '3a21814679'
the error appears to be coming from webdriver and the driver version for geckodriver?
Driver info: driver.version: unknown
    at getErrorFromResponseBody (/Users/pmerwin/Projects/Adept/lib-webdriver.io/node_modules/webdriver/build/utils.js:197:12)
    at NodeJSRequest._request (/Users/pmerwin/Projects/Adept/lib-webdriver.io/node_modules/webdriver/build/request/index.js:158:60)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at startWebDriverSession (/Users/pmerwin/Projects/Adept/lib-webdriver.io/node_modules/webdriver/build/utils.js:67:20)
    at Function.newSession (/Users/pmerwin/Projects/Adept/lib-webdriver.io/node_modules/webdriver/build/index.js:46:45)
    at remote (/Users/pmerwin/Projects/Adept/lib-webdriver.io/node_modules/webdriverio/build/index.js:77:22)
    at /Users/pmerwin/Projects/Adept/lib-webdriver.io/node_modules/webdriverio/build/index.js:139:26
    at async Promise.all (index 0)
          So, I bumped the geckodriver version to 31, the latest, and I am running the latest ff locally with the 4.0 selenium standalone release on one firefox browser, what I am seeing is selenium standalone service logs never start, and there is no geckodriver in node_modules ?
is the issue that sel-standlone is not downloading / starting geckodriver?
2022-04-29T17:51:11.010Z ERROR webdriver: TimeoutError: Timeout awaiting 'request' for 90000ms when running "http://localhost:4444/wd/hub/session" with method "POST" and args "{"capabilities":{"alwaysMatch":{"browserName":"firefox"},"firstMatch":[{}]},"desiredCapabilities":{"browserName":"firefox"}}"
https://gist.github.com/pmerwin/d028eac552c9b76ba0d27e6447f36584
          as a workaround I found geckodriver service is working fine for me for single browser tests ( has issues with multi remote):
https://www.npmjs.com/package/wdio-geckodriver-service
  "runner": "local",
  "services": [
      "geckodriver",
        "args": [
          "--log=info"
        "logs": "./data/gecko.log"
  "specs": [
    "./test/learn-webapp/skill-video/specs/skill.edit.existing.spec.js"
  "exclude": [],
  "capabilities": [
      "browserName": "firefox"
          I believe there is some mismatch between geckodriver and firefox. As you can see here geckodriver 0.31 cannot work with FF 90.
I configured wdio to use 0.30 like this and this unblocked me for some time. Probably until FF 91 is publicly available.
          @propheel does your pr fix problem for chrome driver also? In current version of wdio-selenium-standalone-service chrome also can't start and also I find out one strange thing about download url when 'installArgs' are exists in the wdio.config.
wdio.conf example (to be more clear):

    services: [ ['selenium-standalone', { logPath: './temp', installArgs: { version: "3.9.1", baseURL: "https://selenium-release.storage.googleapis.com", drivers: { chrome: { version: "102.0.5005.27", arch: process.arch, baseURL: "https://chromedriver.storage.googleapis.com" } } }, }] ],
actual ink -       'https://selenium-release.storage.googleapis.com/selenium-3.9.1/selenium-server-standalone-3.9.1.jar'

expected link - 'https://selenium-release.storage.googleapis.com/3.9/selenium-server-standalone-3.9.1.jar'
I believe there is some mismatch between geckodriver and firefox. As you can see here geckodriver 0.31 cannot work with FF 90.
I configured wdio to use 0.30 like this and this unblocked me for some time. Probably until FF 91 is publicly available.
I am doing this:
"services": [
      "selenium-standalone",
        "drivers": {
          "firefox": {
            "version": "0.30.0"
using ff 99.01

and these versions
"devDependencies": {
  "@wdio/dot-reporter": "7.19.5",
  "@wdio/firefox-profile-service": "7.19.5",
  "@wdio/selenium-standalone-service": "7.19.5",
  "@wdio/spec-reporter": "7.19.5",
  "chromedriver": "^101.0.0",
  "eslint": "^8.14.0",
  "eslint-config-cbtnuggets": "^8.2.2"
"dependencies": {
  "16": "0.0.2",
  "@axe-core/webdriverio": "^4.4.2",
  "@babel/cli": "^7.17.10",
  "@babel/core": "^7.17.10",
  "@babel/preset-env": "^7.17.10",
  "@babel/register": "^7.17.7",
  "@slack/webhook": "^6.1.0",
  "@wdio/cli": "7.19.6",
  "@wdio/devtools-service": "7.19.6",
  "@wdio/local-runner": "7.19.5",
  "@wdio/logger": "7.19.0",
  "@wdio/mocha-framework": "7.19.5",
  "@wdio/sauce-service": "7.19.5",
  "@wdio/sync": "7.19.5",
  "async": "^3.2.3",
  "async-prompt": "^1.0.1",
  "commander": "9.2.0",
  "csv-stringify": "^6.0.5",
  "devtools": "7.19.5",
  "dogapi": "^2.8.4",
  "expect": "^28.0.2",
  "expect-webdriverio": "^3.3.1",
  "fs-extra": "^10.1.0",
  "lodash": "^4.17.21",
  "mailosaur": "^8.2.0",
  "moment": "^2.29.3",
  "moment-timezone": "^0.5.34",
  "path": "^0.12.7",
  "q": "^1.5.1",
  "random-email": "^1.0.3",
  "random-name": "^0.1.2",
  "sauce-connect-launcher": "1.3.2",
  "superagent": "^7.1.3",
  "wdio-electron-service": "^3.0.1",
  "wdio-intercept-service": "4.2.2",
  "wdio-json-reporter": "3.0.0",
  "webdriverio": "7.19.5"
and firefox will not run locally for me, same error:




    

there are no logs generated for in wdio-selenium-standalone log, I am not sure the service is even running, so nothing has been "fixed" here.
2022-05-02T15:29:45.585Z INFO webdriver: DATA {
  capabilities: { alwaysMatch: { browserName: 'firefox' }, firstMatch: [ {} ] },
  desiredCapabilities: { browserName: 'firefox' }
2022-05-02T15:31:15.593Z ERROR webdriver: Request failed with status undefined due to TimeoutError: Timeout awaiting 'request' for 90000ms when running "http://localhost:4444/wd/hub/session" with method "POST" and args "{"capabilities":{"alwaysMatch":{"browserName":"firefox"},"firstMatch":[{}]},"desiredCapabilities":{"browserName":"firefox"}}"
2022-05-02T15:31:15.593Z ERROR webdriver: TimeoutError: Timeout awaiting 'request' for 90000ms when running "http://localhost:4444/wd/hub/session" with method "POST" and args "{"capabilities":{"alwaysMatch":{"browserName":"firefox"},"firstMatch":[{}]},"desiredCapabilities":{"browserName":"firefox"}}"
    at getTimeoutError (/Users/pmerwin/Projects/Adept/lib-webdriver.io/node_modules/webdriver/build/utils.js:320:24)
    at NodeJSRequest._request (/Users/pmerwin/Projects/Adept/lib-webdriver.io/node_modules/webdriver/build/request/index.js:147:59)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at startWebDriverSession (/Users/pmerwin/Projects/Adept/lib-webdriver.io/node_modules/webdriver/build/utils.js:67:20)
    at Function.newSession (/Users/pmerwin/Projects/Adept/lib-webdriver.io/node_modules/webdriver/build/index.js:46:45)
    at remote (/Users/pmerwin/Projects/Adept/lib-webdriver.io/node_modules/webdriverio/build/index.js:77:22)
    at Runner._startSession (/Users/pmerwin/Projects/Adept/lib-webdriver.io/node_modules/@wdio/runner/build/index.js:223:56)
    at Runner._initSession (/Users/pmerwin/Projects/Adept/lib-webdriver.io/node_modules/@wdio/runner/build/index.js:176:25)
    at Runner.run (/Users/pmerwin/Projects/Adept/lib-webdriver.io/node_modules/@wdio/runner/build/index.js:88:19)
2022-05-02T15:31:15.596Z ERROR @wdio/runner: Error: Failed to create session.
Timeout awaiting 'request' for 90000ms when running "http://localhost:4444/wd/hub/session" with method "POST" and args "{"capabilities":{"alwaysMatch":{"browserName":"firefox"},"firstMatch":[{}]},"desiredCapabilities":{"browserName":"firefox"}}"
    at startWebDriverSession (/Users/pmerwin/Projects/Adept/lib-webdriver.io/node_modules/webdriver/build/utils.js:72:15)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at Function.newSession (/Users/pmerwin/Projects/Adept/lib-webdriver.io/node_modules/webdriver/build/index.js:46:45)
    at remote (/Users/pmerwin/Projects/Adept/lib-webdriver.io/node_modules/webdriverio/build/index.js:77:22)
    at Runner._startSession (/Users/pmerwin/Projects/Adept/lib-webdriver.io/node_modules/@wdio/runner/build/index.js:223:56)
    at Runner._initSession (/Users/pmerwin/Projects/Adept/lib-webdriver.io/node_modules/@wdio/runner/build/index.js:176:25)
    at Runner.run (/Users/pmerwin/Projects/Adept/lib-webdriver.io/node_modules/@wdio/runner/build/index.js:88:19)
@propheel - Thank you!! When can we expect this be merged?
I'm not the author of the repo, I don't know how to fix this, I just noticed geckodriver 0.30 works for me 😉
@propheel does your pr fix problem for chrome driver also? In current version of wdio-selenium-standalone-service chrome also can't start and also I find out one strange thing about download url when 'installArgs' are exists in the wdio.config.
No idea, I was just fixing Firefox on my end.
I am doing this:
"services": [
      "selenium-standalone",
        "drivers": {
          "firefox": {
            "version": "0.30.0"
I believe it should look more like this:
"services": [
      "selenium-standalone",
        "drivers": {
          "firefox": "0.30.0"
          Running since Friday into the same issue with Chrome. (Version 101).

Error Log:

webdriver: Request failed with status undefined due to TimeoutError: Timeout awaiting 'request' for 90000ms when running "http://localhost:4444/wd/hub/session" with method "POST" and args "{"capabilities":{"alwaysMatch":{"browserName":"chrome","goog:chromeOptions":{}},"firstMatch":[{}]},"desiredCapabilities":{"browserName":"chrome","goog:chromeOptions":{}}}"
[0-0] 2022-05-03T12:32:03.910Z ERROR webdriver: TimeoutError: Timeout awaiting 'request' for 90000ms when running "http://localhost:4444/wd/hub/session" with method "POST" and args "{"capabilities":{"alwaysMatch":{"browserName":"chrome","goog:chromeOptions":{}},"firstMatch":[{}]},"desiredCapabilities":{"browserName":"chrome","goog:chromeOptions":{}}}"
          seeing this on saucelabs now, unable to run firefox over saucelabs:
@christian-bromann is ff working on saucelabs for you?
2022-05-03T15:17:32.910Z ERROR webdriver: Request failed with status undefined due to TimeoutError: Timeout awaiting 'request' for 9000ms when running "https://ondemand.us-west-1.saucelabs.com/wd/hub/session" with method "POST" and args "{"capabilities":{"alwaysMatch":{"browserName":"firefox","browserVersion":"latest","platformName":"Windows 10","sauce:options":{"username":"adept-poc","accessKey":"REMOVED","
# switched to selenium-standalone service in service section
$ cd 8282
# updated capabilities to run Firefox
$ npx wdio
# all tests pass

Also adding user and key to the setup and run these tests on Sauce Labs worked fine. The webdriverio packages I've been using:
"@wdio/cli": "^7.19.7",
"@wdio/local-runner": "^7.19.7",
"@wdio/mocha-framework": "^7.19.7",
"@wdio/selenium-standalone-service": "^7.19.5",
"@wdio/spec-reporter": "^7.19.7"
# all tests pass
Also adding user and key to the setup and run these tests on Sauce Labs worked fine. The webdriverio packages I've been using:
"@wdio/cli": "^7.19.7",
"@wdio/local-runner": "^7.19.7",
"@wdio/mocha-framework": "^7.19.7",
"@wdio/selenium-standalone-service": "^7.19.5",
"@wdio/spec-reporter": "^7.19.7"
What node version did you use? I am having similar issues using node 16.15.0 but with jasmine framework instead of mocha. Potentially related to node version?
npm init wdio . (cucumber + selenium standalone)
Changed capabilities

    capabilities: [{ maxInstances: 5, browserName: 'firefox', acceptInsecureCerts: true }],
npm run wdio
Attaching logs (logs.txt)
Version of npm & node

Unfortunately I wasn't able to reproduce it on my Mac M1 machine.
Like @MadSandwich I try to run it on Windows 11.

If I remember right, my college has no problems. She is also running the project on Mac.
          full review of my setup in case it helps. unfortunately, i cannot give an example from what i am working on as it is proprietary however i will try to setup something later that is not.
MBP (Mid 2015)

macOS 12.3.1

node 16.15.0

npm 8.5.5
package.json:

"@wdio/cli": "~7.19.6",

"@wdio/dot-reporter": "~7.19.5",

"@wdio/jasmine-framework": "~7.19.5",

"@wdio/local-runner": "~7.19.5",

"@wdio/sauce-service": "~7.19.5",

"@wdio/selenium-standalone-service": "~7.19.5",

"@wdio/spec-reporter": "~7.19.5",
package-lock.json versions:

"@wdio/cli": "7.19.6",

"@wdio/dot-reporter": "7.19.5",

"@wdio/jasmine-framework": "7.19.5",

"@wdio/local-runner": "7.19.5",

"@wdio/sauce-service": "7.19.5",

"@wdio/selenium-standalone-service": "7.19.5",

"@wdio/spec-reporter": "7.19.5",
assuming there are a couple of packages in there that are not directly related but thought i would just add what i have. i will try to update those patch versions to see if that makes a difference
          Oh jeez.... so as a workaround I had just installed the geckodriver service and the chromedriver service. after seeing the patch updates above, i updated my versions and removed those services:
"@wdio/appium-service": "~7.19.5",
"@wdio/cli": "~7.19.7",
"@wdio/dot-reporter": "~7.19.7",
"@wdio/jasmine-framework": "~7.19.7",
"@wdio/local-runner": "~7.19.7",
"@wdio/sauce-service": "~7.19.7",
"@wdio/selenium-standalone-service": "~7.19.5",
"@wdio/spec-reporter": "~7.19.7",
this seems to be functioning as expected. not 100% sure what is the reason for it working now, especially since "@wdio/selenium-standalone-service" version is the same. 😬
          yep works for me too now lol. no further changes made since.
dep versions
    "@wdio/allure-reporter": "^7.19.5",
    "@wdio/browserstack-service": "^7.19.5",
    "@wdio/cli": "^7.19.5",
    "@wdio/local-runner": "^7.19.5",
    "@wdio/logger": "^7.19.0",
    "@wdio/mocha-framework": "^7.19.5",
    "@wdio/selenium-standalone-service": "^7.19.5",
    "@wdio/spec-reporter": "^7.19.5",
on macOS 12.3.1 2019 pro but also on CI in a container based off selenium/standalone-chrome:101.0.

using node v14.18.0 / npm 6.14.15
          it is sadly not running on my maschine with chrome. I'm using now this package-versions:
"@wdio/allure-reporter": "7.19.7",

"@wdio/cli": "7.19.7"

"@wdio/firefox-profile-service": "7.19.5",

"@wdio/local-runner": "7.19.7",

"@wdio/mocha-framework": "7.19.7",

"@wdio/selenium-standalone-service": "7.19.5",

"@wdio/spec-reporter": "7.19.7",
Chrome is on version 101

Firefox is on version 99

NPM is on version 8.4.1

Node is on version 16.15.0
I'm using Windows 11 and it has also no updates to install.
          Got a Windows update today, except for this I changed nothing on the project or the drivers.

But it is running again! 🙌  So thanks from my side for all your work and help!

Hopefully, we will not write again so soon! 😁

Jan from Germany 😄