Downloading ChromeDriver 115+ fails

[JaZo]

Downloading ChromeDriver 115+ fails

[glaszig]

looks like they changed infrastructure:

• builds: https://googlechromelabs.github.io/chrome-for-testing/
• json endpoints: https://github.com/GoogleChromeLabs/chrome-for-testing#json-api-endpoints

i think the correct endpoint for our case here is https://googlechromelabs.github.io/chrome-for-testing/known-good-versions-with-downloads.json

[driesvints]

Hey all. I sent in a PR that we're hopefully gonna merge and tag soon. I'd appreciate anyone who could try it out. I need some testing on different OS's like Linux/Windows: #1042

[rettigd]

I've run it through docker debian instances (locally and through github deployment actions) with no errors. The detection/download takes a really long time. This step has gone from 10ish seconds to 2+ minutes as a github action. Also very slow locally. No idea it it's an upstream issue or not.

[driesvints]

@rettigd strange... that's indeed a lot longer. I'm not sure why that is. All I did was adopt the new download urls.

[JaZo]

I experience the same performance issue as @rettigd; from a few seconds in the old situation to a minute now. I've narrowed it down to the download of the ChromeDriver zip. When I swap the file_get_contents for a curl_exec it only takes a few seconds. I also tried this solution, but that didn't make a difference.

[devphp0786]

Hi Team,

I am successfully updated the chrome binary with this solution but now dusk is not working and not able to find the elements like username password and having button to login

[hashimaziz1]

What's the best way to fix this in a Laravel 8 application? Is it safe to run composer update laravel/dusk --with-all-dependencies without running the risk of breaking things?