-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This version of ChromeDriver only supports Chrome version 114 #263
Comments
Are you using the latest 2.17.1? Are you calling the SetUpDriver method with the default VersionResolveStrategy.Latest? If so, I would suggest trying it with VersionResolveStrategy.MatcingBrowser. |
I am having the same issue. The latest version of WebDriverManager (2.17.1) is not working for me with Chrome 116. |
Try updating Selenium.WebDriver dependency to 4.11.0. It worked for me |
|
with latest version of both webdrivermanager 2.17.1 and webdriver version of 4.12.2 I am getting the same error |
Pretty sure that as of 2.17, the logic has been updated to use the new chrome-for-testing end point(s). Take a look at |
I am having the same issue on version 2.17.1 and chrome v116.0.5845.180. Here is the line that causes the exception |
I have managed to resolve this by using selenium manager (by Selenium) instead of webdrivermanager |
I am getting below mentioned error :
System.Exception : System.Exception::: System.IO.InvalidDataException ::: Unable to initialize driver for 'chrome' webbrowser! session not created: This version of ChromeDriver only supports Chrome version 114
Current browser version is 116.0.5845.111 with binary path C:\Program Files\Google\Chrome\Application\chrome.exe (SessionNotCreated) - Error occurred while trying to launch 'chrome'.
TearDown : System.Exception : System.NullReferenceException::: Object reference not set to an instance of an object. - Exception occurred while trying to take the screen-shot.
Line of code for which this error pops-up:
new WebDriverManager.DriverManager().SetUpDriver(new ChromeConfig(), VersionResolveStrategy.Latest);
The text was updated successfully, but these errors were encountered: