WARNING: Unable to find an exact match for CDP version 97, so returning the closest version found: 96
Which version of Selenia supports CDP 97?
Currently, CDP 96 is the latest supported by selenium CDP version.
I saw this commit 23 days ago (Jan 5, 2022).
https://github.com/SeleniumHQ/selenium/commit/ba01ccd11a9cb75149acaa174a329a91e706ef99
So it should be available in the next released version.
Related
I am trying to execute a basic Selenium Java program:
public static void main(String[] args)
{
System.setProperty("webdriver.chrome.driver", "C:\\BrowserDrivers\\chromedriver.exe");
WebDriver driver = new ChromeDriver();
driver.quit();
}
With the following configuration:
Selenium 4.x
Chrome Version 109.0.5414.75 (Official Build) (64-bit) (Win 10)
ChromeDriver 109.0.5414.25
ChromeDriver:
Chrome and ChromeDriver both being of Version 109.x, though the program executes successfully still I see some WARNING messages on the console as follows:
Starting ChromeDriver 109.0.5414.25 (771113d280dd3dda2fb422a6c805f0eb2b8ee6ed-refs/branch-heads/5414#{#303}) on port 57273
Only local connections are allowed.
Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
ChromeDriver was started successfully.
Jan 14, 2023 3:10:47 AM org.openqa.selenium.remote.ProtocolHandshake createSession
INFO: Detected upstream dialect: W3C
Jan 14, 2023 3:10:47 AM org.openqa.selenium.devtools.CdpVersionFinder findNearestMatch
WARNING: Unable to find an exact match for CDP version 109, so returning the closest version found: a no-op implementation
Jan 14, 2023 3:10:47 AM org.openqa.selenium.devtools.CdpVersionFinder findNearestMatch
INFO: Unable to find CDP implementation matching 109.
Jan 14, 2023 3:10:47 AM org.openqa.selenium.chromium.ChromiumDriver lambda$new$3
WARNING: Unable to find version of CDP to use for . You may need to include a dependency on a specific version of the CDP using something similar to `org.seleniumhq.selenium:selenium-devtools-v86:4.3.0` where the version ("v86") matches the version of the chromium-based browser you're using and the version number of the artifact is the same as Selenium's.
Can someone help me to understand the issue behind the warnings:
WARNING: Unable to find an exact match for CDP version 109, so returning the closest version found: a no-op implementation
and
WARNING: Unable to find version of CDP to use for . You may need to include a dependency on a specific version of the CDP using something similar to `org.seleniumhq.selenium:selenium-devtools-v86:4.3.0` where the version ("v86") matches the version of the chromium-based browser you're using and the version number of the artifact is the same as Selenium's.
This is because the compatible version of 'Selenium Dev-Tools' is not yet released. The latest 'Selenium Dev-Tools' version is v108 which is compatible with Chrome version V108.
You can refer the below repository for all the Selenium Dev-Tools versions:
https://repo1.maven.org/maven2/org/seleniumhq/selenium/
I checked with Selenium v4.7.2 with Chrome Version 109.0.5414.75 and with the Chromedriver v109.0.5414.74, got the below same warning:
Then I downgraded Chrome browser to v108.0.5359.126, checked with Selenium v4.7.2 and ChromeDriver v108.0.5359.71, this time didn't get the warning:
The next Selenium Dev-Tools version may be released with the next Selenium upgrade.
You can also install Selenium Dev-Tools separately from Maven respository: https://mvnrepository.com/search?q=Selenium+DevTools+V108
Anyway, this is just a warning.
CDP
With the availablity of Selenium v4.0.0.0-alpha-1 the basic support for CDP landed via the "DevTools" interface. Moving ahead, from v4.0.0-alpha-4 onwards Chrome Debugging Protocol commands now mirror latest CDP spec.
This usecase
As you were using ChromeDriver/GoogleChrome combo v109.0, support for it was added recently in Selenium v4.8.0:
v4.8.0
======
* Supported CDP versions: 85, 107, 108, 109
So incase someone tries to use ChromeDriver/GoogleChrome combo v109.0 with Selenium v4.7.2 or earlier, Selenium won't be able to find an exact match for CDP version 109 and would return the closest version found i.e. 108
Hence the warning:
WARNING: Unable to find an exact match for CDP version 109, so returning the closest version found
I am working on a Symfony project in which I need to use Panther for testing.
For that, I need the chromeDriver corresponding to my version of Google Chrome.
Google chrome is up to date in its latest version: Version 88.0.4324.104
So I downloaded the ChromeDriver corresponding to version 88 of google chrome, on the ChromeDriver download site: https://chromedriver.chromium.org/downloads
Now when I run the tests with this version of ChromeDriver I get the following error:
Facebook\WebDriver\Exception\SessionNotCreatedException : session not created: This version of ChromeDriver only supports Chrome version 84
If I run manually the ChromeDriver.exe, I can see : Starting ChromeDriver 88.0.4324.96, so it's the good version
I don't understand why, since I have version 88 of Google Chrome, and the correct version of ChromeDriver
EDIT : Here is the answer :
I had this folder: C:/webdrivers with an old chromeDriver. Panther will first search in this folder, before going to look for the chromeDriver in the project/drivers folder
I had this folder: C:/webdrivers with an old chromeDriver. Panther will first search in this folder, before going to look for the chromeDriver in the project/drivers folder
I am trying to find out what is the latest JDK level supported by TomEE 8 or 9. Specifically if JDK 15 will work. The install documentation says only Java 6 or 7 are supported. That seems a bit too old.
The JDK compatibility and support of TomEE is not well documented. The "java compatibility" note in the official documentation is outdated. The Java versions mentioned in the install documentation are an obsolete minimum requirement - propably a copy & paste thingy.
Here is what is known:
TomEE 8.0.9 definitely supports JDK 8, JDK 11, JDK 17
From a short stackoverflow research, for some users JDK 14 or JDK 15 also worked
TomEE 9.x does only support the Jakarta namespace (Jakarta EE 8, Jakarta EE 9.x)
Watch the Release Notes for updates.
According to this documentation page only JDK 8 is supported by TomEE 8.
I heard Google is having plans to support ORTC standards from version 38 or 39, but haven't seen any confirmation on it.
https://bloggeek.me/google-roadmap-webrtc/
This was on the roadmap but did not happen.
Programmatically , you can check for the existence of the RTCRtpSender object. It's not there in the canary version (43 as of today) of chrome even.
Looking at Platforms Supported by Selenium the highest version of selenium supported is v 10. I am assuming this is in line with 10 being the current extended support release, v17 is the next ESF, due out on 20 Nov 2012
Firefox extended suport
Firefox release calendar
However looking at the release notes for the Selenium client driver 2.25 (18 July 12) it says "Updated supported versions of Firefox to 17"
Which page should we read? How does the Platforms Supported by Selenium page relate to the 2.2.5 release?
You should refer to CHANGELOG. Thats always the latest. Seleniumhq.org gets updated by someone manually... Which is not happening regularly I guess.
I use selenium 2.25 and I had to download to Firefox version 14 in order to get selenium to work correctly.
Other people have documented this issue but I haven't found any resources that say what versions of Firefox are supported for each version of selenium.
selenium-firefox-driver 2.25.0 not working correctly with Firefox 15
Also if you are using selenium with your web browser you are going to have to turn off automatic updates on your browser to prevent it from updating.