Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Workaround for wrong chromedriver version

See original GitHub issue

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?

Issue Analytics

State:
Created 4 years ago
Reactions:12
Comments:27 (6 by maintainers)

Top GitHub Comments

3reactions

21stChannelcommented, Mar 27, 2019

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

2reactions

santiago-pancommented, Apr 25, 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