[🐛 Bug]: Unable to find match for CDP version 129 - SELENIUM IS 4.25.0

[Tennessene]

What happened?

When I run my program with Selenium 4.25.0 as the dependency and chromeDriver/Chrome 129.0.6668.58 (seems to be any 128 or 129 version), I get the message saying it can't find a match for CDP version 129 when I'm using Selenium 4.25.0

How can we reproduce the issue?

The repo is at https://github.com/Tennessene/SampleSeleniumProject
Run the "Test Run" workflow
The log should print the error

Relevant log output

Sep 25, 2024 5:43:28 PM org.openqa.selenium.devtools.CdpVersionFinder findNearestMatch
WARNING: Unable to find an exact match for CDP version 129, returning the closest version; found: 127; Please update to a Selenium version that supports CDP version 129

Operating System

macOS Sequoia / Windows 11 / Ubuntu 22.04

Selenium version

Java 4.25.0

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

Chrome 129.0.6668.58

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

chromeDriver 129.0.6668.58

Are you using Selenium Grid?

No

[github-actions]

@Tennessene, 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!

[joerg1985]

@Tennessene the linked repo is not visible to me. Are you using a fat jar for your project? This might break the ServiceLoader.

[Tennessene]

I forgot to make it visible. Yes, I’m using the fat jar because I don’t know how to run it otherwise.

…

On Thu, Sep 26, 2024 at 02:42 joerg1985 ***@***.***> wrote: @Tennessene <https://github.com/Tennessene> the linked repo is not visible to me. Are you using a fat jar for your project? This might break the ServiceLoader. — Reply to this email directly, view it on GitHub <#14538 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOT6SIPGIOGUMS5HG2YQFNTZYO3F5AVCNFSM6AAAAABO3V4GK6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZWGE3DQOBYGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Tennessene]

@joerg1985 I've edited my post to point to a simpler project created just for this issue. Please use it instead

[joerg1985]

The fat jar does break the ServiceLoader, you could exclude the v127 & v128 dependency to fix this.

When a fat jar is build the files inside the META-INF folder are not merged correctly, so only one of the implementations is loaded, see #13791.

[Tennessene]

Okay, so it's just a problem on my end, not a bug. Thank you

[github-actions]

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