[🐛 Bug]: Unable to find an exact match for CDP version 130, returning the closest version; found: 129; Please update to a Selenium version that supports CDP version 130

[alibdaer]

What happened?

This Warning appear:

Oct 21, 2024 10:55:20 AM org.openqa.selenium.devtools.CdpVersionFinder findNearestMatch WARNING: Unable to find an exact match for CDP version 130, returning the closest version; found: 129; Please update to a Selenium version that supports CDP version 130

please not i have the latest versions for all dependencies

    <dependency>
        <groupId>org.seleniumhq.selenium</groupId>
        <artifactId>selenium-java</artifactId>
        <version>4.25.0</version>
    </dependency>

    <dependency>
        <groupId>io.github.bonigarcia</groupId>
        <artifactId>webdrivermanager</artifactId>
        <version>5.9.2</version>
    </dependency>

Because of that and after this warning started appearing, I have errors while running the test case, it no longer waits for the Iframe to finish fully loading.

How can we reproduce the issue?

<dependency>
            <groupId>org.seleniumhq.selenium</groupId>
            <artifactId>selenium-java</artifactId>
            <version>4.25.0</version>
        </dependency>

        <dependency>
            <groupId>io.github.bonigarcia</groupId>
            <artifactId>webdrivermanager</artifactId>
            <version>5.9.2</version>
        </dependency>

Relevant log output

Oct 21, 2024 10:55:20 AM org.openqa.selenium.devtools.CdpVersionFinder findNearestMatch
WARNING: Unable to find an exact match for CDP version 130, returning the closest version; found: 129; Please update to a Selenium version that supports CDP version 130

Operating System

Windows 10

Selenium version

4.25.0

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

Chorme (Latest Version: 130.0.6723.59)

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

webdrivermanager - 5.9.2 (chromedriver - 130.0.6723.58)

Are you using Selenium Grid?

No response

[github-actions[bot]]

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

[mrankin32]

I have almost the same specs and versions as the author but with Windows 11 instead of Windows 10 with the same error:

[10/21/2024 21:54:57] WARN : org.openqa.selenium.devtools.CdpVersionFinder : Unable to find an exact match for CDP version 130, returning the closest version; found: 129; Please update to a Selenium version that supports CDP version 130

[LloyDee]

Same issue here:

<dependencies>
        <!-- https://mvnrepository.com/artifact/org.seleniumhq.selenium/selenium-java -->
        <dependency>
            <groupId>org.seleniumhq.selenium</groupId>
            <artifactId>selenium-java</artifactId>
            <version>4.25.0</version>
        </dependency>
        <!-- https://mvnrepository.com/artifact/io.github.bonigarcia/webdrivermanager -->
        <dependency>
            <groupId>io.github.bonigarcia</groupId>
            <artifactId>webdrivermanager</artifactId>
            <version>5.9.2</version>
        </dependency>
</dependencies>

Oct 21, 2024 11:32:23 PM org.openqa.selenium.devtools.CdpVersionFinder findNearestMatch WARNING: Unable to find an exact match for CDP version 130, returning the closest version; found: 129; Please update to a Selenium version that supports CDP version 130

[alibdaer]

The problem is not only the warning, but some of the written commands are now working illogically, and some pages and frames are now being dealt with without waiting for them to load. Something has changed. I have test cases that have been working properly for more than a year, now after this warning they are broken and not working. We are waiting for the problem to be solved, either by a new version of selenium, or for the issue to be fixed by the browsers.

[SerhiiYesychko]

using the same versions

org.seleniumhq.selenium selenium-java 4.25.0 io.github.bonigarcia webdrivermanager 5.9.2

I test started failing on Friday with NoSuchSession Session ID is null. randomly at some moment during test run

[krish-tcc]

Same - literally just started happening to me right in the middle of using selenium.

Please update to a Selenium version that supports CDP version 130

[miteshkumat]

Same issue happen to me. I literally try to hard solve this problem . Please update Selenium version that supports CDP version 130.This is my error.

Oct 22, 2024 8:20:58 P.M. org.openqa.selenium.devtools.CdpVersionFinder findNearestMatch WARNING: Unable to find an exact match for CDP version 130, returning the closest version; found: 129; Please update to a Selenium version that supports CDP version 130

[eftewuer]

Confirmed. This warning started to appear when running existing selenium tests with Chrome 130.x.

[SerhiiVoloshchenko]

Thats because in 4.25.0 you have only selenium-devtools-v129 but there is no selenium-devtools-v130. Thats mean you not supporting Chrome v130

