Hi, Google Chrome has been automatically updated to version 115.0.5790.171 (64-bits). Where can I find the ChromeDriver for this version?
--
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/dffd332e-c3d8-4303-8e55-ada41a3fc7f2n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/11791cb4-ede2-4a7e-a790-1a28ca1090b2n%40googlegroups.com.
No similar option to request the latest recommendede driver available for download from 115 on...
That script works if you find a driver version number at https:/edgedl.../chrome-for-testing ... that matches excactly the version number of your Chrome browser.But when my update script detects I have Chrome version 115.0.5790.171 running on my test computers, "https://edgedl.me.gvt1.com/edgedl/chrome/chrome-for-testing/115.0.5790.171/win64/chromedriver-win64.zip" will not find any driver...Problem is there are so many different sub versions of Chrome 115, but the Chrome-For-Testing site only offers download of the .170 driver version...
- Up until version 114, we could find the recommended driver version avialable for download by a request to https://chromedriver.storage.googleapis.com/LATEST_RELEASE_114
- This request would e.g. return 114.0.5735.90
- The driver could then be downloaded from "https://chromedriver.storage.googleapis.com/114.0.5735.90/chromedriver_win32.zip"
- No similar option to request the latest recommendede driver available for download from 115 on...
To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/4791c3f0-b9df-4cc3-ad06-9389c40af635n%40googlegroups.com.
How can I query for the recommended driver for Chrome 115 after it is removed from this list of latest Stable/Beta/Dev/Canary releases?
To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/813cf1ed-84d1-4d5e-be21-e2fe039635bbn%40googlegroups.com.
What they seem to be doing in v115+ is forcing us to use either the closest matching version of Chromedriver (using custom or third party tools as their webservice doesn't seem to work for v115+)
For example, they will release a specific stable version of Chrome for Testing and the matching Chromedriver for that version but they don't seem to have either Chrome for Testing or Chromedriver releases for every version of Chrome being released to end users.
To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/63310724-a7de-4acf-b6ce-1075f8dbf4f0n%40googlegroups.com.
Which web service isn’t working?
To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/4ebbd4d3-4028-452b-9a51-0b9657edc0f4n%40googlegroups.com.
Mathias, yes, I have read that page as anyone here I believe. Can you point what I am missing?
We are trying to create an automated Chromedriver downloader by looking at the Chrome version of our users. If the version is below 115 we use the LATEST_RELEASE link as before, for 115 and above we use the version selection pages info.
For version 115.0.5790.171 particularly our software started failing again, because none of the version selection info, neither the dashboard here:
https://googlechromelabs.github.io/chrome-for-testing/
nor any of the JSON links here:
https://github.com/GoogleChromeLabs/chrome-for-testing#json-api-endpoints
has the .171 version of Chrome as a Stable release, and there are no links to Chromedriver for .171 exists.
In your announcement in May, you said:
"every Chrome release that gets pushed to users automatically gets a correspondingly-versioned ChromeDriver release"
So according to this info what we have done to update our software is to try to find the same Chrome version corresponding Chromedriver version.
But with .171 our customers have started reporting bugs for our software not working because their Chrome is updated to 115.0.5790.171, and we can't find the corresponding Chromedriver, causing our auto-update to fail again.
Isn't 115.0.5790.171 a stable version? Why can't we find it anywhere in the version selection pages?
Or should we not look for the same chromedriver version and just use the latest Stable chromedriver version closest to the Chrome version in the dashboard Stable channel or the JSON links.
Thanks,
Or should we not look for the same chromedriver version and just use the latest Stable chromedriver version closest to the Chrome version in the dashboard Stable channel or the JSON links.
To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/ebc3b9c9-06dd-4eb8-b941-a6e11de05004n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/9ad9200d-10e5-440a-9381-10691b0a73a0n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/12e12874-deae-4740-a342-0b5d61cedbadn%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/2b45fc11-6bcc-493a-834e-b3e454a08771n%40googlegroups.com.
I have the same issue: my Chrome browsers are 115.0.5790.171, but the closest matching ChromeDriver version is 115.0.5790.170Using the chromedriver googleapis url pre Chrome 115, I could automate the driver updates by requesting the recommended driver version number for chrome, and then download that version.For this new Chrome-For-Testing setup, you say that each chrome version should have a chromedriver with a corresponding version number.
Thus I would expect, that if my scripts finds that I have Chrome version X.Y.Z, I could download the corresponding chromedriver from https://edgedl.me.gvt1.com/edgedl/chrome/chrome-for-testing/X.Y.Z/win64/chromedriver-win64.zipIs there any endpoint I could query, to get the excact chromedriver version number recommended for a specific chrome version (or major version)?
On Friday, 4 August 2023 at 17:01:16 UTC+2 Gilles Hoeltzel wrote:
instructions ?
Le vendredi 4 août 2023 à 07:26:15 UTC+2, Mathias Bynens a écrit :
Please follow the instructions at https://chromedriver.chromium.org/downloads/version-selection.On Fri, Aug 4, 2023 at 5:10 AM Aleksandr Vasilev <how...@gmail.com> wrote:
пятница, 4 августа 2023 г. в 03:34:18 UTC+9, SAMIR ABBOUD:
Hi, I Have the same issue And I can't find the ChromeDriver for the version 115.0.5790.171, any solution!
Le jeudi 3 août 2023 à 12:32:54 UTC+2, jd....@yucom.be a écrit :
I can't find the ChromeDriver 115.0.5790.171 (64-bits) via your link. Only the ChromeDriver 115.0.5790.170 (64-bits) is listed.Op donderdag 3 augustus 2023 om 08:58:07 UTC+2 schreef Mathias Bynens:
Hi, Google Chrome has been automatically updated to version 115.0.5790.171 (64-bits). Where can I find the ChromeDriver for this version?--
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/dffd332e-c3d8-4303-8e55-ada41a3fc7f2n%40googlegroups.com.
--
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/11791cb4-ede2-4a7e-a790-1a28ca1090b2n%40googlegroups.com.
“Google Chrome for Testing” is damaged and can’t be opened. You should move it to the Trash.
b) Should I even use this TEST version of the Chrome? My current general version is Version 116.0.5845.96 (Official Build) (arm64). Does that mean that the CrhomeWebDriver is embedded?
If so, how should I configure my code in this case? Do I need to use the chrome_driver_path?