-
Notifications
You must be signed in to change notification settings - Fork 116
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
Latest chrome is not supported 115.0.5790.98 #523
Comments
@dgp1130 ??? |
I think this is also the same with my problem, today I tried to run webdriver-manager on my phyton code for selenium, and this error appear
|
i am also getting the same issue. is some one looking into it? $ npx webdriver-manager update --gecko=false --versions.chrome 115.0.5790.102 Error: Invalid filename: C:\Users\m\AppData\Local\npm-cache_npx\88020e2694c9921b\node_modules\webdriver-manager\selenium\chromedriver_115.0.5790.102.zip Node.js v19.8.1 |
chromedrive changed their endpoint for download the latest chromedriver (115 onwards) |
use "selenium-manager" to download latest chromedriver binaries. |
@StanislavKharchenko do you have idea how to match the "selenium-manager" with protractor ? |
@bboycs The simple solution is to prepare short script which will call selenium-manager, download driver binaries and copy it to node-modules/webdriver-manager/downloads folder (to path where these binaries should actually present) |
What I did to solve this is just write a postinstall node script to hit the "last-known-good-versions-with-downloads" endpoint , download the correct file, and unzip it. I then added the "chromeDriver" parameter to the protractor config file, so that it points to where I download it, instead of attempting to use webdriver-manager. |
Inspired by @StanislavKharchenko and @ParmaJonEman proposals, I use this method as a workaround:
|
For Mac and using NPM webdriver-manager package,
Now, you would be using latest chrome driver for selenium with your latest browser. You would not see following error "session not created: This version of ChromeDriver only supports Chrome version 114 Don't run webdriver-manager update cmd after renaming otherwise it will overwrite older version of chrome-driver |
@karan-deep I tried this but I still get an error:
Any ideas? |
Protractor's downloading of chromedriver is broken (angular/webdriver-manager#523), so we add a workaround using a different download tool. We could do this by changing the CI job definition, but then we would have to sync this change to every branch. If we instead change only the Docker image and hack the npx command (that gets executed by the current CI job) to do what we need, it will immediately start working again across all branches, and it will be easy to remove again if necessary. So while this hack is somewhat ugly, it seems preferable. Cf. #1141 git-svn-id: https://svn.sosy-lab.org/software/cpachecker/trunk@44685 4712c6d2-40bb-43ae-aa4b-fec3f1bdfe4c
@karan-deep @ParmaJonEman |
Can you be more specific? What should people use instead of |
Background
As of version 115, chromedriver builds are now stored in a new repository.
Reproducible case
Output
The text was updated successfully, but these errors were encountered: