webdriver-manager: Workaround for wrong chromedriver version

I noticed that when using the webdriver-manager update command it downloads the Chromedriver v74.x.x and it only runs with the Chrome v74, which I don’t have on my machine yet because the latest Chrome stable version is v73.

So, this stopped working…

Why this started to download and apply this chromedriver versions?

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 12
Comments: 27 (6 by maintainers)

Commits related to this issue

feat(max_versions): set max versions based on string matching - Do a version match based on string startsWith of the maxVersion An example: Matching "0.1" might find versions 0.14.0, 0.151.0, 0.... — committed to cnishina/webdriver-manager by cnishina 5 years ago
feat(max_versions): set max versions based on string matching - Do a version match based on string startsWith of the maxVersion An example: Matching "0.1" might find versions 0.14.0, 0.151.0, 0.... — committed to cnishina/webdriver-manager by cnishina 5 years ago
feat(max_versions): set max versions based on string matching - Do a version match based on string startsWith of the maxVersion An example: Matching "0.1" might find versions 0.14.0, 0.151.0, 0.... — committed to cnishina/webdriver-manager by cnishina 5 years ago
feat(max_versions): set max versions based on string matching - Do a version match based on string startsWith of the maxVersion An example: Matching "0.1" might find versions 0.14.0, 0.151.0, 0.... — committed to cnishina/webdriver-manager by cnishina 5 years ago
feat(max_versions): set max versions based on string matching - Do a version match based on string startsWith of the maxVersion An example: Matching "0.1" might find versions 0.14.0, 0.151.0, 0.... — committed to cnishina/webdriver-manager by cnishina 5 years ago
feat(max_versions): set max versions based on string matching - Do a version match based on string startsWith of the maxVersion An example: Matching "0.1" might find versions 0.14.0, 0.151.0, 0.... — committed to cnishina/webdriver-manager by cnishina 5 years ago
feat(max_versions): set max versions based on string matching - Do a version match based on string startsWith of the maxVersion An example: Matching "0.1" might find versions 0.14.0, 0.151.0, 0.... — committed to cnishina/webdriver-manager by cnishina 5 years ago
feat(max_versions): set max versions based on string matching (#369) - Do a version match based on string startsWith of the maxVersion An example: Matching "0.1" might find versions 0.14.0, 0... — committed to angular/webdriver-manager by cnishina 5 years ago

Most upvoted comments

Same issue here. I now force the job to use a static version (2.46) as workaround, but it’s not ideal.

21stChannel on Mar 27, 2019

Same here:

16:27:31] I/launcher - Running 1 instances of WebDriver
[16:27:31] I/local - Starting selenium standalone server...
[16:27:31] E/launcher - Error: Error: Server terminated early with status 1
    at earlyTermination.catch.e (/.../node_modules/selenium-webdriver/remote/index.js:252:52)
    at process._tickCallback (internal/process/next_tick.js:68:7)
[16:27:31] E/launcher - Process exited with error code 100

santiago-pan on Apr 25, 2019

@21stChannel Thanks for update, I was able to do the same ugly workaround to unblock my integration with Protractor 6.0:

webdriver-manager update --versions.chrome=2.46

rajarshi-singh on Mar 29, 2019