Chromedriver

[Mohammed Asif]

Hi All,

browser = webdriver.Chrome(executable_path=ChromeDriverManager().install()) this is how i used to automatically install updated version of chromedriver.exe and do the automation process. But after updating the new version of the chrome i  am unable to download the new version of chromedriver which throws me error in webdriver-manager package. The error states that 'ValueError: There is no such driver by url https://chromedriver.storage.googleapis.com/LATEST_RELEASE_115.0.5790'.

Please anyone help me with the issue. All my previous automations also now stopped working..

[Mani Renukuntla]

Facing the same issue

[Sarah “Early For Learners” Academy]

Facing same issue need help

[adhigundla mahesh]

Facing same issue

[Mathias Bynens]

We’re aware of an issue where ChromeDriver 115 on macOS doesn’t find the regular Google Chrome browser binary at its default location. The relevant crbug is https://bugs.chromium.org/p/chromium/issues/detail?id=1466427. We’ve already identified the issue and submitted a fix for M117, and are currently working on back-merging the fix to M115 and M116 as well. Until this process is complete, you can use any of the workarounds we’ve posted on GitHub.

Apologies for the inconvenience.

--
You received this message because you are subscribed to the Google Groups "ChromeDriver Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromedriver-us...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/cf62ec82-aa20-46b8-8025-845b3584381bn%40googlegroups.com.

[Mathias Bynens]

We’re aware of an issue where ChromeDriver 115 on macOS doesn’t find the regular Google Chrome browser binary at its default location. The relevant crbug is https://bugs.chromium.org/p/chromium/issues/detail?id=1466427. We’ve already identified the issue and submitted a fix for M117, and are currently working on back-merging the fix to M115 and M116 as well. Until this process is complete, you can use any of the workarounds we’ve posted on GitHub.

Apologies for the inconvenience.

--

You received this message because you are subscribed to the Google Groups "ChromeDriver Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromedriver-us...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/76aebd9f-1d80-47a6-9462-10fb3cbab8efn%40googlegroups.com.

[Mathias Bynens]

This sounds like an issue with ChromeDriverManager rather than with ChromeDriver. A quick search revealed https://github.com/SergeyPirogov/webdriver_manager/issues/536, for which a patch is already available: https://github.com/SergeyPirogov/webdriver_manager/pull/537

On Fri, Jul 21, 2023 at 7:12 AM Sarah “Early For Learners” Academy <gulshana.ch...@gmail.com> wrote:

--

[NIHITH RAJ]

+ Facing the same issues. Uninstalling Chrome and Rebooting seems to be temporary Fix. Something to do with ChromeDriverManager Glitch.

[Amita Das]

Facing same issue

[Nicole-Jocelyn Sanchez]

I found this solution from git user Yacov-ma in this thread that worked seamlessly:


"You can pass a version to ChromeDriverManager as a workaround.
For example :

s = Service(ChromeDriverManager(version="114.0.5735.90").install())

and it's work."

Happy selenium-ing! :) 

[Amelia Jochna]

Solved this issue by downgrading chrome version and changing driver version. Not the best solution but works as a temporary one.