webdriver-manager update downloads an incompatible version of chromedriver #376
Comments
|
Update protractor/webdriver-manager to the latest version. |
|
I'll have a hot fix out in the next few days for this. Latest webdriver-manager does work BUT:
|
|
Here is the proposed fix: #377 Neat that my few days estimate is actually 30 minutes. |
|
With the release of Chrome 74 and webdriver-manager 12.1.2 not supporting this is now an official bug. |
|
And 12.1.3 has been released! This should resolve the ChromeDriver issue. How to get it?
|
|
More info on the StackOverflow post: https://stackoverflow.com/questions/55910242/when-using-protractor-5-4-2-webdriver-manager-downloads-2-46-which-is-not-compa/55911176#55911176 |
|
@cnishina Thanks for resolving this issue. Verified 12.1.3 is downloading Chrome 74 with proper Selenium Jar file using Protractor 5.4.2 |
|
Looks to be working only if the default version is used. We always specify the version as our jenkins machines have a fixed chrome version and therefore we want to specify the webdriver version. This used to work, but now it is reporting errors in the console. Command that is failing: Output Using this command does not report the errors: |
|
Yup I can duplicate this on my machine.... 😞 |
|
@cnishina Is there a workaround for this? We're installing > ./node_modules/.bin/webdriver-manager version
12.1.3
> google-chrome --version
Google Chrome 74.0.3729.108When supplying > ./node_modules/.bin/webdriver-manager update --versions.chrome=$(google-chrome --version | cut -d ' ' -f 3)
[16:32:13] E/downloader - undefined
[16:32:13] I/update - chromedriver: file exists /tests/node_modules/protractor/node_modules/webdriver-manager/selenium/chromedriver_74.0.3729.108.zip
[16:32:13] I/update - chromedriver: unzipping chromedriver_74.0.3729.108.zip
(node:99) UnhandledPromiseRejectionWarning: Invalid filename
(node:99) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)When not supplying > ./node_modules/.bin/webdriver-manager update
[16:44:54] I/update - chromedriver: file exists /tests/node_modules/protractor/node_modules/webdriver-manager/selenium/chromedriver_75.0.3770.8.zip
[16:44:54] I/update - chromedriver: unzipping chromedriver_75.0.3770.8.zip
[16:44:54] I/update - chromedriver: setting permissions to 0755 for /tests/node_modules/protractor/node_modules/webdriver-manager/selenium/chromedriver_75.0.3770.8
[16:44:54] I/update - chromedriver: chromedriver_75.0.3770.8 up to dateWhen trying to run tests in protractor, we then get the following error: [chrome #01-14] [15:58:41] I/runnerCli - session not created: This version of ChromeDriver only supports Chrome version 75 |
|
Having the exact same issue. as scooper91. |
cnishina
changed the title
|
Proposed fixes for downloading specific versions, starting specific versions, status, and preventing 75 from being downloaded. |
|
yup. exact same issue here. latest installs 75, chrome version is 74, trying to do a |
|
I just released 12.1.4. This should fix the issues we are seeing with chromedriver 75 and chrome 74 mismatches. Also you should be able to download Could I get some verifiers that 12.1.4 is working for you? |
|
It worked for me. Thanks |
|
Verified both "webdriver-manager update" & "webdriver-manager update --versions.chrome 74.0.3729.6" with Protractor 5.4.2, ChromeDriver "chromedriver_74.0.3729.6.zip" is downloaded correctly. Thanks again for fixing this issue. |
|
@cnishina I'll spend some time to add tests around this functionality to prevent incidents like this from happening in future. |
|
@macroking This is the legacy branch that I want to be off of. Problem here is that I already wrote these fixes for the master branch and the reason for the new master branch was to have more testing. |
|
Here is the StackOverflow post that goes along with this: https://stackoverflow.com/questions/55910242/when-using-protractor-5-4-2-webdriver-manager-downloads-2-46-which-is-not-compa |
|
@cnishina : Hello, i tried the step you have mentioned and i also see that the chrome version is pointing out to 74xx but when i run this in the docker , i am running into the same issue : |
|
Wow that's weird. So do you have Chrome 74 and Chromedriver 74? What version of Chrome are you using in this docker file? In my circleci config, I check the chrome version to make sure I know what I'm dealing with. https://github.com/angular/protractor/blob/master/.circleci/config.yml#L13 |
|
@jthimmavajjhala I created an example test https://github.com/cnishina/protractor542-chrome74 with my output from my desktop. This is using direct connect and I was able to create a session. Is this docker file available to review? |
|
Closing this issue. |
* build: fix in check_deps.sh * feat(builtin): change default node version to 10.16.0 Also update CircleCI image to 10.16.0 as well as the CHROMEDRIVER_VERSION_ARG env. Lock needed updating to get the latest webdriver-manager that can handle the latest chromedriver archives. See angular/webdriver-manager#376.
|
@cnishina |
|
This solution works for me.
|
|
This issue is back :( now it's happening with Chrome 79.0.3945, on AzureDevops it downloads 79.0.3945.36 but azure only supports 79.0.3945.16 and there's NO way to force webdriver to use this exact version. it automatically downloads the LATEST on 79.0.3945.XXX and this is breaking my deployment. |
|
installing all the packages globally including chromdriver and making changes to the config.json file of webdriver worked for me :) |
|
WebDrivermanager 4.0.0 not supporting chrome 83. By launching browser through selenium, getting "data:," in url. Please suggest any solution.. |
|
For me LATEST downloaded chromedriver 85 and Official release of Chrome is 84.. Tried to update version of chromdriver but it's still running wrong version |
|
For us, stable chrome is still 84, but webriver manager downloads chromedriver 85 ... |
|
We are also facing the same issue. Chrome is on version 84 (stable version) but protractor uses chromedriver 85 (latest version) |
|
Same here. How can webdriver use a chrome version that is not even published? Edit: It worked yesterday. Started up the computer this morning and wanted to run the tests again, then the announced problem occured. Edit2: Then copy and paste the downloaded driver to your desired destination (in my case, it's the root of my angular app where protractor.conf.js is, I created a folder called "chromeDrivers" on the root level) and specify the path to the .exe in the protractor.conf.js file like this (notice the path is relative): exports.config = { Then, back on the cmd, just run Hope it helps someone, although it's not directly a webdriver-manager issue. |
Thanks!!! this works for me |
|
The following worked for us:
Protractor still installs chromedriverr 85, but it will use the 84 version. ** In our case, we run our protractor tests in docker, but develop mostly on windows. So I updated the protractor.conf to have this line so that it works in either: |
|
Should this be a new issue thread since this one has already been caused? We don't know if it has the same root cause as the past similar issues. |
and others
Now that Chrome 74 is the stable version, our unit tests are no longer working. Looking into the issue, we see that Chrome 74 is out, but
webdriver-manager updateis downloading 2.46 instead of the correct version of74.0.3729.6.Even if we run the command with the correct version, it is failing:
Opening the
node_modules/webdriver-manager/selenium/update-config.jsonI can see that it is saying 2.46 is the latest instead of 74.0.3729.6From http://chromedriver.chromium.org/:
This is blocking our ability to test our code. I'd appreciate any work-around if any is known in getting Chrome 74 working with
webdriver-managerThe text was updated successfully, but these errors were encountered: