Latest webdriver-manager is installing chromedriver 75 while the latest stable chrome is 74

[acuper]

I checked that wm 12.1.3 and 13.0.0 is now installing chromedriver 75 while the latest stable chrome is 74.
This leads to protractor error:
W/launcher - Ignoring uncaught error SessionNotCreatedError: session not created: This version of ChromeDriver only supports Chrome version 75

> webdriver-manager update

webdriver-manager: using local installed version 12.1.3
[11:51:56] I/file_manager - creating folder C:\WORK\Bmb\wkit\wkit-one-monorepo\packages\wkit-one-legale-ui\tests\e2e\node_modules\webdriver-manager\selenium
[11:51:56] I/config_source - curl -oC:\WORK\Bmb\wkit\wkit-one-monorepo\packages\wkit-one-legale-ui\tests\e2e\node_modules\webdriver-manager\selenium\standalone-response.xml https://selenium-release.storage.googleapis.com/
[11:51:56] I/config_source - curl -oC:\WORK\Bmb\wkit\wkit-one-monorepo\packages\wkit-one-legale-ui\tests\e2e\node_modules\webdriver-manager\selenium\chrome-response.xml https://chromedriver.storage.googleapis.com/
[11:51:56] I/config_source - curl -oC:\WORK\Bmb\wkit\wkit-one-monorepo\packages\wkit-one-legale-ui\tests\e2e\node_modules\webdriver-manager\selenium\gecko-response.json https://api.github.com/repos/mozilla/geckodriver/releases
[11:51:56] I/downloader - curl -oC:\WORK\Bmb\wkit\wkit-one-monorepo\packages\wkit-one-legale-ui\tests\e2e\node_modules\webdriver-manager\selenium/selenium-server-standalone-3.141.59.jar https://selenium-release.storage.googleapis.com/3.141/selenium-server-standalone-3.141.59.jar
[11:51:56] I/downloader - curl -oC:\WORK\Bmb\wkit\wkit-one-monorepo\packages\wkit-one-legale-ui\tests\e2e\node_modules\webdriver-manager\selenium/chromedriver_75.0.3770.8.zip https://chromedriver.storage.googleapis.com/75.0.3770.8/chromedriver_win32.zip
[11:51:57] I/update - chromedriver: unzipping chromedriver_75.0.3770.8.zip
[11:51:58] I/downloader - curl -oC:\WORK\Bmb\wkit\wkit-one-monorepo\packages\wkit-one-legale-ui\tests\e2e\node_modules\webdriver-manager\selenium/geckodriver-v0.24.0.zip https://github.com/mozilla/geckodriver/releases/download/v0.24.0/geckodriver-v0.24.0-win64.zip
[11:52:00] I/update - geckodriver: unzipping geckodriver-v0.24.0.zip

It's working fine with wm 12.1.1

[hadouke]

And it doesn't work, even when I've tried to install Chrome Canary (Version 76.0.3781.0 (Official Build) canary (64-bit)) for now.

[hadouke]

@acuper you can make it work with following (temporary solution for now):

• install chromedriver with npm install chromedriver
• go to folder you've installed chromedriver
• copy zip file
• go to webdriver-manager %USER%AppData\Roaming\npm\node_modules\webdriver-manager\selenium and paste it there
• rename copied archive from chromedriver_32 to chromedriver_75.0.3770.8
• also copy chromedriver.exe from downloaded zip to %USER%AppData\Roaming\npm\node_modules\webdriver-manager\selenium and rename it to chromedriver_75.0.3770.8.exe

[acuper]

Based on https://github.com/angular/webdriver-manager/blob/12.1.3/CHANGELOG.md
the suggested solution for the issue is to use --versions.chrome and indicate version matching your chrome version.

Based on http://chromedriver.chromium.org/downloads/version-selection we cannot expect that latest version will match latest stable chrome release ("Before a new major version of Chrome goes to Beta, a matching version of ChromeDriver will be released").

So maybe we need some automatic solution detecting the version of chrome and then downloading correct version of driver?

[jagdheesh-github]

steps to resolve this issue :
stop the selenium , or close that window.
1.open the folder where the drivers are placed : \AppData\Roaming\npm\node_modules\webdriver-manager\downloads
2.rename the "chromedriver_74.0.3729.6.exe " as plain ""chromedriver.exe".
3.place this "chromedriver.exe" into the zip file "chromedriver_win32.zip".
4.open the "chromedriver.config.json" file , change the "last" driver version to "74.0.3729.6" and save.
5.rename the "chromedriver_75.0.3770.8.exe" as "_chromedriver_75.0.3770.8.exe" to hide it.
6.now open a cmd window , enter the command "webdriver-manager start" , it will unzip the zip file and launch the chrome driver version 74. you can see the log messages
7. open another cmd window , and start your test suite. The issue must be resolved.

if you don't have previous stable version that matches with your chrome browser version , download it from below version. note : always update your chrome browser version from help section of the browser
https://chromedriver.storage.googleapis.com/index.html?path=74.0.3729.6/

[cnishina]

I have a fix! #380

[cnishina]

Also this is duplicate to #376, Closing this.

[amyboyd]

This is an alias to update webdriver-manager to a version that supports your installed version of Chrome. Should work on Mac:

chrome_version() {
    /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version | tr -d 'Google Chrome'
}

alias updateselenium='node_modules/webdriver-manager/bin/webdriver-manager update --versions.chrome=$(chrome_version)'

Use: updateselenium

[cnishina]

For Mac that might work. This would also have to work with Windows and Linux. Windows could have atypical paths to the binary.

[amyboyd]

@cnishina I get your point, but it's a comment on GitHub, it doesn't have to do anything.

[cnishina]

I see. I haven't had enough sleep so I misread that. 😴

Do you know if the Chrome and ChromeDriver versioning has the same number? Also, moving forward is it easier of --versions.chrome to just be the major chrome version. So possibly saying webdriver-manager update --versions.chrome 75?