ChromeDriver 103.0.5060.53 has been released

[Vladimir Nechaev]

Hello ChromeDriver users,

We are happy to announce that ChromeDriver version 103.0.5060.53 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 103.

Changes in this version of ChromeDriver include:

• Resolved issue 4048: target frame detached [Pri-]

Please see the release notes 103.0.5060.53 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

[Funda C]

Hi The ChromeDriver Team

Now target frame issue is solved via 103 version but observed recently another two issues which are happen randomly 

1. unknown error: cannot determine loading status
2. unknown error: unexpected command response 

Could you advise us what should be the solution please?

Does down grade driver version solve the issue?

Thank you

[Vladimir Nechaev]

Dear Funda,

These issues are addressed in ChromeDriver 104 Beta that is going to be released on Friday 24.06.2022.

Best regards,
Vladimir

--
You received this message because you are subscribed to the Google Groups "ChromeDriver Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromedriver-us...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/20dea591-c954-42a5-95e7-f649b1703cf9n%40googlegroups.com.

[Toddler Cartoons]

Hi,

I am also having the same issue, when it navigate the url it fails.
When it will only be fixed in 104 then ChromeDriver 103.0.5060.53 is pretty useless. Its an intermittent issue, but its like 9 out of 10 attempts that get this error.
Many of my customers auto update to Chrome 103 which causes me a big headache as the software I build will stop working when they do.

For reference, the error:

unknown error: cannot determine loading status

from unknown error: unexpected command response
  (Session info: chrome=103.0.5060.53)

