WebDriverManager.Net: [🐛 Bug]: WebDriverManager.Net not working with new chromedriver endpoints for Chrome since version 115
Problem
After updatating Chrome to version 115 the code below:
new DriverManager().SetUpDriver(new ChromeConfig(), VersionResolveStrategy.MatchingBrowser);
finishes with error:
System.Net.WebException
The remote server returned an error: (404) Not Found.
   at System.Net.HttpWebRequest.GetResponse()
   at WebDriverManager.DriverConfigs.Impl.ChromeConfig.GetLatestVersion(String url)
   at WebDriverManager.DriverConfigs.Impl.ChromeConfig.GetMatchingBrowserVersion()
   at WebDriverManager.DriverManager.GetVersionToDownload(IDriverConfig config, String version)
   at WebDriverManager.DriverManager.SetUpDriver(IDriverConfig config, String version, Architecture architecture)
Looks like there are changes for downloading chromedriver since v115 https://chromedriver.chromium.org/downloads “If you are using Chrome version 115 or newer, please consult the Chrome for Testing availability dashboard. This page provides convenient JSON endpoints for specific ChromeDriver version downloading.”
About this issue
- Original URL
- State: closed
- Created a year ago
- Reactions: 13
- Comments: 42 (4 by maintainers)
If you can (temporarily) live with the latest chrome version, just change the ResolveStrategy to ‘Latest’. Then it will works fine.
We temporarily patched our systems by adding an override for the
GetMatchingBrowserVersionwith a quick chrome 115 version check to redirect the URL.This workaround may help others so posting here
Hey everyone, this issue should get resolved once a version is released containing #254 FYI - I think there may be another addition to this change where we need to look at applying the
WithProxysettings to theChromeForTestingClient.@inflextion I have added a pull request now: #259
I use 2.17.1 and has the same problem after Chrome updated to 116. It works correctly before (115).
Probably, in the method
WithProxyof the classDriverManagernew you should set not only the default proxy ofWebRequestbut also ofHttpClient, because in the classChromeForTestingClientnew theHttpClientis used.If we set the default proxy of
HttpClient, the exception described above will no longer occur.[https://chromedriver.storage.googleapis.com/LATEST_RELEASE_115.0.5790]
Which returns
<Error>NoSuchKey<Message>The specified key does not exist.</Message>This is due to the changes that Google annoucned in May that would take effect with the 115 release and includes
Here are the new end points
@stevekiszow
We moved to selenium 4 ‘built-in’ driver manager. It also have some issues in our test runs, but we fixed it on our side
FYI there is also issue for that in selenium 4 ‘buil-in’ driver manager https://github.com/SeleniumHQ/selenium/pull/12208
Hi folks, do we have a time frame for this issue? Just seeing this today also and wondering if there is a work around?