ChromeDriver 111.0.5563.64 has been released

[Vladimir Nechaev]

Hello ChromeDriver users,

We are happy to announce that ChromeDriver version 111.0.5563.64 has been released, and is now available at the ChromeDriver Downloads site. This version of ChromeDriver is intended for users of the current Stable release of Chrome version 111.

Changes in this version of ChromeDriver include:

• Resolved issue 4216: Run ChromeDriver with custom BiDiMapper [Pri-]

• Resolved issue 4300: Window handle is interoperable between Classic and BiDi [Pri-]

• Resolved issue 4325: Handling of toJSON in jsonSerialize of call_function.js deviates from the standard. [Pri-]

• Resolved issue 4330: DCHECK fails at DevToolsClientImpl::AddListener [Pri-]

• Resolved issue 4357: ChromeDriver session issue with --headless and --user-data-dir options [Pri-1]

Please see the release notes 111.0.5563.64 for a more complete list of changes included in this release.

Thanks for your continued support of ChromeDriver, and please let us know if you have any questions.

Sincerely,

The ChromeDriver Team

[sharanaprasad Mailar]

Hello Vladimir,

I am getting Error when I update this chrome driver 

Starting ChromeDriver 111.0.5563.64 (c710e93d5b63b7095afe8c2c17df34408078439d-refs/branch-heads/5563@{#995}) on port 6420
Only local connections are allowed.
Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
ChromeDriver was started successfully.
Mar 08, 2023 2:16:44 PM org.openqa.selenium.remote.http.WebSocket$Listener onError
WARNING: Invalid Status code=403 text=Forbidden
java.io.IOException: Invalid Status code=403 text=Forbidden
        at org.asynchttpclient.netty.handler.WebSocketHandler.abort(WebSocketHandler.java:92)
        at org.asynchttpclient.netty.handler.WebSocketHandler.handleRead(WebSocketHandler.java:118)
        at org.asynchttpclient.netty.handler.AsyncHttpClientHandler.channelRead(AsyncHttpClientHandler.java:78)
        at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444)
        at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
        at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)
        at io.netty.channel.CombinedChannelDuplexHandler$DelegatingChannelHandlerContext.fireChannelRead(CombinedChannelDuplexHandler.java:436)
        at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:346)
        at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:333)
        at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:454)
        at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:290)
        at io.netty.channel.CombinedChannelDuplexHandler.channelRead(CombinedChannelDuplexHandler.java:251)
        at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:442)
        at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
        at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)
        at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410)
        at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:440)
        at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
        at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919)
        at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:166)
        at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:788)
        at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724)
        at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650)
        at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562)
        at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
        at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
        at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
        at java.lang.Thread.run(Thread.java:750)

org.openqa.selenium.remote.http.ConnectionFailedException: Unable to establish websocket connection to http://localhost:50317/devtools/browser/d3b31d03-6922-4155-a0fe-8bbb94188109
Build info: version: '4.8.0', revision: '267030adea'
System info: os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_331'
Driver info: driver.version: ChromeDriver
        at org.openqa.selenium.remote.http.netty.NettyWebSocket.<init>(NettyWebSocket.java:102)
        at org.openqa.selenium.remote.http.netty.NettyWebSocket.lambda$create$3(NettyWebSocket.java:128)
        at org.openqa.selenium.remote.http.netty.NettyClient.openSocket(NettyClient.java:107)
        at org.openqa.selenium.devtools.Connection.<init>(Connection.java:78)
        at org.openqa.selenium.chromium.ChromiumDriver.lambda$new$2(ChromiumDriver.java:116)
        at java.util.Optional.map(Optional.java:215)
        at org.openqa.selenium.chromium.ChromiumDriver.<init>(ChromiumDriver.java:114)
        at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:82)
        at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:71)
        at Genericlibrary.Base.launchApp(Base.java:146)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:124)
        at org.testng.internal.MethodInvocationHelper.invokeMethodConsideringTimeout(MethodInvocationHelper.java:59)
        at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:458)
        at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:222)
        at org.testng.internal.Invoker.invokeMethod(Invoker.java:523)
        at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:719)
        at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:989)
        at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
        at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:750)

[Sebastian Richter]

here the same with ChromeDriver 111.0.5563.64

and Chrome or Chromium 111.0.5563.64

org.openqa.selenium.remote.http.ConnectionFailedException: Unable to establish websocket connection to http://localhost:51782/devtools/browser/63aa4853-8704-4ea3-aa0b-9240d03304e1

after

