[🐛 Bug]: ChromeDriverService.CreateDefaultService() + service.Start() results in ArgumentNullException

[drauch]

What happened?

Executing the following in a .NET 7 environment:

var service = ChromeDriverService.CreateDefaultService();
service.Start();

throws:

System.ArgumentNullException : Value cannot be null. (Parameter 'path1')
   at System.ArgumentNullException.Throw(String paramName)
   at System.IO.Path.Combine(String path1, String path2)
   at OpenQA.Selenium.DriverService.Start()

How can we reproduce the issue?

See above.

Relevant log output

-

Operating System

Windows 10

Selenium version

4.12.x

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

Chrome

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

ChromeDriver 117.0.5938.62

Are you using Selenium Grid?

no

[github-actions]

@drauch, 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]

Diego fixed this in Java recently
5bce8d9

Need to do something similar here.

[nvborisenko]

Reproduced it with 4.14.1.

[nvborisenko]

Fixed by 6f97b8d

[titusfortner]

so, uhh, looks like I didn't assign the result to driverServicePath 🤦
https://github.com/SeleniumHQ/selenium/pull/12816/files#diff-c38089621d41671b4719164b262303e275d4a4a442125fd9d4ea61eeca855c2bR267

[nvborisenko]

Don't blame yourself, I approved your change.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.