Unable to scroll chrome browser using Appium - selenium

I am trying to scrolldown chrome browser for my appium project but I am unable to scroll down. Below is the error message.
Exception in thread "main" org.openqa.selenium.WebDriverException: unknown error: call function result missing 'value'
(Session info: chrome=65.0.3325.109)
(Driver info: chromedriver=2.33.506120 (e3e53437346286c0bc2d2dc9aa4915ba81d9023f),platform=Windows NT 10.0.16299 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 0 milliseconds
There is a mismatch between ChromDriver and ChromeBroser version may be. How to check my ChromeDriver verison (2.33 as present in the error log) in my android device. How can I update the current version?

Update both chrome browser and chrome driver to latest version.Recent version of chrome browser doesn't work until driver is updated to latest version.

I found a solution how to fix the issue with updating the chrome driver to 2.36 It was to download the chromedriver version and replace it with the "chromedriver" that is taken by Appium the path was
C:\Users\Hamza_Soltani\AppData\Local\Programs\appium-desktop\resources\app\node_modules\appium\node_modules\appium-chromedriver\chromedriver\win\chromedriver.exe

Related

How to fix this issue " chrome browser compatibilty issue in selenium webdriver"?

I am just trying to automate a piece of code for automating the contact form, it was working fine a month ago but right now it's showing the below mention error
Exception in thread "main" org.openqa.selenium.SessionNotCreatedException: session not created: Chrome version must be between 70 and 73
(Driver info: chromedriver=73.0.3683.20 (8e2b610813e167eee3619ac4ce6e42e3ec622017),platform=Windows NT 10.0.17134 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 2.19 seconds
version compatibility issue, my chrome version is 74.** something and selenium is supporting 70-73
Issue : Your Chrome Browser Version is 74 and Your framework is having ChromeDriver Binary v73.0.3683.20 which supports Chrome Browser v73
Solution : Update your ChromeDriver Binary Version to v74.0.3729.6
Please have a look at Chrome Browser Release Section : Chrome Browser vs ChromeDriver Binary and follow below information -
If you are using Chrome version 75, please download ChromeDriver 75.0.3770.8
If you are using Chrome version 74, please download ChromeDriver 74.0.3729.6 (You shall follow this)
If you are using Chrome version 73, please download ChromeDriver 73.0.3683.68
For older version of Chrome, please see this discussion for the version of ChromeDriver that supports it.
Hope following above would resolve your issue.

HOOK-ERROR in after_step: TimeoutException: Message: timeout

Sometimes, when my script is run by jenkins i get an error:
HOOK-ERROR in after_step: TimeoutException: Message: timeout
(Session info: chrome=69.0.3497.92)
(Driver info: chromedriver=2.35.528139
(47ead77cb35ad2a9a83248b292151462a66cd881),platform=Linux 4.4.0-128-generic x86_64)
i cannot reproduce this situation on my local machine. Do you have any idea how can i check and fix it?
This error message...
HOOK-ERROR in after_step: TimeoutException: Message: timeout
(Session info: chrome=69.0.3497.92)
(Driver info: chromedriver=2.35.528139
...implies that the ChromeDriver was unable to initiate/spawn a new WebBrowser i.e. Chrome Browser session.
Your main issue is the incompatibility between the version of the binaries you are using as follows:
You are using chromedriver=2.35
Release Notes of chromedriver=2.35 clearly mentions the following :
Supports Chrome v62-64
You are using chrome=69.0
Release Notes of ChromeDriver v2.43 clearly mentions the following :
Supports Chrome v69-71
So there is a clear mismatch between the ChromeDriver v2.35 and the Chrome Browser v69.0
Solution
Upgrade JDK to recent levels JDK 8u191.
Upgrade Selenium to current levels Version 3.14.0.
Upgrade ChromeDriver to current ChromeDriver v2.42 level.
Keep Chrome version between Chrome v69-71 levels. (as per ChromeDriver v2.43 release notes)
Clean your Project Workspace through your IDE and Rebuild your project with required dependencies only.
If your base Web Client version is too old, then uninstall it through Revo Uninstaller and install a recent GA and released version of Web Client.
Execute your #Test.

Error number: 33: SessionNotCreatedError session not created exception from unknown error while trying to simulate chrome browser using SeleniumBasic

I have been using the COM interface provided by Internet Explorer but, since some sites have now moved on and don't support IE, I have been looking to substitute this with SeleniumBasic.
As this is completely new to me, I'm at the very basic level - I've downloaded the
Selenium Type Library (I've downloaded the Selenium library reference from Github, and referenced is in the module).
I've put in a very basic bit of code to test it out but I'm getting the following error:
Error number: 33
Error description:
SessionNotCreatedError session not created exception from unknown
error: Runtime.executionContextCreated has invalid 'context':
{"auxData":{"frameId":"AE85B634088DDFB4B8E7D65A145ADA0F","isDefault":true},"id":1,"name":"","origin":"://"}
(Session info: chrome=69.0.3497.100) (Driver info:
chromedriver=2.21.371459
(36d3d07f660ff2bc1bf28a75d1cdabed0983e7c4),platform=Windows NT 10.0
x86_64)
The code is;
Sub TestCode()
Dim driver as New Selenium.Chrome
driver.get "www.Google.com"
End Sub
I've tried this with firefox and Edge browsers too but am getting the same issues - any suggestions on what might be going wrong?
This error message...
SessionNotCreatedError session not created exception from unknown error: Runtime.executionContextCreated has invalid 'context': {"auxData":{"frameId":"AE85B634088DDFB4B8E7D65A145ADA0F","isDefault":true},"id":1,"name":"","origin":"://"}
(Session info: chrome=69.0.3497.100)
(Driver info: chromedriver=2.21.371459 (36d3d07f660ff2bc1bf28a75d1cdabed0983e7c4),platform=Windows NT 10.0 x86_64)
...implies that the ChromeDriver was unable to initiate/spawn a new WebBrowser i.e. Chrome Browser session.
Your main issue is the incompatibility between the version of the binaries you are using as follows:
You are using chromedriver=2.21
Release Notes of chromedriver=2.21 clearly mentions the following :
Supports Chrome v46-50
You are using chrome=69.0
Release Notes of ChromeDriver v2.42 clearly mentions the following :
Supports Chrome v68-70
So there is a clear mismatch between ChromeDriver v2.21 and the Chrome Browser v69.0
Solution
Upgrade Selenium to current levels Version 3.14.0.
Upgrade ChromeDriver to current ChromeDriver v2.42 level.
Keep Chrome version between Chrome v68-70 levels. (as per ChromeDriver v2.42 release notes)
Clean your Project Workspace through your IDE and Rebuild your project with required dependencies only.
Execute your #Test.
Update A
As per florentbr/SeleniumBasic the last version of SeleniumBasic (A Selenium based browser automation framework for VB.Net, Visual Basic Applications and VBScript) seems to be Release v2.0.9.0 only.
As per the CHANGELOG of Release v2.0.9.0 the underlying components are:
Firefox driver version 2.52.0
IE driver version 2.52.1
Update B
If you intend to use GeckoDriver with Firefox you can following the matrix below:

Selenium error when deleting cookies

Has anyone encountered this issue when Selenium tries to delete cookies?
After months of working fine and not changing anything, we're suddenly hitting this error when running tests:
System.InvalidOperationException : unknown error: Runtime.executionContextCreated has invalid 'context': {"auxData":{"frameId":"(FE3E5C7422F34F92AF238C0A8EBA89BF)","isDefault":true},"id":1,"name":"","origin":"://"}
(Session info: chrome=64.0.3282.167)
(Driver info: chromedriver=2.9.248315,platform=Windows NT 6.3 x86_64)
at OpenQA.Selenium.Remote.RemoteWebDriver.UnpackAndThrowOnError(Response errorResponse)
at OpenQA.Selenium.Remote.RemoteWebDriver.Execute(String driverCommandToExecute, Dictionary`2 parameters)
at OpenQA.Selenium.Remote.RemoteCookieJar.DeleteAllCookies()
at FluentAutomation.CommandProvider.<>c__DisplayClass2.<.ctor>b__0()
at System.Lazy`1.CreateValue()
at System.Lazy`1.LazyInitValue()
at FluentAutomation.CommandProvider.get_webDriver()
at FluentAutomation.CommandProvider.<>c__DisplayClassc.<FindMultiple>b__a()
at FluentAutomation.ElementProxy.get_Elements()
The error says it all :
System.InvalidOperationException : unknown error: Runtime.executionContextCreated has invalid 'context': {"auxData":{"frameId":"(FE3E5C7422F34F92AF238C0A8EBA89BF)","isDefault":true},"id":1,"name":"","origin":"://"}
(Session info: chrome=64.0.3282.167)
(Driver info: chromedriver=2.9.248315,platform=Windows NT 6.3 x86_64)
Your main issue is the compatibility between the Version of the Binaries you are using.
You are using chromedriver=2.9
Release Notes of chromedriver=2.9 clearly mentions the following :
Supports Chrome v31-34
You are using Chrome Browser version 64.0
So there is a clear mismatch between the Version of the Binaries.
Solution
Upgrade your ChromeDriver to recent ChromeDriver=2.35 level.
As per the Release Notes of ChromeDriver=2.35 upgrade your Chrome Browser to Chrome v62-64 levels.
If your base Chrome Browser version is too old uninstall Chrome Browser through Revo Uninstaller and install a recent released GA version of Chrome Browser
Execute your Tests

Chrome driver exception on Jenkins

I have selenium 2.53.1.jar, platform-Windows, Java- 1.8, chrome = 52.0, chrome-driver.exe-2.23.
I am seeing the following message when trying to run Night watch test on Jenkins.
org.openqa.selenium.WebDriverException: unknown error: unable to
discover open pages (Driver info: chromedriver=2.23.409699
(49b0fa931cda1caad0ae15b7d1b68004acd05129),platform=Windows NT
6.3.9600 x86_64)
Please note that the test is running correctly from the command line- all paths given are same as in the Jenkins job.
I also tried a previous version 2.22 of Chrome driver. Still see the same error.
Test is running correctly on FF.
Even I'm getting the same error. Maybe you can try putting sand-box for chrome. Maybe that might help you out temporarily.