-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Chromedriver patcher is broken for Chrome >= 115 #1402
Comments
Thank you for posting this, @Hyperz. I am noticing the same issue. Also seeing this issue with an RPA software too. Kinda surprised I did not hear about that chromedriver change prior to now. |
How can this be solved? |
According to https://github.com/SeleniumHQ/selenium/milestone/12, the earliest that the fix will be available in Until then, you can use SeleniumBase's UC Mode as an alternative, which has the fix for Chrome 115. First from seleniumbase import Driver
import time
driver = Driver(uc=True)
driver.get("https://nowsecure.nl/#relax")
time.sleep(8)
driver.quit() |
I change self.version_main = version_main to self.version_main = 114 in pather.py, all work, chrome version 115.0.5790.99 |
I use your code (bypass is ok), but if click on some link in page, I see cloudflar block page!!! |
@mdmintz I checked that link to the Selenium milestone. But I didn't find an issue for this. Is there one that you can link? Seems like this is still not fixed on their side. |
@claell Code has been merged, but not yet released: Relevant links: |
has this been fixed yet ?? |
I did confirm that patcher.py is setting the location to download the driver as "https://chromedriver.storage.googleapis.com" Which is the old location that only houses 114 and below. So unfortunately it seems to still be broken for me on Chrome 115 with the latest selenium (4.11.2) and the latest undetected_chromedriver (3.5.0) |
@ecossett-hc Yep, the UC maintainer still needs to update:
First detect the Chrome version, then download from the correct location. There's a patched fork in another repo with an example here: #1402 (comment) |
@mdmintz Ah gotcha! I'll poke around with seleniumbase. Unfortunately our RPA software (based on Selenium) has hit issues with chrome 115 as well so I've been fighting both of these issues at once haha |
@ecossett-hc For the seleniumbase formats that run with pytest, be sure to use |
@mdmintz will do! |
seems like the issue got resolved. its working with 115 for me |
This issue still persists. |
Found a temporary fix: ugorsahin/TalkingHeads#25 (comment) |
It looks like Google has deprecated https://chromedriver.storage.googleapis.com for Chrome versions over 114. As a result the patcher is throwing a 404 HTTPError with the latest Chrome update because https://chromedriver.storage.googleapis.com/LATEST_RELEASE_115 doesn't exist. There's a new API at https://googlechromelabs.github.io/chrome-for-testing/last-known-good-versions-with-downloads.json which replaces the old one.
Related Google announcement: https://groups.google.com/g/chromedriver-users/c/clpipqvOGjE/m/5NxzS_SRAgAJ
The text was updated successfully, but these errors were encountered: