For MacOS chromedriver upgrade did the trick:
brew upgrade --cask chromedriver
ID : 20013
viewed : 39
Tags : rseleniumgoogle-chromeselenium-chromedriverrseleniumr
94
For MacOS chromedriver upgrade did the trick:
brew upgrade --cask chromedriver
90
This error message...
Selenium message:session not created: This version of ChromeDriver only supports Chrome version 74 (Driver info: chromedriver=74.0.3729.6 (255758eccf3d244491b8a1317aa76e1ce10d57e9-refs/branch-heads/3729@{#29}),platform=Mac OS X 10.14.3 x86_64)
...implies that the ChromeDriver expects the Chrome Browser version to be 74.
To install the latest version of ChromeDriver you can use:
brew tap homebrew/cask && brew cask install chromedriver
sudo apt-get install chromium-chromedriver
choco install chromedriver
Your main issue is the incompatibility between the version of the binaries you are using as follows:
Supports Chrome v74
So there is a clear mismatch between the ChromeDriver v74.0.3729.6 and the Chrome Browser v73.0
@Test
.driver.quit()
within tearDown(){}
method to close & destroy the WebDriver and Web Client instances gracefully.You can find a relevant detailed discussion in:
77
I encountered the same issue today and found this post and others from Google. I think I may have a more direct solution as a modification of your code. The previous answer is correct in identifying the mismatch in versions.
I tried the proposed solutions to no avail. I found that the versions were correct on my computer. However, this mismatch error was not resulting from the actual versions installed on the computer, but rather the RSelenium code is seeking the "latest" version of Chrome/ChromeDriver by default argument. See ?rsDriver()
help page for the arguments.
If you run the code binman::list_versions("chromedriver")
as specified in the help documentation, then you can identify the versions of compatible with the function. In my case, I was able to use the following code to establish a connection.
driver <- rsDriver(browser=c("chrome"), chromever="73.0.3683.68", extraCapabilities = eCaps)
You should be able to specify your version of Chrome with the chromever=
argument. I had to use the closest version, though (my chrome version was "73.0.3683.75").
Hope this helps!
70
Updating the Google Chrome version to 74 worked for me.
Steps: 1. Go to Help -> About Google Chrome -> Chrome will automatically look for updates(update Chrome to the latest version)
51
I had to reinstall protractor for it to pull the updated webdriver-manager
module. Also, per @Mark’s comment, the package-lock.json
may be locking the dependency.
npm uninstall protractor npm install --save-dev protractor
Then, make sure to check the maxChromedriver
value in node_modules/protractor/node_modules/webdriver-manager/config.json
after re-install to verify it matches the desired Chrome driver version.