Selenium ChromeDriver Version Conflict - ruby

My Selenium program written with Ruby randomly stopped working (it ran perfectly yesterday) and gave me this error:
Backtrace:: session not created: This version of ChromeDriver only supports Chrome version 89 (Selenium::WebDriver::Error::SessionNotCreatedError)Current browser version is 91.0.4472.77 with binary path C:\\Program Files (x86)\\Google\\Chrome\\Application\\chrome.exe
I've since tried:
Un & re-installing ChromeDriver (newest version, as I was using before)
Replacing my current version with version 89 along with changing the path (this resulted in the same error)
Following these similar issues 1 & 2
I'm not sure where to go from here

I had a similar problem recently with the C# version.
I would double check where Selenium is being ran from.
In my case it was debug/netcoreapp3.1\chromedriver.exe, so it was running an outdated version compared to the version of Chrome installed.
Make sure you have the correct ChromeDriver version from here
If this fails, check the Ruby bindings wiki here

I had the same problem, but in C#. I had to update Nugget for ChromeDriver to match versions. So I basically updated my ChromeDriver to 91.0.4472 and it's resolved the issue.

Related

Google Cloud SDK v274.0.0 update asking for Python 2.7 interpreter on a machine that has only ever had Python 3+ (Windows)

This is really strange - I've found no help in the documentation, nor can we replicate the error on a machine of a similar build. The gcloud CLI has worked without any error on my Python 3 machine for months.
After today's update, any gcloud command is met with the below error message, looking for a Python 2.7 interpreter. I'm at a loss as to how to proceed - even when attempting to uninstall with the gcloud command the same error is thrown.
This is a known issue that is being tracked here
Version 2.74 installation is broken on Windows. You will need to install an older version. This can be fixed by hand-editing gcloud.cmd but I do not recommend this.
Use the following link to download a previous version after uninstalling the current version.
Installing from versioned archives
[UPDATE 12/30/2019]
Google has released a minor revision update that appears to fix this problem. The revised update is version 2.74.0.1.

Version of node for Sidekick

I've just downloaded the latest Nativescript Sidekick. When I try to run it, I get the message that it is expecting:
"NodeJS >=8.0.0 <=10.5.0"
I'm using nvm, so I can switch node versions at will, but Sidekick appears to ignore this and pick up the latest (10.9.0 in my case). How does Sidekick detect the nodejs version? And how can I persuade otherwise???
After #GGarabedian confirmed that it worked with NVM for him, I played around a bit and discovered that Sidekick is looking for the NVM alias Stable.
So, by setting the alias to v8.11.0, Sidekick did work for me.
nvm alias stable v8.11.0
I have tested NativeScript Sidekick with the Node Version Manager and it appears to detect the currently selected Node version correctly. Can you verify if you have installed and selected a NodeJS version between 8.0.0 and 10.5.0 by running the node --version command in the Command Prompt?
Also, my tests were conducted on a Windows machine and it would be good to know if you are running on the same or different OS.

Using old version of Cygwin

I am trying to use the old version of 32 bit cygwin (1.7.22 - 1.7.32) which uses GCC 4.7.3 version.
Just found one (cygwin 1.7.25) but during the standard installation (running with setup-x86.exe) it shows the following errors:
The current ini file is from a newer version of setup.exe. If you have
any trouble installing, please download a fresh version from "cygwin
official page"
Is that old version not supported anymore and I can not chose right address from where it can download and install the needed packages?
Thanks,
Arsen
I can't find a good answer. Normally what you see in the installer is what you have access to.
When you load your setup-x86.exe, get to the packages (ignore the warning), and see if you can select the version of Cygwin you need (use the search box to narrow it down). On mine I can only get a few revisions and nothing as old as you need. That being said, I do have the latest installer and can't test this for you.

Selenium does not work when we get a upgrade from firefox

I am working on Automation tool Behat/Mink . After upgrading Firefox version to 25 , i am seeing this error .
Curl error thrown for http POST to http://localhost:4444/wd/hub/session/execute with params: {"script":"return document.getElementById('user') !== null;","args":[]}
Failed to connect to 127.0.0.1: Can't assign requested address
I am using selenium webdriver version 2.37.0.jar as the server.
Support for Firefox 25 has been added in version 2.38. Current version is 2.39 which supports Firefox 26.
It is a good practice to check for the new selenium version every time Firefox upgrades. Updating the server should work.
Official download page.
run this command before running your tests
java -jar selenium-server-standalone-*
this will help you to resolve your problem
make sure your selenium latest version should be on same folder

Selenium WebDriver + Firefox 7.0.1 incompatibility

I have a project where we have some Selenium tests. I have recently upgraded Firefox to 7.0.1 because it prompted me to and now the "WebDriver for Firefox" extension that these tests use is broken.
How can I fix this? Must I uninstall this current version of Firefox and install an older one? Or is there a file I can edit to tell it to ignore that the version is different?
An upgrade to Selenium webdriver to 2.8 would probably solve it.
http://web.archive.org/web/20120115040501/http://selenium.googlecode.com/svn/tags/selenium-2.8.0/rb/CHANGES
Unfortunately this has been the case for every Firefox upgrade since 5.0
I would try with the latest selenium-webdriver. I run Firefox 7.0.1 as well and it works with selenium-webdriver 2.8.0.
You can tell Firefox to ignore plugin and extension versions.
Type about:config in the browser address bar
Right-click and create a new boolean value called extensions.checkCompatibility.7.0
Set this value to false
That should prevent the plugin raising an issue with its version compatibility to 7.0.1
i am working with FF-8. Just change the firefox version from standalone.jar. For this unzip your jar file with unzipper and search for install.rdf files in the unzipped files. Open them in word pad and change version. you can add the latest version of browser. There are five or six files that to be changed. after doing that again zip them change to extension .jar

Resources