selenium-manager is downloading latest driver (134) but the browser is still on 133

[GrayDwarf]

Some teams recently switched over to selenium-manager but not all. We are now seeing the following error in our lab.

session not created: This version of ChromeDriver only supports Chrome version 134
Current browser version is 133.0.6943.142 with binary path C:\Program Files (x86)\Google\Chrome\Application\chrome.exe (SessionNotCreated)

We're using the default configuration for selenium-manager which I understand to use latest.
new DriverManager().SetUpDriver(new ChromeConfig());

Given that setup, I expect selenium-manager to evaluate the installed version of chrome for getting the correct driver version. I'm not clear on whether selenium-manager will download the latest version of Chrome or not.

We actually don't want selenium-manager to download newer versions of the browsers because we share a lab and not all people are using selenium-manager so we need to upgrade the browsers manually still. 

Do I need to be more specific in my initial configuration to get the desired result?

also, we're seeing a new Chrome folder with a bunch of different chromedriver versions in it and I assume that is selenium-manager who is doing that. The documentation suggests these files will go in ~/cache/selenium so I'm confused about where that is and why files are ending up in the working directory. Is documentation off or do I misunderstand?

[GrayDwarf]

Got some help from folks in Slack. Found out that we don't need to explicitly install WebDriverManager and that my usage ' new DriverManager().SetUpDriver(new ChromeConfig());' isn't needed either. After some package updates, things are working locally. Going to run in the lab for a bit and we won't know if things are working correctly until the next Chrome update. I might post back if I remember (or things don't work).

[Sahitya Kokkula]

If Selenium Manager is downloading the latest driver (version 134) but your browser is still on version 133, there might be a compatibility issue. Selenium WebDriver requires the browser version and the driver version to match for smooth execution.

How to Fix This Issue?

1. Manually Download the Compatible Driver

   • Go to the official ChromeDriver page: https://sites.google.com/chromium.org/driver/
   • Download the driver version matching your Chrome browser (133).
   • Replace the existing driver in your Selenium setup.

2. Use Selenium Manager with a Specific Version

   • Instead of letting Selenium Manager auto-download the latest version, specify the correct driver version in your script.

3. Update Your Browser to Match the Latest Driver

   • If possible, update your browser to version 134 so it aligns with the latest driver.

If you’re facing frequent compatibility issues in Selenium automation, consider joining our Selenium automation testing online course free demo to learn troubleshooting techniques, best practices, and expert tips to streamline your test automation process. 🚀 Sign up today and take your Selenium skills to the next level!