Selenium 4.18.1 with Chrome 122 is not working

[Abhay Bharti]

Recently I upgraded selenium jar version to 4.18.1 in my project. I am running on Google Chrome version 122. Web app is not loading correctly, like icons/images are not loading. Execution is getting stuck, after some time error "Caused by: org.openqa.selenium.TimeoutException: java.util.concurrent.TimeoutException" is getting thrown.

When I downgrade Selenium version to 4.13.0, getting this error.

21:45:32 Feb 27, 2024 9:45:31 PM org.openqa.selenium.chromium.ChromiumDriver lambda$new$5 21:45:32 WARNING: Unable to find version of CDP to use for 122.0.6261.70. You may need to include a dependency on a specific version of the CDP using something similar to `org.seleniumhq.selenium:selenium-devtools-v86:4.13.0` where the version ("v86") matches the version of the chromium-based browser you're using and the version number of the artifact is the same as Selenium's. org.openqa.selenium.devtools.DevToolsException: You are using a no-op implementation of the CDP. The most likely reason for this is that Selenium was unable to find an implementation of the CDP protocol that matches your browser. Please be sure to include an implementation on the classpath, possibly by adding a new (maven) dependency of `org.seleniumhq.selenium:selenium-devtools-vNN:4.13.0` where `NN` matches the major version of the browser you're using.

[Krishnan Mahadevan]

Couple of things to check for:

* If you are managing the driver binaries manually or via any other means, get rid of them and let Selenium do its magic via the Selenium Manager.

* Downloading just the dependencies might not work because I believe that every version of selenium packs along with it the corresponding and supported CDP implementations that are required to interact with the web tools capability of the chrome browser. So if you downgrade your selenium dependency, you may also need to downgrade your chrome browser as well.

* If the issue continues, then you can for the time being resort to running your tests against chrome docker image for the corresponding version of your client binding. That way you wont see the error you mentioned below.

If the problem still persists after ensuring that browser driver binaries are being managed fully via Selenium Manager, you should report this as a bug.

Thanks & Regards
Krishnan Mahadevan

"All the desirable things in life are either illegal, expensive, fattening or in love with someone else!"
My Scribblings @ http://wakened-cognition.blogspot.com/

My Technical Scribblings @ https://rationaleemotions.com/

--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-users/2484049b-d435-46da-8df0-a49785bc9f19n%40googlegroups.com.