Disconnected: not connected to DevTools

[leishman_keith]

Attempting to launch test case, or browser via object spy, using Chrome and getting the following message…

Caused by: org.openqa.selenium.WebDriverException: disconnected: not connected to DevTools

Searching seems to be some sort of mismatch between chrome and chrome driver versions possibly. I have the latest Chrome and chromeDriver versions as far as I am aware, so off hand I am unsure what the issue is currently.

Browser will launch and then close right away.

What directions should I be looking to sort this out?

Chrome: v114.0.5735.199
chromeDriver: v144.0.5735.90

[Russ_Thomas]

Do this first:

[leishman_keith]

Already did that.

[kazurayam]

@leishman_keith

chromeDriver: v144.0.5735.90

I have a doubt about this.

It could rather be:

chromeDriver: v114.0.5735.90

Can you check this?

ーーーーーーーー

Here is another post about ChromeDriver v114.0.5735.90:

Chrome not reachable ChromeDriver 114.0.5735.90

A quote from https://stackoverflow.com/questions/76562584/unable-to-find-the-latest-chrome-driver-114-0-5735-134 Google recently has changed the build process for Chrome and ChromeDriver. Going forward, all the releases will be available at https://googlechromelabs.github.io/chrome-for-testing/. This is done to steamline the chrome and chrome driver versions. Now each chrome release would have its corresponding same version available. … answered Jun 27 at 13:36 18 July 2023, I looked at http…

It is reported that Chrome 114.0.5735.198 does not work well for testing via WebDriver.

[leishman_keith]

I’ve looked into that but doesn’t seem to be too helpful, will maybe try to roll back chrome to something before that version.

[kazurayam]

See also

Chrome not reachable ChromeDriver 114.0.5735.90

19 July 2023, I revisited the Chrome for Testing availability . I found that Chrome has been updated to a new version 115.0.5790.98. The version is reported to be OK for testing. [Chrome-for-Testing-availability (1)] I happpen to see the progress of Chrome releases. It was a bit of surprise for me. @btl82894 may try upgrading Chrome now. Hopefully it should solve the problem.

[leishman_keith]

Edit: Still seeing the same error after chrome updated to 115, I had to manually install the corresponding driver. Updating the driver via Katalon had an error.

It also displays:
Caused by: org.openqa.selenium.WebDriverException: disconnected: Unable to receive message from renderer

[kazurayam]

I tried “Updating web driver …” for Chrome on my Mac; I encountered a similar error as well.

The message told me that Katalon Studio’s “Updating web driver” feature tried to access https://chromedriver.storage.googleapis.com/

I tried https://chromedriver.storage.googleapis.com/ which responded an XML document where many versions of ChromeDrivers are included. However, the list did not include the version 115.0.5790.00. Therefore I got an error. I understood the reason why I got an error.

But I do not know why the XML list does not include the latest version 115.0.5790.00 yet. The site is managed by Google; I am not in charge of it, of course.

I have no more knowledge about the way how ChromeDriver is distributed.

I will just wait for a few days to see how things change …

[vinayak_joshi1]

@leishman_keith can you try manual workaround mentioned in this earlier post

chromeDriver Upgrade Error

Hi I am currently using Katalon Studio Version - 6.3.3 and My chrome got updated recently from 76 to 78 I am getting “Caused by: org.openqa.selenium.SessionNotCreatedException: session not created: This version of ChromeDriver only supports Chrome version 76 Build info: version: ‘3.141.59’, revision: ‘e82be7d358’, time: ‘2018-11-14T08:25:53’ System info: host: ‘TP120934’, ip: ‘10.6.100.23’, os.name: ‘Windows 7’, os.arch: ‘amd64’, os.version: ‘6.1’, java.version: ‘1.8.0_181’ Driver info: dr…

[leishman_keith]

I did attempt that yesterday with the latetest v115 build that they had released, and that was when the error changed from the DevTools one to the Renderer one, so still some issues with the driver not working right it seems.

[kazurayam]

@leishman_keith

