mac-x64 115.0. 5790.114 chromedriver missing

[Ben Moroze]

Hi,

The latest stable Mac Chrome binary is 115.0.5790.114, but there is no corresponding chromedriver under mac-x64 at least.  The latest one only matches the latest Windows stable of .110.  Will this be available shortly?

Thanks,

Ben

[Mathias Bynens]

Please use https://googlechromelabs.github.io/chrome-for-testing/ to get the latest available Chrome for Testing + ChromeDriver binaries. See https://groups.google.com/g/chromedriver-users/c/qVPTFXnedw0 for more context.

--
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/5fa9b92a-3b88-46bd-bd5a-a9fe86780248n%40googlegroups.com.

[Ben Moroze]

Hi--thanks.  I am not sure how this is useful, as it doesn't even list the correct latest stable release of Chrome for the Mac.  The latest stable is 115.0.5790.114.  That version is nowhere to be found in the JSON endpoints, or on the page you linked.  How can we possibly reliably automatically determine the correct chromedriver URL when these versions are inconsistent?  Up until now with this new scheme there has always been a chromedriver download that matched the exact Chrome version release on a platform.  Also, the current stable releases even on Windows for example is .110, yet this page says .102 and the "upcoming" is .110.  I think these need to be kept up to date and accurate. The .114 is not found in *any* of the JSON API endpoints files I checked.

Please advise.

Ben 

[Balaji Arumugam]

yeah facing the same issue, can someone help mitigate this?

[Mathias Bynens]

We recommend using Chrome for Testing rather than regular Chrome. This way you’re guaranteed to use the exact same version of Chrome + ChromeDriver.

If instead you insist on using regular Chrome and want to match it to a compatible ChromeDriver version, you need to do Version Selection just like before, except now you do it through the new JSON API endpoints.

Up until now with this new scheme there has always been a chromedriver download that matched the exact Chrome version release on a platform. 

This is false.

To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/b5e5dc76-270e-4571-8f56-25c9f274fc52n%40googlegroups.com.

[Ben Moroze]

The JSON endpoints are currently out of date and incorrect.  They reference older versions of the stable chrome releases, for instance.  We need to test on the actual stable (and beta) Chrome releases.  I think it's preferable to just make sure that there is a matching chromedriver available across all platforms when new channel endpoints are released, which is not false, it's been true up until the Mac case a few days ago.

[Yuri Khodos]

All this Chrome-For-Testing thing is very confusing. 

I currently have Chrome Browser. 115.0.5790.114 on mac-arm64. I downloaded ChromeDriver 115.0.5790.102, because it is the closest one available based on the https://googlechromelabs.github.io/chrome-for-testing/#stable page (I also checked the JSON endpoints) . Now I'm getting errors 

failed to create driver from callback 'script16906608136241638868675$_run_closure2$_closure4$_closure18@104789a1'
geb.driver.DriverCreationException: failed to create driver from callback 'script16906608136241638868675$_run_closure2$_closure4$_closure18@104789a1'

Could it be because the browser version is different? If so, how can I get the compatible driver?

Why wouldn't you simply release chromedriver together with the chrome browser version? It would make thing so much clearer.
 

[Kevin Bang]

How can I work around this? Do I need to wait until the .114 chromedriver gets released?

[Rasolomanana Kotoarijaona]

I faced the same issue, and i just used this old version of chromedriver 114.0.5735.90 and it's working for me at the moment.

[Yejin Jeong]

This worked for me. Thank you

2023년 8월 1일 화요일 오후 4시 6분 46초 UTC+9에 Rasolomanana Kotoarijaona님이 작성:

[Kevin Bang]

This worked for me as well, thank you!

[denzo]

same here, thank u so much

[Ben Moroze]

The problem here is that because they’re out of sync with *some* platforms with the chromedriver vs chrome channels, that it’s a manual guessing game as to what to use and is very difficult to automate. 

The json endpoints are completely wrong and do not match the actual release channels at all. 

This should be fixed. There’s no excuse for not having an identically-numbered chromedriver with *actual* stable release versions across all platforms, not just some. 

Ben

On Aug 1, 2023, at 2:07 PM, denzo <angela...@gmail.com> wrote:



You received this message because you are subscribed to a topic in the Google Groups "ChromeDriver Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/chromedriver-users/yf_7h_ryWY0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to chromedriver-us...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/c948b3d1-945d-45b5-9495-0ebbbb7cf756n%40googlegroups.com.