WebDriverManger Couldn't get actual chrome driver for Chrome for testing browser.

[hemanshurana]

WebDriverManger Couldn't get actual chrome driver for Chrome for testing browser.

[bonigarcia]

Using the latest WebDriverManager version (5.7.0 at the time of this writing) and clearing the cache (at least once) should fix this issue:

WebDriverManager.chromedriver().clearDriverCache().setup();

If not, please report your WebDriverManager traces. See: https://bonigarcia.dev/webdrivermanager/#troubleshooting

[tlpbu]

Hello!
I am using latest WebDriverManager version 5.8.0 and still have similar problem even with suggested fix.

org.openqa.selenium.SessionNotCreatedException: Could not start a new session. Response code 500. Message: session not created: This version of ChromeDriver only supports Chrome version 124
Current browser version is 123.0.6312.122 with binary path /Applications/Google Chrome for Testing.app/Contents/MacOS/Google Chrome for Testing 

After debugging if is clear version of ChromeDriver is detected based on ordinary Chrome version via shell command.

➜ /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version
Google Chrome 124.0.6367.61 

~ 
➜ /Applications/Google\ Chrome\ for\ Testing.app/Contents/MacOS/Google\ Chrome\ for\ Testing --version 
Google Chrome for Testing 123.0.6312.122 

As a result eventually always latest ChomeDriver is being used and it required manually updating Chrome for Testing but in this case it is even more tricky since there is not compatible version available on https://googlechromelabs.github.io/chrome-for-testing/ (only 123, 125, 126 versions available as of now).

Quick solution locally to unblock for me now is to specify WebDriverManager.chromedriver().browserVersion('123').setup().

Big question is if it is correct by nature to detect browser version for chromedriver based on ordinary Chrome if Chrome for Testing is installed on particular machine and will be automatically used for test execution?