-
Notifications
You must be signed in to change notification settings - Fork 209
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Selenium Grid Extras broken for Chrome 74+ #426
Comments
it should work, i am using it with chrome 75.0 and it works for me. I just made sure grid extras does not decide the chrome driver version for me. For e.g. it will ask this question for driver version, it will automatically download it for you if you give the below version info, just check the download page, you will get the version number for each chrome releases. https://chromedriver.storage.googleapis.com/index.html?path=75.0.3770.90/ What version of Chrome Driver should we use? If its chrome 76, give this version : 76.0.3809.25 , it will auto download the driver. |
Hi @selfamit , thank you for the tip - but I'm still getting the same error running with Chrome Driver 75.0.3770.90/Chrome 75.0: ERROR: [object Object] What version of Selenium Grid Extras are you using? Also what OS/platform is your worker node on? Does it happen to work for you with Firefox with any driver version? |
i am running selenium grid extras 2.0.4 running on windows10 machine, chrome version 75.Maybe i need to check with firefox but chrome 75 works fine for me. |
@selfamit , thanks for your replies. One more question, what version of Webdriver are you running? we have |
Is this problem still open? I am having an issue where it will not download anything since 75 as well. |
@byamagata yes, the issue still exists. Selenium-grid-extras won't download chromedriver versions past 2.46 (corresponding to browser version 73). Driver versions after that follow a different format corresponding to the browser version. Drivers can be downloaded manually, but so far all browser/driver/version/bitness combinations past 73(64-bit)/2.46(32-bit) result in the error "invalid argument: 'text' must be a string" when setting text fields. Including the latest Chrome 85.0.4183.121 with https://chromedriver.storage.googleapis.com/index.html?path=85.0.4183.87/ (per instructions at https://chromedriver.chromium.org/downloads/version-selection:) |
Selenium-grid-extras with Chromedriver will break when Chrome upgrades to v 74 or higher.
(Firstly it can't auto-download the corresponding driver versions. If you manually download and rename the appropriate driver versions, 74.0, 75.0, Selenium Grid Extras errors out with the same errors we see with Firefox.)
Chromedriver version 2.46 supports Chrome v71-73 per http://chromedriver.chromium.org/downloads, and that is the last one that appears to work with Selenium Grid Extras.
The error that appears when trying to run with Chrome v 75 /chromedriver 75.0 (manually updated and renamed to match selenium grid extras' pattern) is the same as that seen with Firefox in #387 , "ERROR: [Object object]." (actual error is {"type": "unknown", "message": "unknown"}.)
Also according to https://stackoverflow.com/questions/56452798/how-to-turn-off-w3c-in-chromedriver-to-address-the-error-unknown-command-cannot, chromedriver 75 starts in w3c standard mode by default. Geckodriver is also w3c compliant so perhaps this is related to both this issue and #387.
The text was updated successfully, but these errors were encountered: