Chromedriver 115 do not find Chrome #1968
Comments
|
GoogleChromeLabs/chrome-for-testing#30 is probably the root cause. Let's wait on that before re-releasing 115 again. |
soulgalore
added a commit
that referenced
this issue
Jul 21, 2023
It turns out the Chrome team didn't test the new Chrome/Chromedriver 115 setup so I guess it's best we do it for them. #1968
soulgalore
added a commit
that referenced
this issue
Jul 21, 2023
soulgalore
added a commit
that referenced
this issue
Jul 21, 2023
* Run Firefox and Chrome tests on Mac. It turns out the Chrome team didn't test the new Chrome/Chromedriver 115 setup so I guess it's best we do it for them. #1968 * Also test on Edge
soulgalore
added a commit
that referenced
this issue
Jul 21, 2023
soulgalore
added a commit
that referenced
this issue
Aug 15, 2023
Fixes #1968 so we can renmove our fix.
soulgalore
added a commit
that referenced
this issue
Dec 28, 2023
Chromedriver has been updated that fixes the problem in #1968 so lets remove our fix.
soulgalore
added a commit
that referenced
this issue
Dec 28, 2023
Chromedriver has been updated that fixes the problem in #1968 so lets remove our fix.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I updated to 115.0.5790-98 I get
cannot find Chrome binaryeven though I got Chrome 115 installed on my Mac. I wonder if there's a new switch or something and that Chromedriver defaults to "Chrome for testing"? It seems to work fine for Linux and Windows though. On Mac it works if you set the path to the Chrome binary.The text was updated successfully, but these errors were encountered: