[🐛 Bug]: <Chrome 115 fix causes Mac OSX security Popup>

[Shiho240]

Have you read the Contributing Guidelines on issues?

• [X] I have read the Contributing Guidelines on issues.

WebdriverIO Version

8.14.2

Node.js Version

18.14.2

Mode

Standalone Mode

Which capabilities are you using?

No response

What happened?

With the change done in #10805 , chromedriver management was moved to wdio from selenium-standalone. This was due to Google changing how they managed the driver and chrome binaries. After updating to latest and attempting to run 115/latest locally, we run into a mac osx issue. Despite clicking allow, every time a test spec launches a Chrome browser instance, a pop-up will come up asking Do you want the application "Google Chrome for Testing.app" to accept incoming network communications. After allowing once, this has no impact on testing, as even if you ignore the window, testing will still occur. However it is a bit of an annoyance to have to close hundreds of popups when we run any suite with a large amount of test specs. I have checked that the Google Chrome for Testing application is greenlit in OSX's firewall, but other than that I'm unsure how to work around this.

What is your expected behavior?

Chrome browser should open normally without spamming the user with security popups

How to reproduce the bug.

You can run any example code that opens a chrome browser locally on a Mac OSX system. I have only tested against chrome 115

Relevant log output

N/A

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

Is there an existing issue for this?

• [X] I have searched the existing issues

[christian-bromann]

@Shiho240 thanks for reporting.

I can see this being annoying but I am not sure where this is coming from nor how to disable this. Any recommendation would be appreciated.

We greatly appreciate any contributions that help resolve the bug. While we understand that active contributors have their own priorities, we kindly request your assistance if you rely on this bug being fixed. We encourage you to take a look at our contribution guidelines or join our friendly Discord development server, where you can ask any questions you may have. Thank you for your support, and cheers!

[christian-bromann]

@Shiho240 I am not sure what has changed but I can't reproduce this anymore with latest WebdriverIO and Chrome. I will go ahead and close. Please verify this on your end. If it turns out to be still as posted above I am happy to re-open.

[thedaviddias]

I'm able to reproduce this same annoyance with the latest version of Chrome and webdriverio

[sadabnepal]

@christian-bromann this still is an issue. I am facing mostly when I clean my temp files, reboot system and then again run test which downloads browser and driver. Once you allow it works next time.

[wdio-bot]

Thanks for reporting!

We greatly appreciate any contributions that help resolve the bug. While we understand that active contributors have their own priorities, we kindly request your assistance if you rely on this bug being fixed. We encourage you to take a look at our contribution guidelines or join our friendly Discord development server, where you can ask any questions you may have. Thank you for your support, and cheers!