Starting ChromeDriver 111.0.5563.64 (c710e93d5b63b7095afe8c2c17df34408078439d-refs/branch-heads/5563@{#995}) on port 3136

[WARN][AsyncHttpClient-1-14][org.openqa.selenium.remote.http.WebSocket$Listener.onError] Invalid Status code=403 text=Forbidden

[Manjunath Attili]

Adding the below worked with v111 Chromedriver. But is there a fix coming in so that we need not make this change in all existing scripts ? Please let us know.

ChromeOptions ops = new ChromeOptions();

ops.addArguments("--remote-allow-origins=*");

[Sebastian Richter]

Titus Fortner

ungelesen,

08.03.2023, 18:55:18 (vor 15 Stunden) 

an ChromeDriver Users

TL;DR

1. If you are Java 11+ please use the new HTTP Client
2. Selenium will add this parameter to the Chrome service class by default for Java < 11 users (we already do this for Firefox); It will be in Selenium 4.9
3. If you can't update to Selenium 4.9 (when we release it) and can't upgrade to Java 11, you'll need to use: chromeOptions.addArguments("--remote-allow-origins=*")

[Faizan Mamji]

Hello Everyone,

I have upgraded Java to 15 version.
Browser launching successfully for me if i am not using headless.

But when i am trying with headless it doesn't work for me.
Getting this below error.
Can anyone please help me to resolve this issue?

For reference i am adding the code as well.

public WebDriver launchWebBrowser(String browserName, String appUrl) { System.setProperty("webdriver.http.factory", "jdk-http-client"); DesiredCapabilities capss = new DesiredCapabilities(); ChromeOptions options = new ChromeOptions(); try { options.setAcceptInsecureCerts(true); options.setExperimentalOption("excludeSwitches", Arrays.asList("test-type")); options.addArguments("--headless=new"); options.addArguments("--disable-web-security"); options.addArguments("--no-sandbox"); options.addArguments("start-maximized"); options.addArguments("--disable-dev-shm-usage"); options.addArguments("--disable-gpu"); options.addArguments("--print-to-pdf"); options.addArguments("--allow-running-insecure-content"); capss.setCapability(ChromeOptions.CAPABILITY, options); capss.setCapability(CapabilityType.ACCEPT_INSECURE_CERTS, true); options.merge(capss); if (browserName.equalsIgnoreCase("chrome")) { WebDriverManager.chromedriver().setup(); driverWeb = new ChromeDriver(options); } else if (browserName.equalsIgnoreCase("firefox")) { WebDriverManager.firefoxdriver().setup(); driverWeb = new FirefoxDriver(); } driverWeb.navigate().to(appUrl); driverWeb.manage().window().maximize(); System.out.println("Browser size is " + driverWeb.manage().window().getSize()); tWdriver.set(driverWeb); driverWeb.manage().timeouts().implicitlyWait(Duration.ofSeconds(Integer.parseInt(PropertyReader.getConfigValue(configFile, "implicitWait")))); } catch (Exception ex) { Assert.fail("Issue in launching browser - " + ex.getMessage()); } return driverWeb; } **Error I am Getting when running headless** Starting ChromeDriver 111.0.5563.64 (c710e93d5b63b7095afe8c2c17df34408078439d-refs/branch-heads/5563@{#995}) on port 36269 Only local connections are allowed. Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe. ChromeDriver was started successfully. Mar 13, 2023 9:47:38 AM org.openqa.selenium.devtools.CdpVersionFinder findNearestMatch WARNING: Unable to find an exact match for CDP version 111, so returning the closest version found: 110 junit.framework.AssertionFailedError: Issue in launching browser - no such window: target window already closed from unknown error: web view not found (Session info: chrome=111.0.5563.64) Build info: version: '4.8.1', revision: '8ebccac989' System info: os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.16', java.version: '15.0.2' Driver info: org.openqa.selenium.chrome.ChromeDriver Command: [8f586fb87f597bc9007bdb76dfbe218b, get {url=https://test-caseworker-portal.platform.rer.dev/}] Capabilities {acceptInsecureCerts: true, browserName: chrome, browserVersion: 111.0.5563.64, chrome: {chromedriverVersion: 111.0.5563.64 (c710e93d5b63..., userDataDir: /var/folders/v8/mrd778lx16n...}, goog:chromeOptions: {debuggerAddress: localhost:54038}, networkConnectionEnabled: false, pageLoadStrategy: normal, platformName: MAC, proxy: Proxy(), se:cdp: ws://localhost:54038/devtoo..., se:cdpVersion: 111.0.5563.64, 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} Session ID: 8f586fb87f597bc9007bdb76dfbe218b Please suggest the workaround for headless.

[Dhaval Dosi]

Here's fix 

WebDriverManager.chromedriver().setup();

ChromeOptions options = new ChromeOptions();

options.addArguments("--remote-allow-origins=*");
DesiredCapabilities cp = new DesiredCapabilities();
cp.setCapability(ChromeOptions.CAPABILITY, options);
options.merge(cp);
driver = new ChromeDriver(options);

[Harnek Singh]

Hi,

Has ChromeDriver 112.xxx been released yet? I can't find it and we have a limited set of test PCs that received Chrome ver 112. The vast majority as fortunately still at ver 111.

I have searched under stable and beta releases of ChromeDriver and can't find any mention of ver 112 - just ver 111 as the latest available. Although we don't use canary builds, there is also no ver 112 in there as well.

As a work around we are able to use using the latest ver 111 ChromeDriver with Chrome ver 112 successfully at the moment but it is not ideal. Luckily, we have a in-house test framework build (C#/.NET based) which dynamically checks the current installed browser version and copies  down the correct major version matching chromedrivers from a shared local store. That store has been pre-populated and maintained  by a scheduled daily process searching for latest releases for the latest 4 major version numbers of chromedriver from the production and beta releases. So we were able to fake it for now by copying the latest chromedriver 111 as 112 to our shared local store. This is obviously a temporary (and icky) solution.

Does anyone know why ChromeDriver 112 is not out?

Regards,

Harnek

[Ferdy Ciputra]

Hello,
I am use chrome browser version 111.0.5563.65

I am getting Error with details as below:

Starting ChromeDriver 111.0.5563.64 (c710e93d5b63b7095afe8c2c17df34408078439d-refs/branch-heads/5563@{#995}) on port 27559

Only local connections are allowed.
Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
ChromeDriver was started successfully.

Mar 15, 2023 2:43:22 PM org.openqa.selenium.remote.http.WebSocket$Listener onError

WARNING: Invalid Status code=403 text=Forbidden
java.io.IOException: Invalid Status code=403 text=Forbidden

Can anyone please help me to resolve this issue?

[Harnek Singh]

Update - Chrome Webdriver ver 112 just released in last few hours.

[전금례]

111.0.5563.111버젼을 내줘!

2023년 3월 8일 수요일 오후 3시 10분 17초 UTC+9에 Vladimir Nechaev님이 작성: