0

I'm trying to start a selenium webdriverinstance, but I get this error:

SessionNotCreatedError: session not created: This version of ChromeDriver only supports Chrome version 97 Current browser version is 100.0.4896.75 with binary path *path here*

I already tried using chromium 98, it works, but a new vulnerability was found in version 100 and i would like to update

jason karanik
  • 23
  • 1
  • 3

2 Answers2

1

Just in case if both Chrome browser version and ChromeDriver versions are in sync, then maybe you should look for the directory from where you project is invoking it, means there could some other directory from where ChromeDriver is being executed and whose version is incompatible with the browser.

In my case, my VS Code was picking up ChromeDriver from project's directory node_modules/.bin/ChromeDriver, so i replaced this with the latest and it worked.

Dharman
  • 26,923
  • 21
  • 73
  • 125
Karan Sharma
  • 35
  • 9
0

This error message...

SessionNotCreatedError: session not created: This version of ChromeDriver only supports Chrome version 97 Current browser version is 100.0.4896.75 with binary path...

...implies that the ChromeDriver was unable to initiate/spawn a new Browsing Context i.e. session.

Your main issue is the incompatibility between the version of the binaries you are using as follows:

  • You are using chrome=100.0.4896.75
  • You are using chromedriver=97.0
  • Release Notes of chromedriver=97.0 clearly mentions the following :

Supports Chrome version 97

So there is a clear mismatch between chromedriver=97.0 and the chrome=100.0.4896.75

Solution

Ensure that:

undetected Selenium
  • 151,581
  • 34
  • 225
  • 281
  • Thanks for this answer. As a sidenote, `Selenium Webdriver` truly is a nightmare to install and maintain. The fact that chromedriver only works with one version at a time and must constantly be kept in sync w/ Chrome's auto updates are just one of the reasons why this tech is 'advanced' as far as how difficult it is to maintain. On our team only one person's e2e tests run properly, due to webdriver install/versioning/dependency/OS/CPU issues (yes, all of those). As an Angular dev I'm glad Protractor is being deprecated and can't wait to jump to something like Cypress (does not use Webdriver). – Kyle Vassella May 11 '22 at 10:35