[🐛 Bug]: Getting error code: "65: Wrong browser/driver version" while triggering the chromedriver in C# N-unit project

marupudit commented 2 weeks ago

What happened?

I have updated the selenium dependancies to latest version: Selenium.Webdriver: 4.21.0 Selenium.Support: 4.21.0

and using the chrome Version 125.0.6422.142 (Official Build) (64-bit)

When I execute the tests in this project(C# Nunit Selenium Test solution), getting this error:

Message: OpenQA.Selenium.NoSuchDriverException : Unable to obtain chrome using Selenium Manager; For documentation on this error, please visit: https://www.selenium.dev/documentation/webdriver/troubleshooting/errors/driver_location ----> OpenQA.Selenium.WebDriverException : Error starting process: \bin\Debug\net7.0-windows\selenium-manager/windows/selenium-manager.exe --browser "chrome" --output json ----> OpenQA.Selenium.WebDriverException : Selenium Manager process exited abnormally with 65 code: \bin\Debug\net7.0-windows\selenium-manager/windows/selenium-manager.exe --browser "chrome" --output json { "logs": [ { "level": "ERROR", "timestamp": 1718105504, "message": "Wrong browser/driver version" } ], "result": { "code": 65, "message": "Wrong browser/driver version", "driver_path": "", "browser_path": "" } }

TearDown : OpenQA.Selenium.NoSuchDriverException : Unable to obtain chrome using Selenium Manager; For documentation on this error, please visit: https://www.selenium.dev/documentation/webdriver/troubleshooting/errors/driver_location ----> OpenQA.Selenium.WebDriverException : Error starting process: \bin\Debug\net7.0-windows\selenium-manager/windows/selenium-manager.exe --browser "chrome" --output json ----> OpenQA.Selenium.WebDriverException : Selenium Manager process exited abnormally with 65 code: \bin\Debug\net7.0-windows\selenium-manager/windows/selenium-manager.exe --browser "chrome" --output json { "logs": [ { "level": "ERROR", "timestamp": 1718105505, "message": "Wrong browser/driver version" } ], "result": { "code": 65, "message": "Wrong browser/driver version", "driver_path": "", "browser_path": "" } }

How can we reproduce the issue?

Tried to run the command via CMD:
PS \bin\Debug\net7.0-windows\selenium-manager/windows/selenium-manager.exe  --browser "chrome" --output json                                                                                   {
  "logs": [
    {
      "level": "ERROR",
      "timestamp": 1718112097,
      "message": "Wrong browser/driver version"
    }
  ],
  "result": {
    "code": 65,
    "message": "Wrong browser/driver version",
    "driver_path": "",
    "browser_path": ""
  }
}

Relevant log output

Tried to run the command via CMD:
PS \bin\Debug\net7.0-windows\selenium-manager/windows/selenium-manager.exe  --browser "chrome" --output json                                                                                   {
  "logs": [
    {
      "level": "ERROR",
      "timestamp": 1718112097,
      "message": "Wrong browser/driver version"
    }
  ],
  "result": {
    "code": 65,
    "message": "Wrong browser/driver version",
    "driver_path": "",
    "browser_path": ""
  }
}

Operating System

Windows 10

Selenium version

4.21.0

What are the browser(s) and version(s) where you see this issue?

chrome Version 125.0.6422.142

What are the browser driver(s) and version(s) where you see this issue?

chrome Version 125.0.6422.142

Are you using Selenium Grid?

No

github-actions[bot] commented 2 weeks ago

@marupudit, thank you for creating this issue. We will troubleshoot it as soon as we can.

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

titusfortner commented 2 weeks ago

I think this is duplicate of #14093 If not, we'll need to see logs at FINE/DEBUG level to differentiate

SeleniumHQ / selenium