Repository navigation
Couldn't download latest 76 chrome driver, even if specify the version explicitly #408
Description
webdriver-manager version: 12.1.6
introduced by Protractor 5.4.2
The latest ChromeDriver version is 76.0.3809.68 according to https://chromedriver.chromium.org/downloads
It fixed a bug in detecting circular reference in JavaScript objects, which exists in 76.0.3809.25 and 76.0.3809.12.
But webdriver-manager update couldn't download it.
=============================================
Logs:
D:\Test\node_modules.bin>webdriver-manager update --versions.chrome 76.0.3809.68
[15:35:11] I/downloader - curl -oD:\Test\node_modules\protractor\node_modules\webdriver-manager\selenium/chromedriver_76.0.3809.68.zip https://chromedriver.storage.googleapis.com/76.0.3809.12/chromedriver_win32.zip
[15:35:12] I/update - selenium standalone: file exists D:\Test\node_modules\protractor\node_modules\webdriver-manager\selenium\selenium-server-standalone-3.141.59.jar
[15:35:12] I/update - selenium standalone: selenium-server-standalone-3.141.59.jar up to date
[15:35:12] I/update - chromedriver: unzipping chromedriver_76.0.3809.68.zip
[15:35:13] I/update - geckodriver: file exists D:\Test\node_modules\protractor\node_modules\webdriver-manager\selenium\geckodriver-v0.24.0.zip
[15:35:13] I/update - geckodriver: unzipping geckodriver-v0.24.0.zip
[15:35:13] I/update - geckodriver: geckodriver-v0.24.0.exe up to date
Activity
Abacist commentedon Aug 6, 2019
It downloaded the 76.0.3809.12 version driver, and renamed it to 76.0.3809.68 version...
abhinaba-ghosh commentedon Aug 6, 2019
I am also facing the same issue. Internally it reflects downgraded version.
sk13man commentedon Aug 6, 2019
Same issue
pierre-hilt commentedon Aug 6, 2019
Hello,
I had a look at the issue and did a fix if you are interested: pierre-hilt@f8cb4e2
On the logic to get the right chromedriver to download, the patch version was removed (because 76.0.3809.68 is not a valid semver), and so 76.0.3809(.12) is equal to 76.0.3809(.68).
sergss commentedon Aug 12, 2019
please try to reinstall protractor 5.4.2:
cnishina commentedon Aug 12, 2019
This unfortunately has to do with the logic there to only look at the first 3 numbers for semver for ChromeDriver. We will fix it but probably not for the legacy branch of webdriver-manager. You could also call
webdriver-manager update --versions.chrome 76.0.3809.68.If you feel like this is something that should be fixed right now, feel free to put in a PR. I'll happily review it. Thanks!
VadimSkuratovskyi commentedon Aug 13, 2019
Hello,
Faced with the same issue, trying to install chromeDriver --versions.chrome 76.0.3809.68 but downloaded --versions.chrome 76.0.3809.12
(\node_modules\protractor\node_modules\webdriver-manager\selenium/chromedriver_76.0.3809.68.zip https://chromedriver.storage.googleapis.com/76.0.3809.12/chromedriver_win32.zip)and then when I try to run tests I receiving an error
which I assume was fixed in the ChromeDriver 76.0.3809.68
Do you have any ideas on how to fix it?
abhinaba-ghosh commentedon Aug 13, 2019
@VadimSkuratovskyi
quick fix : install chromedriver through npm - v76.0.0
https://www.npmjs.com/package/chromedriver
VadimSkuratovskyi commentedon Aug 13, 2019
@abhinaba1080 thank you, it's helped, but do you know, is there any fix planned?
abhinaba-ghosh commentedon Aug 13, 2019
TravkinAlex commentedon Aug 14, 2019
A really counter-intuitive error, investigation took quite some time. Would be great to get it fixed ASAP to avoid hacky workarounds.
@pierre-hilt Could you please submit a PR with your fix, if possible?
morozserg commentedon Aug 19, 2019
And when it will be released?
TravkinAlex commentedon Aug 19, 2019
Would be nice for this to get more attention, I'm sure a lot of people ran into this problem after upgrading to Chrome 76.
shaileshsharma786 commentedon Aug 19, 2019
It worked for me. After reinstall protractor I used ng e2e and it automatically downloads latest chormedriver 76.#.###.# version
vaindil commentedon Sep 5, 2019
Installing
chromedrivermanually didn't fix anything for me, the old version is still used. I had to manually get thechromedriverexe, rename it to have the old version number, and replace the one the package downloaded. No other method worked for me.cnishina commentedon Sep 16, 2019
Please try 12.1.7. This downloads always the LATEST_RELEASE from chromedriver. This hopefully matches up better with Chrome releases.
If you are having issues with getting the latest:
I would make sure to clean up node_modules before installing. Potentially the version of webdriver-manager satisfies the protractor version number even though there is a newer version available. So it helps to delete the node_modules folder or doing an npm install -f (to force install).
Also this is fixed with 64795b7
TravkinAlex commentedon Sep 17, 2019
While getting the latest chromedriver
may have been fixed, getting the specific version still ignores patch number (as discussed here). I'll create a separate issue and update my PR #413 .EDIT: Actually, getting the latest version still uses
getSpecificChromeDriverVersion, so with webdriver-manager 12.1.7 still not the latest chromedriver version gets downloaded, because the patch version is ignored!@cnishina This issue should be reopened, as the problem described has not been fixed.