WebDriver Not Compatible with Chrome/65.0.3325.146 on LINUX

[dipesh17]

Meta -

OS: LINUX
Selenium Version: 3 .7. 1
Browser:
Chrome/65.0.3325.146

-->

Browser Version:
Chrome/65.0.3325.146 (64-bit)

Expected Behavior -

Webdriver should be able to click on webelement

Actual Behavior -

Test Failed: org.testng.TestException: The following element is not clickable: [[[ChromeDriver: chrome on LINUX (d03e89e10987409f7705777f68e0204c)] -> id: topbar__login]]

searchFuncationality Test Failed: org.openqa.selenium.WebDriverException: unknown error: call function result missing 'value' (Session info: chrome=65.0.3325.146) (Driver info: chromedriver=2.33.506092 (733a02544d189eeb751fe0d7ddca79a0ee28cce4),platform=Linux 3.10.0-693.2.2.el7.x86_64 x86_64) (WARNING: The server did not provide any stacktrace information) Command duration or timeout: 0 milliseconds Build info: version: '3.7.1', revision: '8a0099a', time: '2017-11-06T21:01:39.354Z' System info: host: 'ip-10-30-74-198.eu-west-1.compute.internal', ip: '10.30.74.198', os.name: 'Linux', os.arch: 'amd64', os.version: '3.10.0-693.2.2.el7.x86_64', java.version: '1.8.0_152' Driver info: org.openqa.selenium.chrome.ChromeDriver Capabilities {acceptSslCerts: true, applicationCacheEnabled: false, browserConnectionEnabled: false, browserName: chrome, chrome: {chromedriverVersion: 2.33.506092 (733a02544d189e..., userDataDir: /tmp/.org.chromium.Chromium...}, cssSelectorsEnabled: true, databaseEnabled: false, handlesAlerts: true, hasTouchScreen: false, javascriptEnabled: true, locationContextEnabled: true, mobileEmulationEnabled: false, nativeEvents: true, networkConnectionEnabled: false, pageLoadStrategy: normal, platform: LINUX, platformName: LINUX, rotatable: false, setWindowRect: true, takesHeapSnapshot: true, takesScreenshot: true, unexpectedAlertBehaviour: , unhandledPromptBehavior: , version: 65.0.3325.146, webStorageEnabled: true} Session ID: 56e57cfa83a7d0ff79500c238608a779

addProductToCart Test Failed: org.testng.TestException: The following element is not clickable: [[[ChromeDriver: chrome on LINUX (f10c1eab1c3034045e01555ef00bef63)] -> css selector: .product-item-link]]

Steps to reproduce -

Pre-requisite: setup a Linux OS and Chrome/65.0.3325.146 (64-bit)

Create a selenium script to perform click operation.

NOTE:

Chrome/65.0.3325.146 (64-bit) and MAC OS: test suite is working as expected on MAC OS.

[cgoldberg]

you need to upgrade chromedriver to version 2.36 to use Chrome 65

[EllaVader]

upgrading chrome driver to version 2.36 doesn't fix it. Also seeing the problem on Windows 10

[bolmaster2]

Chrome 65 should not be compatible with chromedriver 2.33 💔

I found the release notes a kinda easy overview to see which versions are compatible: https://chromedriver.storage.googleapis.com/2.36/notes.txt

[GeorgeKaraszi]

I'm seeing similar issue's too.

I've had to downgrade to v2.34

          Selenium::WebDriver::Error::SessionNotCreatedError:
            session not created exception: Chrome version must be >= 63.0.3239.0
              (Driver info: chromedriver=2.36.540471 (9c759b81a907e70363c6312294d30b6ccccc2752),platform=Linux 4.14.12-041412-generic x86_64)

[EllaVader]

Additionally -- this banner is now a back: "Chrome is being controlled by automated test software" and doing this
chromeOptions.AddArgument("--disable-infobars");
doesn't supress it anymore like it used to.

[cgoldberg]

@EllaVader the --disable-infobars flag was removed from Chrome 65.

[dipesh17]

@cgoldberg

• I've tried upgrading the Chrome driver 2.36 on the Linux operating system, however, I am having test failures and reason, "Element not clickable"
• Tried with headless and normal chrome browser

[herrtunante]

I have also had problems using the CSS selectors to find elemenets (RemoteWebDriver) when upgrading to 2.36 (due to the Chrome 65 update which broke my previous integration with 2.33 )
I moved to 2.35 instead and now everything is working...

[barancev]

For issues please provide a concise reproducible test case and describe what results you are seeing and what results you expect.

See CONTRIBUTING.md

[tmertens]

I'm seeing a possibly related issue where for Chrome headless v65 on linux, capybara-webkit / selenium-webdriver is reporting elements as non-visible when they are not on the visible portion of the page displayed in the viewport. You must scroll them into view for them to be considered "visible" by the driver:

(scroll_to taken from: https://stackoverflow.com/a/38085926)

def scroll_to(element)
  script = <<-JS
    arguments[0].scrollIntoView(true);
  JS
  Capybara.current_session.driver.browser.execute_script(script, element.native)
end

top_of_page_element.visible? #=> true
bottom_of_page_element.visible? #=> false, bottom of page is scrolled out of view
scroll_to(bottom_of_page_element)
# Visibility is now reversed, the element at the top of the page is scrolled out of the viewport and reported as non-visible:
top_of_page_element.visible? #=> false
bottom_of_page_element.visible? #=> true

Tested with selenium-webdriver 3.10.0 and google-chrome-stable (65.0.3325.146-1) on Debian GNU/Linux 8.9 (jessie)

[EllaVader]

@cgoldberg Regarding the --disable-infobars flag being removed from Chrome 65, what are we supposed to use in it's place to remove that banner?

[tmertens]

@EllaVader that is unrelated to the original topic, you should open a separate ticket for discussion.

[lmtierney]

@EllaVader that is a question for the chromium/chrome people. That flag is only passed through selenium.

[kpmueller]

we are also seeing weird elements not being visible with chrome 65 and chromedriver 2.36

[cgoldberg]

if you are having issues with chromedriver, you should submit them to the chromedriver tracker.

and when you do... please be much more descriptive than "seeing weird elements not being visible"

[tmertens]

I am seeing the same behavior with headless firefox v58.0.1 selenium-webdriver (3.9.0 & 3.10.0) on Debian GNU/Linux 8.9 (jessie) and geckodriver-v0.19.1

(edit: tested using the same steps as my previous comment)

[tmertens]

This also appears to affect non-headless chrome v65.

[erajkovic]

Also having issues to get the latest combination to run on Linux - here is the output with my current config:

org.openqa.selenium.WebDriverException: unknown error: unhandled inspector error: {"code":-32000,"message":"Cannot navigate to invalid URL"}
  (Session info: chrome=65.0.3325.146)
  (Driver info: chromedriver=2.36.540471 (9c759b81a907e70363c6312294d30b6ccccc2752),platform=Linux 4.9.60-linuxkit-aufs x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 0 milliseconds
Build info: version: '3.11.0', revision: 'e59cfb3', time: '2018-03-11T20:26:55.152Z'

[barancev]

Please stop writing about all chrome-related problems to the same issue report!

Also, for issues please provide a concise reproducible test case and describe what results you are seeing and what results you expect.

[sbartoloti]

I'm getting this error when I try to run test on linux, did anyone found a solution for this?

Test started: Check user account name [Ljava.lang.StackTraceElement;@1ab06251 null unknown error: unknown sessionId (Session info: chrome=65.0.3325.146) (Driver info: chromedriver=2.36.540471 (9c759b81a907e70363c6312294d30b6ccccc2752),platform=Linux 4.13.0-1008-gcp x86_64) (WARNING: The server did not provide any stacktrace information) Command duration or timeout: 0 milliseconds Build info: version: '3.8.1', revision: '6e95a6684b', time: '2017-12-01T18:33:54.468Z' System info: host: 'runner-7899691b-project-5528664-concurrent-065n6r', ip: '10.124.1.167', os.name: 'Linux', os.arch: 'amd64', os.version: '4.13.0-1008-gcp', java.version: '1.8.0_151' Driver info: org.openqa.selenium.remote.RemoteWebDriver Capabilities {acceptInsecureCerts: false, acceptSslCerts: false, applicationCacheEnabled: false, browserConnectionEnabled: false, browserName: chrome, chrome: {chromedriverVersion: 2.36.540471 (9c759b81a907e7..., userDataDir: /tmp/.org.chromium.Chromium...}, cssSelectorsEnabled: true, databaseEnabled: false, handlesAlerts: true, hasTouchScreen: false, javascriptEnabled: true, locationContextEnabled: true, mobileEmulationEnabled: false, nativeEvents: true, networkConnectionEnabled: false, pageLoadStrategy: normal, platform: LINUX, platformName: LINUX, rotatable: false, setWindowRect: true, takesHeapSnapshot: true, takesScreenshot: true, unexpectedAlertBehaviour: , unhandledPromptBehavior: , version: 65.0.3325.146, webStorageEnabled: true, webdriver.remote.sessionid: 5728a4d1fc2cdf2d21fac5874c3...} Session ID: 5728a4d1fc2cdf2d21fac5874c30ac47

before chrome update, everything was fine... please help?

[erajkovic]

Sorry, I was assuming that my issue was the same or related, as I was using the same version - chrome=65.0.3325.146 / chromedriver=2.36.540471
In my case, it turn out that some other code path was still running with 2.33 - Sorry for getting overloaded info in the thread.

[Lupeipei]

I have got an error: unknown error: call function result missing 'value'.
my headless chrome version 65.0.3325.162, and chrome driver version 2.34.522932. After google around, I upgrade the chrome driver to 2.36, but it's still not working. can anyone give an suggestion?

[alippai]

@Lupeipei It seems if the function result is void, ChromeDriver 2.36 returns the Success response with no 'value' field. Just add the extra check for the existence of the field.

[Lupeipei]

@alippai Thanks for your help! I really appreciate it.
I have figured it out yesterday. I have mistaken the version. I thought I have upgraded chrome driver successfully, but actually, I haven't. the old version is still there. After upgrading, everything is ok now.

[bedus-creation]

Chrome and chromedriver should have matched version.

for example :

Chrome driver 2.37 Supports Chrome v64-66
Chrome driver 2.36 Supports Chrome v63-65
For more Details go to

https://sites.google.com/a/chromium.org/chromedriver/downloads

In your case You are using chrome 65 and driver 2.35 so you need to update driver to

2.36

Steps:-

Go to https://chromedriver.storage.googleapis.com/index.html?path=2.36/ and download chrome driver .
Now extract the chromedriver and replace the driver inside of /path-to-your-project/vendor/laravel/dusk/bin/chromedriver-linux (Incase of linux)
Now Its done .
https://aammui.com/question/cannot-set-property-value-of-null-laravel-dusk

[Lupeipei]

@bedus-creation got it! Thanks a lot!

[Shubham-Saxena-IGT]

I am using chromedriver 2.37 and chrome browser 65 but still facing the same issue i,e web element is not clickable.

[rafaelbgil]

I have the same problem, I don't know if my problem is the chromedriver, chrome browser or its relationship.In my tests when I use Selenium with TestNG did not work, when I use only Selenium my tests work fine.

Is possible that the problem can be in my code, but the problem appears after update the chrome browser.

[cgoldberg]

https://sites.google.com/a/chromium.org/chromedriver/help/clicking-issues

[dipesh17]

@cgoldberg Tried following the above and many others. Updated 2.37 chrome driver.
The problem still exists, Chrome browser crashing, an element is not clickable, mouse over, entering keyword issue.
Based on the consistent comments from other it seems an issue with chrome V65 and selenium test even after updating chrome driver 2.37

[Shubham-Saxena-IGT]

I have used chromedriver 2.35 with Chrome 65. Somehow it worked for me. I know that on the official website chromedriver 2.35 only supports till Chrome 64 but my problem resolved after downgrading chromedriver to 2.35.

[barancev]

Closing the issue as there is no reproduction scenario provided.

[robotmonkey]

For those getting unknown error: Element is not clickable at point on headless chrome, on v65, I was able to fix this by passing in --window-size=3360, 1890 (play with sizes till one works for you) in chrome options. I only got the above error on Headless Chrome, and this fixed it for that particular scenario.

[NartanVyas]

I can reproduce same error with google chrome v-65 , and I used following chrome driver versions but it is not working with any of them.
chrome driver 2.32, 2.33, 2.34, 2.35, 2.36, 2.37 with google chrome =65.0.3325.181.
selenium web driver: 3.0.1, 3.5.1, 3.6.0, 3.7.1, 3.10.0, 3.11.
Can you provide solution?

[kevin2107]

I can also reproduce the error it has something to do with chrome 65. I downgraded my chrome version and the issues were fixed.

[DhanuRCG]

Now you can use the latest chrome driver 2.37 to fix these issues.

You can find it here.

Chrome Driver 2.37

[lucascaton]

I can also reproduce the error here:

Selenium::WebDriver::Error::UnknownError:
  unknown error: unknown sessionId
    (Session info: headless chrome=65.0.3325.181)
    (Driver info: chromedriver=2.37.544337 (8c0344a12e552148c185f7d5117db1f28d6c9e85),platform=Mac OS X 10.13.4 x86_64)

[lucascaton]

I've found out how to fix it:

Just pass a user-agent (you can find some here):

Capybara.register_driver :chrome do |app|
  Capybara::Selenium::Driver.new app, browser: :chrome,
    options: Selenium::WebDriver::Chrome::Options.new(args:
      ['headless', 'disable-gpu', "--user-agent='Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.75 Safari/535.7'"])
end

Capybara.javascript_driver = :chrome

[benbonnet]

200% unable to get a correct version of chromedriver via homebrew, ended up using a npm version

After making sure your chromedriver install points to the npm version (which chromedriver should output show node_modules in the path), the following comes handy in your rails_helper or spec/support/capybara.rb config file :

Selenium::WebDriver::Chrome.driver_path = '/path_to_npm_modules/bin/chromedriver'

Which is far from being optimal, but ended up working (after loads of struggle)

[MonSap]

@dipesh17 Did You got solution for the issue mentioned. I am getting same error .WebDriverException: Message: unknown error: Chrome failed to start: exited abnormally
(Driver info: chromedriver=2.37.544315 (730aa6a5fdba159ac9f4c1e8cbc59bf1b5ce12b7),platform=Linux 3.10.0-862.el7.x86_64 x86_64).
My browser version is 66.0

[Galileo1]

same error here - I am using "--no-sandbox" flag even then -

Constructor threw exception; nested exception is org.openqa.selenium.WebDriverException: unknown error: Chrome failed to start: exited abnormally
(Driver info: chromedriver=2.30.477691 (6ee44a7247c639c0703f291d320bdf05c1531b57),platform=Linux 4.4.0-101-generic x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 60.10 seconds
Build info: version: '3.13.0', revision: '2f0d292', time: '2018-06-25T15:24:21.231Z'
System info: host: 'travis-job-9c490209-933f-4e86-bb9c-10d479d1c97f', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '4.4.0-101-generic', java.version: '1.8.0_151'
Driver info: driver.version: ChromeDriver

[schnmudgal]

Chrome updated its latest version yesterday, and it not working again for ubuntu at least. Huh.
https://www.ubuntuupdates.org/package/google_chrome/stable/main/base/google-chrome-stable

[cgoldberg]

@schnmudgal please submit Chrome and ChromeDriver issues to the Chromium team:
https://bugs.chromium.org/p/chromedriver

When reporting, please be more specific than "not working", and be sure to include detailed version information for Chrome and ChromeDriver.