[🐛 Bug]: BiDi URL IP 4/6 resolution issue #14039
Description
Have you read the Contributing Guidelines on issues?
- I have read the Contributing Guidelines on issues.
WebdriverIO Version
latest
Node.js Version
22
Mode
Standalone Mode
Which capabilities are you using?
{"capabilities":{"acceptInsecureCerts":false,"browserName":"chrome","browserVersion":"131.0.6778.140","chrome":{"chromedriverVersion":"131.0.6778.108 (3b014839fbc4fb688b2f5af512d6ce312ad208b1-refs/branch-heads/6778@{#2393})","userDataDir":"C:\\Windows\\SystemTemp\\scoped_dir3608_1127547173"},"fedcm:accounts":true,"goog:chromeOptions":{"debuggerAddress":"localhost:55664"},"networkConnectionEnabled":false,"pageLoadStrategy":"normal","platformName":"windows","proxy":{},"setWindowRect":true,"strictFileInteractability":false,"timeouts":{"implicit":0,"pageLoad":300000,"script":30000},"unhandledPromptBehavior":"ignore","webSocketUrl":"ws://fv-az1760-623:4780/bidi/d5116166-770a-46f0-a4f9-c3d744df3237","webauthn:extension:credBlob":true,"webauthn:extension:largeBlob":true,"webauthn:extension:minPinLength":true,"webauthn:extension:prf":true,"webauthn:virtualAuthenticators":true}}What happened?
Check failed tests in https://github.com/appium/appium-chromium-driver/actions/runs/12668118313/job/35302892004?pr=380
When BiDi URL returned by the server contains a hostname (ws://fv-az1760-623:4780/bidi/d5116166-770a-46f0-a4f9-c3d744df3237), which could be resolved in both ip4 and ip6 addresses, WDIO only tries one of them (ipv6) and fails instead of trying both.
What is your expected behavior?
WDIO should fallback to ipv4 resolution if it fails to reach the web socket using ipv6
How to reproduce the bug.
Run tests from appium/appium-chromium-driver#380
Relevant log output
https://github.com/appium/appium-chromium-driver/actions/runs/12668118313/job/35302892004?pr=380Code 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