Couldn't download latest 76 chrome driver, even if specify the version explicitly

[Abacist]

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

[Abacist]

It downloaded the 76.0.3809.12 version driver, and renamed it to 76.0.3809.68 version...

[abhinaba-ghosh]

I am also facing the same issue. Internally it reflects downgraded version.

chromedriver_76.0.3809.68.exe -v
ChromeDriver 76.0.3809.12 (220b19a666554bdcac56dff9ffd44c300842c933-refs/branch-heads/3809@{#83})

[sk13man]

Same issue

[pierre-hilt]

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]

please try to reinstall protractor 5.4.2:

npm install protractor@5.4.2 --save

[cnishina]

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]

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

Failed: javascript error: circular reference

which I assume was fixed in the ChromeDriver 76.0.3809.68
Do you have any ideas on how to fix it?

[abhinaba-ghosh]

@VadimSkuratovskyi

quick fix : install chromedriver through npm - v76.0.0

https://www.npmjs.com/package/chromedriver

[VadimSkuratovskyi]

@abhinaba1080 thank you, it's helped, but do you know, is there any fix planned?

[abhinaba-ghosh]

I dont have any idea on that. would be nice to have that in near future as i want my webdriver manager to handle drivers not the npm itself.

…

On Tue 13 Aug, 2019, 17:10 VadimSkuratovskyi, ***@***.***> wrote: @abhinaba1080 <https://github.com/abhinaba1080> thank you, it's helped, but do you know, is there any fix planned? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#408?email_source=notifications&email_token=AFQR3UT2ZHUFZTQS7NN4XBLQEKMTZA5CNFSM4IJTMRDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4FMQBQ#issuecomment-520800262>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFQR3UVF36MLLUGCZ7KIBY3QEKMTZANCNFSM4IJTMRDA> .

[TravkinAlex]

A really counter-intuitive error, investigation took quite some time. Would be great to get it fixed ASAP to avoid hacky workarounds.

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.

@pierre-hilt Could you please submit a PR with your fix, if possible?

[morozserg]

And when it will be released?

[TravkinAlex]

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.