[alibdaer]

Thats because in 4.25.0 you have only selenium-devtools-v129 but there is no selenium-devtools-v130. Thats mean you not supporting Chrome v130

Well, how can supporting the chrome v130?

[AnushanVamathevan]

I’m facing the same problem, and I’ve been struggling to fix it. The error says I need to update Selenium to a version that supports CDP version 130. This is my error: Oct 23, 2024 3:49:37 PM org.openqa.selenium.devtools.CdpVersionFinder findNearestMatch WARNING: Unable to find an exact match for CDP version 130, returning the closest version; found: 129; Please update to a Selenium version that supports CDP version 130

[anilreddy]

Guys the warning is not bug or anything it will go when new version of selenium is released. You are seeing this warning because current selenium version only supports V129 not V130.

[SerhiiYesychko]

So I tried few options like java 11-17 selenium and driver 4.23-25 chrome and chrome driver 127-130 everything works fine locally if I run using Intelijj Idea and maven but when I try to run it in docker

FROM maven:3.6.3-openjdk-17-slim or FROM maven:3.6.3-openjdk-11

randomly at some point I get

[ERROR] SlideDeckV5Test>BaseTest.setUp:524 » NoSuchSession Session ID is null. Using WebDriver after calling quit()? Build info: version: '4.23.0', revision: '4df0a231af' System info: os.name: 'Linux', os.arch: 'amd64', os.version: '6.6.51-0-virt', java.version: '17-ea' Driver info: org.openqa.selenium.chrome.ChromeDriver Command: [null, get {url=here goes my url/}] Capabilities {acceptInsecureCerts: true, browserName: chrome, browserVersion: 127.0.6533.119, chrome: {chromedriverVersion: 127.0.6533.119 (bdef6783a05..., userDataDir: /tmp/.org.chromium.Chromium...}, fedcm:accounts: true, goog:chromeOptions: {debuggerAddress: localhost:37051}, networkConnectionEnabled: false, pageLoadStrategy: normal, platformName: linux, proxy: Proxy(), se:cdp: ws://localhost:37051/devtoo..., se:cdpVersion: 127.0.6533.119, setWindowRect: true, strictFileInteractability: false, timeouts: {implicit: 0, pageLoad: 300000, script: 30000}, unhandledPromptBehavior: dismiss and notify, webauthn:extension:credBlob: true, webauthn:extension:largeBlob: true, webauthn:extension:minPinLength: true, webauthn:extension:prf: true, webauthn:virtualAuthenticators: true}

BaseTest.setUp:524 here I have method that created webdriver as usual if (driver == null) { driver = DriverFactory.getInstance().getWebDriver(); driver.manage().timeouts().pageLoadTimeout(Duration.ofSeconds(Constants.WAITING_TIMEOUT)); driver.manage().timeouts().scriptTimeout(Duration.ofSeconds(Constants.WAITING_TIMEOUT)); } return driver;

    also it happens when it call driver.quit();

    have no idea what happened with docker runs, there was no changes

[alibdaer]

Here is the temporary solution, until Selenium supports version 130, delete Google Chrome completely and reinstall the older version which is 129, this way the problem will be solved temporarily

You can download Chrome V129 from this link: https://www.filepuma.com/download/google_chrome_64bit_129.0.6668.101-41911/

[MuratTopcu]

I use Selenium Manager and I tell it to download and use version 129

https://www.selenium.dev/documentation/selenium_manager/

[diemol]

Guys the warning is not bug or anything it will go when new version of selenium is released. You are seeing this warning because current selenium version only supports V129 not V130.

Exactly what @anilreddy says.

It is a WARNING that does not stop you from using Chrome 130.

We will release a new version of Selenium next week.

[alibdaer]

Guys the warning is not bug or anything it will go when new version of selenium is released. You are seeing this warning because current selenium version only supports V129 not V130.

Exactly what @anilreddy says.

It is a WARNING that does not stop you from using Chrome 130.

We will release a new version of Selenium next week.

Yes it does not stop me from using chrome 130, but there are errors in recognizing the element and sendKey and some problems waiting for pages to load and iframes and others,

Thank you for your response and we are waiting for the new release of Selenium

[diemol]

The errors seem related to the browser version, not Selenium itself. In that case, you should create an issue in the Chrome bug tracker.

[alibdaer]

The errors seem related to the browser version, not Selenium itself. In that case, you should create an issue in the Chrome bug tracker.

I did it: https://issuetracker.google.com/issues/375343406

[anilreddy]

@

The errors seem related to the browser version, not Selenium itself. In that case, you should create an issue in the Chrome bug tracker.

I did it: https://issuetracker.google.com/issues/375343406

@alibdaer your bug will not be accepted anywhere if you don't provide reproducible code or logs where the issue happens. How can any one knows where the bug is actually happening.

Regarding chrome V130 all my scripts are working as expected. I didn't observe any issues as you posted like identifying elements or switching to iframes.

Once posting a bug please check if you are writing proper code which has explicit waits before doing element interactions incase of please waits or there is a loading.

[alibdaer]

@

The errors seem related to the browser version, not Selenium itself. In that case, you should create an issue in the Chrome bug tracker.

I did it: https://issuetracker.google.com/issues/375343406

@alibdaer your bug will not be accepted anywhere if you don't provide reproducible code or logs where the issue happens. How can any one knows where the bug is actually happening.

Regarding chrome V130 all my scripts are working as expected. I didn't observe any issues as you posted like identifying elements or switching to iframes.

Once posting a bug please check if you are writing proper code which has explicit waits before doing element interactions incase of please waits or there is a loading.

I appreciate your advice, but it is naive of me to complain about a problem when I am not sure about the quality of my code.

Yes, my code is written accurately and professionally and I have been using it for more than two years for the server we work with.

After the latest updates, this problem appeared. I do not think it is magic or sorcery, but there is indeed a problem after the latest Google Chrome update.

It is not that simple. How can I attach a report that shows me that it does not recognize Element while before the update it recognized it without problems? How can I convince people like you that it is a problem with the update and not with the code?

Why when I downgrade Google Chrome to version 129 the code works successfully and without problems?

Specialists should review this matter, not me

Thank you, dear professional

[anilreddy]

@

The errors seem related to the browser version, not Selenium itself. In that case, you should create an issue in the Chrome bug tracker.

I did it: https://issuetracker.google.com/issues/375343406

@alibdaer your bug will not be accepted anywhere if you don't provide reproducible code or logs where the issue happens. How can any one knows where the bug is actually happening. Regarding chrome V130 all my scripts are working as expected. I didn't observe any issues as you posted like identifying elements or switching to iframes. Once posting a bug please check if you are writing proper code which has explicit waits before doing element interactions incase of please waits or there is a loading.

I appreciate your advice, but it is naive of me to complain about a problem when I am not sure about the quality of my code.

Yes, my code is written accurately and professionally and I have been using it for more than two years for the server we work with.

After the latest updates, this problem appeared. I do not think it is magic or sorcery, but there is indeed a problem after the latest Google Chrome update.

It is not that simple. How can I attach a report that shows me that it does not recognize Element while before the update it recognized it without problems? How can I convince people like you that it is a problem with the update and not with the code?

Thank you, dear professional

Sorry to say but they will close the bug simply check after some days

[alibdaer]

@

The errors seem related to the browser version, not Selenium itself. In that case, you should create an issue in the Chrome bug tracker.

I did it: https://issuetracker.google.com/issues/375343406

@alibdaer your bug will not be accepted anywhere if you don't provide reproducible code or logs where the issue happens. How can any one knows where the bug is actually happening. Regarding chrome V130 all my scripts are working as expected. I didn't observe any issues as you posted like identifying elements or switching to iframes. Once posting a bug please check if you are writing proper code which has explicit waits before doing element interactions incase of please waits or there is a loading.

I appreciate your advice, but it is naive of me to complain about a problem when I am not sure about the quality of my code. Yes, my code is written accurately and professionally and I have been using it for more than two years for the server we work with. After the latest updates, this problem appeared. I do not think it is magic or sorcery, but there is indeed a problem after the latest Google Chrome update. It is not that simple. How can I attach a report that shows me that it does not recognize Element while before the update it recognized it without problems? How can I convince people like you that it is a problem with the update and not with the code? Thank you, dear professional

Sorry to say but they will close the bug simply check after some days

I have no problem closing it, as it will be resolved after the new release of Selenium next week according to Team Lead.

As you can see many of the comments before you are suffering from the same problem, I am not the only one suffering from this, we are not complaining about the presence of a warning only. We are complaining about the problems that started to appear after the update

[bartlomiejfydrych]

I confirm this issue is occurring.

It looks like there was an update to Chrome Dev Tools and now we need to wait for Selenium to release an update that supports this version.