WebDriverException:    at OpenQA.Selenium.WebDriver.UnpackAndThrowOnError(Response errorResponse)
   at OpenQA.Selenium.WebDriver.Execute(String driverCommandToExecute, Dictionary`2 parameters)
   at OpenQA.Selenium.WebDriver.set_Url(String value)
   at OpenQA.Selenium.Navigator.GoToUrl(String url)

[Avinash Bhandari]

At what time fix will deploy tomorrow?

[Татьяна Максюк]

Hi all. When will the release be added to https://mvnrepository.com/artifact/io.github.bonigarcia/webdrivermanager?
Thank you.

пʼятниця, 24 червня 2022 р. о 08:38:47 UTC+3 Avinash Bhandari пише:

[Linda Fukuyu]

selenium.common.exceptions.WebDriverException: Message: unknown error: unexpected command response
  (Session info: chrome=103.0.5060.53)

[Ian Fischer]

same issue.  it seems that It happens when I have chrome driver click a login button.

[Sagar Ghodke]

facing same issue

[Vennela vinay]

Please fix this ASAP. This is breaking each and every test run

[Christopher Hagler]

 Hello ChromeDriver Team! Are there plans to push the fix into the latest version of Chrome(103)? Or are you planning to only have in 104; and if so, can you please push 104 as latest chrome asap? This is causing a major issue for anyone using selenium for their automated test solution. Thanks in advance!

Chris

[prashant chaudhary]

Hi TheChromeDriver  Team,

I am also getting the below errors in ChromeDriver version 103, These issues are coming randomly in all framework.

1. unknown error: cannot determine loading status
2. unknown error: unexpected command response 

Could you advise us on what should be the solution, please?

Thanks,

Prashant Chaudhary

[Ricardo Carneiro]

Hi folks,

We all know that we are getting random weird issues. Is it possible to release v103.0.5060.66, the same version as Chrome for the Chrome WebDriver to tackle those issues?

Thanks,

Ricardo

[Joseph Lust]

Any update here on the suggested work around? I saw it mentioned to try using the 104 Chromedriver build.

We've tried using Chromedriver `104.0.5112.20` and Chrome `103.0.5060.53`, but keep getting 

> org.openqa.selenium.SessionNotCreatedException: session not created: This version of ChromeDriver only supports Chrome version 104

What's the recommended way to run Se tests against Chrome 103?

Thanks,

Joe

[Fernando Martínez]

Hello everyone,

Same issue here, getting unknown error: unexpected command response on different parts of the tests.

Thanks,

Fernando

[Salma Shaikh]

Hi, I tried using ChromeDriver 104 but that doesnt work either.

[Ching-Yi Chan]

I also got the same problem. My work around is downgrade to order versions.

But the archives for older versions are not easy to find. I use yarn/npm to download a old version.

Check the version mapping between puppeteer and chromium

https://github.com/puppeteer/puppeteer/blob/v15.1.1/versions.js#L22

```

yarn add pupp...@14.0.0

```

You will get a chromium app

```

$ find . -name "Chromium"
./node_modules/puppeteer/.local-chromium/mac-991974/chrome-mac/Chromium.app/Contents/MacOS/Chromium

```

Get the suitable driver and configure binary_location in Options. Everything is working.

Salma Shaikh 在 2022年6月29日 星期三凌晨2:23:46 [UTC+8] 的信中寫道：

[candela ayala]

Hello everyone, any updates on the fix for this bug yet?

I still get this message everytime my tests open a URL:

"selenium.common.exceptions.WebDriverException: Message: unknown error: unexpected command response" 

[Jan Hansen]

Hello ChromedriverTeam.

Thank you for your commitment and work on Chromedriver which we all enjoy and benefit from.

However a lot of your customers are now are facing the "unexpected command response" and "cannot determine loading status". Including me. A rare showstopper.

Since you seem to have a solution implemented in Chromedriver 104 please implement this on an update to Chromedriver 103. This would help a lot of people.

Thank you

/Jan

[Paulo Silveira]

I USE A VBA CODE. THE CHROME VERSION IS 103.0.5060.66 AND THE LAST OF SEQUENCE 103 IN THE CHROME DRIVER IS 103.0.5060.53. WHEN SWITCHING TO NEXT TO 104.0.5112.20 GIVES ERROR BECAUSE IT IS A BETA VERSION. WHAT TO DO ?

[Pankaj Negi]

ChromeDriver - 103.0.5060.66 this version -  Version 103.0.5060.66 (Official Build) (64-bit)

[Sanket Mahajan]

Here is the work around -

1) Uninstall existing Google Chrome browser version 103.X.XX  and Chrome driver version 104.X.XXX

2) Install Beta version for Chrome 104 from below link
Link - https://www.google.com/chrome/beta/?visit_id=637920916445954043-3375103102&p=betadesktop&rd=1
3) Go to C:\Program Files\Google and delete "Chrome" folder and rename "Chrome Beta" folder to "Chrome"
4) Kill chromedriver.exe and Google Chrome tasks from Task Manager

5) Once chrome browser version 104 move out from beta phase, we have to delete the beta version and reinstall the Chrome browser.

Thanks & Regards,
----------------------------------
Sanket N. Mahajan
Mobile: 91-98813-73864
Email: sank...@gmail.com

--
You received this message because you are subscribed to the Google Groups "ChromeDriver Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromedriver-us...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/b4ab8acd-e239-4288-a201-11f022d168b5n%40googlegroups.com.

[Sanket Mahajan]

Please read as "Install  Chrome driver version 104.X.XXX  " in point#1 :)

Thanks & Regards,
----------------------------------
Sanket N. Mahajan
Mobile: 91-98813-73864
Email: sank...@gmail.com

[Jesse Brown]

I'm sorry but you screwed the pooch with the release of 103.xxx

To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/CAFC46zmyGcnas6gQVTSY1hT1hmDOMegu5n5QwyrpH4zNQZD3Ug%40mail.gmail.com.

[Joseph Shi]

Hi CD team, 

we met the same and negative impacting is huge right now. 

Could you please share any workaround here? or other contingent plan? 

Thanks for your time. 

[John Collins]

This really caused me a headache. I've now been forced to downgrade to Chrome version 102.0.5005.63. Hope there will be a fix soon. Thank you.

[younas rehman]

To overcome this issue you need to run in chrome browser in headless mode or use  DriverManager().

options.AddArgument("headless");
or
new DriverManager().SetUpDriver(new ChromeConfig(), VersionResolveStrategy.MatchingBrowser);

[Sarah Saad]

Hi, I am getting the error below when trying to go to a URL

await this.driver.get(appUrl);

 WebDriverError: unknown error: net::ERR_NAME_NOT_RESOLVED
         (Session info: chrome=103.0.5060.53)
           at Object.throwDecodedError (/Users/SSD25/repos/core-video-sdk-js/reference-app/node_modules/selenium-webdriver/lib/error.js:517:15)
           at parseHttpResponse (/Users/SSD25/repos/core-video-sdk-js/reference-app/node_modules/selenium-webdriver/lib/http.js:655:13)
           at Executor.execute (/Users/SSD25/repos/core-video-sdk-js/reference-app/node_modules/selenium-webdriver/lib/http.js:581:28)
           at processTicksAndRejections (node:internal/process/task_queues:96:5)
           at async mixin.execute (/Users/SSD25/repos/core-video-sdk-js/reference-app/node_modules/selenium-webdriver/lib/webdriver.js:724:17)
           at async World.<anonymous> (/Users/SSD25/repos/core-video-sdk-js/reference-app/feature_tests/support/applicationSteps.js:36:5)

[Felipe Whitaker]

Following  Sanket N. Mahajan's workaround, you can:

1)  Install Chrome driver version 104.X.XXX
2) Install Beta version for Chrome 104 from https://www.google.com/chrome/beta/?visit_id=637920916445954043-3375103102&p=betadesktop&rd=1
3) Make your program use chrome driver version 104.X.XXX and the binary of Chrome Beta (on Windows it is  C:\Users\YOUR-USERNAME-HERE\AppData\Local\Google\Chrome Beta\Application\chrome.exe)

On  python, that would be:

from selenium.webdriver.chrome.options import Options
from webdriver_manager.chrome import ChromeDriverManager # !pip install webdriver-manager

chrome_options = Options()
# ... add options
user = os.environ.get("USERNAME") # get current Windows user to build up binary path
# set up selenium to use Chrome Beta
# https://www.google.com/chrome/beta/?visit_id=637920916445954043-3375103102&p=betadesktop&rd=1 as its binary
chrome_options.binary_location = rf"C:\Users\{user}\AppData\Local\Google\Chrome Beta\Application\chrome.exe"
# define `driver`
driver = webdriver.Chrome(
    ChromeDriverManager(
        version = "104.0.5112.20", # keep driver version constant
        cache_valid_range=0.5
    ).install(),
    options=chrome_options,
)

[Tú Đỗ Văn Thanh]

HI mate,

Chrome 103 is updated to 103.0.5060.114

Could you please update chromedriver version?

I'm using macbook M1 pro, forgot to turn off auto update chrome.

How can I resolve the issue:
Unable to create new service: ChromeDriverService

Warm regards,

TuDVT

Vào lúc 16:03:06 UTC+7 ngày Thứ Tư, 22 tháng 6, 2022, nec...@chromium.org đã viết:

[Pranks Calls]

Beta 104 did the trick for now.

[Jesse Brown]

Actually, I was able to move forward with 103 in c# by treating the exception as evil and ignoring it. The problem I encountered was setting the Url, it was rethrowing a null exception. So I wrapped that one call caught the rethrow with a empty handler and went about my task. It didn't matter to completing my task. Now some might bitch about this but if the error handling is broken the it's usually safe to ignore.

--
You received this message because you are subscribed to the Google Groups "ChromeDriver Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromedriver-us...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/0a04cce0-316d-4071-a962-f1d59a060317n%40googlegroups.com.

[candela ayala]

Hi everyone, 

To anyone who needs a quick workaround until the fix is ready, I was able to run my tests if I put a static wait right before navigating the URL :

import time

time.sleep(5)

driver.get(url)

[Vladimir Nechaev]

Dear ChromeDriver users,

The fix for "unexpected command response" has been submitted to the ChromeDriver 103 branch.
It will be available shortly after the next release of Chrome 103.

Sincerely,
The ChromeDriver Team

To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/92c4ec2f-addb-4a20-b3ae-fba7c1418d19n%40googlegroups.com.

[Space Soft System]

any one help me , i try to update google developer team for using https://github.com/adiwajshing/Baileys in  ChromeDriver

but google developer team not update any type code or he say use node js

any one help me for how i create whatsapp automation using ChromeDriver Visual Basic 2019 

can i send button whatsapp message from ChromeDriver

can i send list / menu message in whatsapp using ChromeDriver

please help me

To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/CAAWap_bdE9kc9HRPpW376bYGnjRRuTqSP66o4XvYt_qotEzz%3Dg%40mail.gmail.com.

--

===============================================
Space Soft System
Software Development Work

Software Sales & Service

www.spacesoft.in

Cell 73546-73546

[Sia Gythfeldt]

When is the new chrome driver 103 released? I can't find anything, but it is really messing with my scripts, that are using environment variables.

[Funda C]

After installing the Chrome Beta and setting the binary of Beta and setting the driver version, all are working fine till this morning!!!

The below new issue observed on my side.

org.openqa.selenium.SessionNotCreatedException: Could not start a new session. Response code 500. Message: session not created
from tab crashed
(Session info: chrome=104.0.5112.48)
Build info: version: '4.2.2', revision: '683ccb65d6'

Starting ChromeDriver 104.0.5112.29

Does anyone faced the same issue? 

[Rathod P]

i am also getting the same issue 
How this issue can be resolved?

On Wednesday, June 22, 2022 at 8:50:16 PM UTC+5:30 Toddler Cartoons wrote:

Hi,

I am also having the same issue, when it navigate the url it fails.
When it will only be fixed in 104 then ChromeDriver 103.0.5060.53 is pretty useless. Its an intermittent issue, but its like 9 out of 10 attempts that get this error.
Many of my customers auto update to Chrome 103 which causes me a big headache as the software I build will stop working when they do.

For reference, the error:

unknown error: cannot determine loading status

from unknown error: unexpected command response
  (Session info: chrome=103.0.5060.53)

WebDriverException:    at OpenQA.Selenium.WebDriver.UnpackAndThrowOnError(Response errorResponse)
   at OpenQA.Selenium.WebDriver.Execute(String driverCommandToExecute, Dictionary`2 parameters)
   at OpenQA.Selenium.WebDriver.set_Url(String value)
   at OpenQA.Selenium.Navigator.GoToUrl(String url)

On Wednesday, June 22, 2022 at 1:34:49 PM UTC+2 nec...@chromium.org wrote:

Dear Funda,

These issues are addressed in ChromeDriver 104 Beta that is going to be released on Friday 24.06.2022.

Best regards,
Vladimir

On Wed, Jun 22, 2022 at 1:28 PM Funda C <fundac...@gmail.com> wrote:

Hi The ChromeDriver Team

Now target frame issue is solved via 103 version but observed recently another two issues which are happen randomly 

1. unknown error: cannot determine loading status
2. unknown error: unexpected command response 

Could you advise us what should be the solution please?

Does down grade driver version solve the issue?

Thank you

On Wednesday, 22 June 2022 at 10:03:06 UTC+1 nec...@chromium.org wrote:

Hello ChromeDriver users,

We are happy to announce that ChromeDriver version 103.0.5060.53 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 103.

Changes in this version of ChromeDriver include:

• Resolved issue 4048: target frame detached [Pri-]

Please see the release notes 103.0.5060.53 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

--
You received this message because you are subscribed to the Google Groups "ChromeDriver Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromedriver-us...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/20dea591-c954-42a5-95e7-f649b1703cf9n%40googlegroups.com.

[Somara Atkinson]

https://bugs.chromium.org/p/chromedriver/issues/detail?id=4121#c50
I found this page, which mentions release dates for chrome version releases. There's a row titled "Next Refresh" with tomorrow's date. Hopefully that means we'll get an update both Chrome browser and Chrome browser tomorrow. https://chromiumdash.appspot.com/schedule

[Thierry Jean-Marie]

It Worked fine until this version! 

My Company installs stable software when it has been tested. We thus run with Chrome and edge 103, I cannot switch the version of these two installation.

However I need to perform Unit and Regression testing with Selenium using the corresponding ChromeDriver and msedgedriver, both of which have a problem with version 103.

Is there a parameter that can be set?

            System.setProperty("webdriver.chrome.driver" or "webdriver.edge.driver", absolutePathOfDriver);

            Class<?> webBrowserClass = Class.forName( "org.openqa.selenium.chrome.ChromeDriver" or "org.openqa.selenium.edge.EdgeDriver"  ); 
            WebDriver webDriver = (WebDriver) webBrowserClass.newInstance();

            webDriver.get(url); CRASHES!!!!!

[Eyal Fridrich]

103.0.5060.134  release today but same issue! please fix it soon

[Adrián Jiménez]

Hi, I used the updated chrome driver 103.5060.114 and i am still getting driver exception

" org.openqa.selenium.WebDriverException: unknown error: cannot determine loading status

from unknown error: unexpected command response

  (Session info: chrome=103.0.5060.114)
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:17:03  "

its easy to reproduce, just create a test where you navigate to different sites and execute the test until you get the exception, i wonder if driver 104 is also buggy

[Todd Ogin]

Confirming for my team that 103.0.5060.114 improved things drastically.

Chromedriver devs - It's frustrating that this was flagged when the issue was originally opened to be impacting 103 and was delayed a whole 103 patch release without making it in, when 104 was released as a beta before then with a fix. I'm not sure how it could have been communicated more clearly. Is there guidance you can provide that can help us understand how to get attention on an issue correctly so it gets patched in the current stable version? Or was this slowed by something other than communication?

For Chromedriver users. For situations like this, there is a "--disable-build-check" flag that you can set to use chromedriver versions  with "incompatible" chrome versions. Obviously this has its own risks and shouldn't be done for an extended period of time. It will output a warning saying as much.

One frustrating thing is that historically this "disable-build-check" flag has been locked down quite a bit. See https://groups.google.com/g/chromedriver-users/c/1GffkCgwgqQ

:

My understanding is that with Selenium 4 Java it is an option, see this code point:

https://github.com/SeleniumHQ/selenium/blob/69f46da9ea12f04cef5e7d990e6ee99593396e73/java/src/org/openqa/selenium/chrome/ChromeDriverService.java#L152

It's controlled through Java properties so you'll need to set it through that. This would work for either a Grid set up or a Local program starting chromedriver through ChromeDriverService.

For C#, there wasn't an option for this other than independently starting a Chromedriver instance. In the next Selenium 4 release however this should be improved: https://github.com/SeleniumHQ/selenium/issues/10898/ My understanding is this should be released in August.

Other language users should consult the documentation for their language and push for this flag to be supported through whatever interface they use which starts the Chromedriver process.