the error changed from the DevTools one to the Renderer one, so still some issues with the driver not working right it seems.

You should report your findings to Google.

[leishman_keith]

For reporting to Chrome, they want the chromeDriver to create the logs with Verbose logging; Logging - ChromeDriver - WebDriver for Chrome (google.com);

I haven’t done much with passing arguments through Katalon so could I get an example of how to set that up right in Katalon?

I assume it would be under Project Settings > Desired Capabilities > Web UI > Chrome?

Edit: I did find this link; How to execute chrome with verbose logging - Product Forums / Katalon Studio - Katalon Community but just want to make sure I do the right arguments and where to find these logs?

[leishman_keith]

Katalon was finally able to update the chromeDriver and the new error is “unknown error: cannot find Chrome binary”. If thats the path to the driver, then it is still the same defaulted folder for that and I confirmed the chromeDriver file in there was from when I updated it via Katalon.

[dineshh]

local webdriver or remote webdriver?

[h.kramer]

I have the same error on my local machine. There is no problem on the server. How can this be solved?

[leishman_keith]

Should be the local webdriver.

Checked the version’s again, chrome is still the same and updating chromeDriver via Katalon showed the previous error with 115 not being available. Chome binary’s error is persisting.

[leishman_keith]

I was noticing when looking at the Log Viewer that it shows Chrome’s version as 115.0.0.0. Is this something that could be causing this issue? Chromes actual version is 115.0.5790.110.

[kazurayam]

See my new post:

As of Chrome 115, Tools > Update WebDrivers > Chrome no longer works

I have got Chrome browser autoupdated to the latest v115.x.x.x [スクリーンショット 2023-07-27 8.11.51] When I tried in Katalon Studio “Tools > Update WebDrivers > Chrome”, I got the following output [スクリーンショット 2023-07-27 8.13.50] [ERROR] Error HTTP 404 executing https://chromedriver.storage.googleapis.com/LATEST_RELEASE_115 [WARN] Exception reading https://chromedriver.storage.googleapis.com/LATEST_RELEASE_115 to get latest version of chromedriver (Error HTTP 404 executing https://chromedriver.stor…

As far as I see, Katalon Studio’s “Tools > Update WebDriver > Chrome” no longer works for Chrome v115.x and newer. You need to update ChromeDriver manually or invent a wheel for yourself.

[Elly_Tran]

Hi,

Katalon has acknowledged the issue and working on it. In the meanwhile, we suggest some actions: As of Chrome 115, Tools > Update WebDrivers > Chrome no longer works - #6 by Elly_Tran. Thank you!

[leishman_keith]

I have tried to update chome and chromedriver via the PDF link (How to use Chrome for Testing in Katalon Studio) that @Elly_Tran shared in the linked post…

I downloaded the chrome and chromedriver files utilizing npx…attempted with Stable version 115 and Beta version 116…copied the chrome/chromedriver files to the indicated locations via that PDF…updated the binary source in Katalon’s project settings for DesiredCapabilities>WebUI>Chrome.

When trying with the beta version 116…Katalon still launches the 115 version chromeDriver even though I replace all files both in project\include\driver folder as well as Katalon’s configuration\resources\drivers folder with the 116 version, so idk where it is pulling the 115 driver version from.

When trying with v116, katalon gives an error that the driver 115 isn’t tested with version 116 chrome, even though v116 driver should be installed, it is somehow not targeted properly?!?! It appears to still be having the “Unable to receive message from renderer” error.

When trying to run with 115 for both chrome and chromedriver…I receive the error: “disconnected: Unable to receive message from renderer (failed to check if window was closed: disconnected: not connected to DevTools)”

Error log in attached text file.

I don’t understand how to resolve this in lieu of Katalons 9.0.0 update which was mentioned wont be until sometime in September. This has stopped all productivity on my end to the point that Katalon Studio is no longer a viable solution to my project and I have to now look into other means of Automation Testing and cease using Katalon which is very problematic.

chromeError.txt (11.9 KB)