Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

webdriver-manager is not downloading latest 87.0.4280.88 chrome driver, even if specify the version explicitly #475

Open
code4muktesh opened this issue Dec 14, 2020 · 5 comments

Comments

@code4muktesh
Copy link

Using the below command to update the chrome driver with webdriver-manager 12.1.7
webdriver-manager update --version.chrome=87.0.4280.88

But, It is downloading the version 87.0.4280.20 as:
I/downloader - curl -o\node_modules\webdriver-manager\selenium/chromedriver_87.0.4280.88.zip https://chromedriver.storage.googleapis.com/87.0.4280.20/chromedriver_win32.zip

and renamed it to 87.0.4280.88.zip

Logs:
[15:35:15] I/config_source - curl -o\node_modules\webdriver-manager\selenium\standalone-response.xml https://selenium-release.storage.googleapis.com/
[15:35:15] I/config_source - curl -o\node_modules\webdriver-manager\selenium\chrome-response.xml https://chromedriver.storage.googleapis.com/
[15:35:16] I/downloader - curl -oE:\node_modules\webdriver-manager\selenium/chromedriver_87.0.4280.88.zip https://chromedriver.storage.googleapis.com/87.0.4280.20/chromedriver_win32.zip
[15:35:17] I/update - chromedriver: unzipping chromedriver_87.0.4280.88.zip

@alexkaufman06
Copy link

I'm also seeing issues when trying to use 87.0.4280.88
Here's the error I'm seeing after trying to start my tests with webdriver-manager:
08:00:44.910 ERROR [OsProcess.checkForError] - org.apache.commons.exec.ExecuteException: Execution failed (Exit value: -559038737. Caused by java.io.IOException: Cannot run program "/node_modules/webdriver-manager/selenium/chromedriver_87.0.4280.88" (in directory "."): error=86, Bad CPU type in executable)

@Andi-Lo
Copy link

Andi-Lo commented Feb 3, 2021

I think you have a typo in your command. I fell into the same trap.
This is wrong: --version.chrome xyz
This is right: --versions.chrome xyz
You're missing the s

@code4muktesh
Copy link
Author

I think you have a typo in your command. I fell into the same trap.
This is wrong: --version.chrome xyz
This is right: --versions.chrome xyz
You're missing the s

Tried as suggested but not working

@RockMinsk
Copy link

RockMinsk commented Feb 11, 2021

The same issue is for v.88 - sometimes downloaded --versions.chrome=88.0.4324.27 instead of --versions.chrome=88.0.4324.96 although it explicitly defined --versions.chrome=88.0.4324.96

Logs:

[23:28:12] webdriver-manager update --versions.standalone=3.14.0 --versions.chrome=88.0.4324.96
[23:28:13] I/downloader - curl -oC:\Teamcity\BuildAgent\work\3b8e448305e96a32\TestAutomation\node_modules\webdriver-manager\selenium/chromedriver_88.0.4324.96.zip https://chromedriver.storage.googleapis.com/88.0.4324.27/chromedriver_win32.zip
[23:28:14] I/update - chromedriver: unzipping chromedriver_88.0.4324.96.zip

NOTE: this issue leads then to failures in tests
Logs:

[23:28:30] W/launcher - Ignoring uncaught error WebDriverError: unknown error: Chrome failed to start: exited normally.
(unknown error: DevToolsActivePort file doesn't exist)
(The process started from chrome location C:\Program Files (x86)\Google\Chrome\Application\chrome.exe is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
(Driver info: chromedriver=88.0.4324.27 (6347fe8bf1e48bd0c54d07dc55ca011cf40861c9-refs/branch-heads/4324@{#450}),platform=Windows NT 10.0.14393 x86_64) (WARNING: The server did not provide any stacktrace information)

@CaptainGlac1er
Copy link

I think I fixed this in this commit #426

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants