protractor - session not created exception - selenium-webdriver

I am getting the error below when trying to run Protractor test against chrome.
session not created exception: Chrome version must be >= 59.0.3071.0
[11:42:23] E/launcher - session not created exception: Chrome version must be >= 59.0.3071.0 (Driver info: chromedriver=2.32.498550 (9dec58e66c31bcc53a9ce3c7226f0c1c5810906a),platform=Windows NT 6.1.7601 SP1 x86_64) (WARNING: The server did not provide
any stacktrace information) Command duration or timeout: 6.44 seconds Build info: version: '3.5.3', revision: 'a88d25fe6b', time: '2017-08-29T12:54:15.039Z' System info: host: 'PC328569', ip: '10.25.227.179', os.name: 'Windows 7', os.arch: 'amd64', os.version:
'6.1', java.version: '1.8.0_121' Driver info: driver.version: unknown [11:42:23] E/launcher - SessionNotCreatedError: session not created exception: Chrome version must be >= 59.0.3071.0 (Driver info: chromedriver=2.32.498550 (9dec58e66c31bcc53a9ce3c7226f0c1c5810906a),platform=Windows
NT 6.1.7601 SP1 x86_64) (WARNING: The server did not provide any stacktrace information) Command duration or timeout: 6.44 seconds Build info: version: '3.5.3', revision: 'a88d25fe6b', time: '2017-08-29T12:54:15.039Z' System info: host: 'PC328569', ip:
'10.25.227.179', os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1', java.version: '1.8.0_121' Driver info: driver.version: unknown at WebDriverError (D:\Balachander\DailyScript\node_modules\selenium-webdriver\lib\error.js:27:5) at SessionNotCreatedError
(D:\Balachander\DailyScript\node_modules\selenium-webdriver\lib\error.js:214:5) at Object.checkLegacyResponse (D:\Balachander\DailyScript\node_modules\selenium-webdriver\lib\error.js:505:15) at parseHttpResponse (D:\Balachander\DailyScript\node_modules\selenium-webdriver\lib\http.js:509:13)
at doSend.then.response (D:\Balachander\DailyScript\node_modules\selenium-webdriver\lib\http.js:440:13) at process._tickCallback (internal/process/next_tick.js:103:7) From: Task: WebDriver.createSession() at Function.createSession (D:\Balachander\DailyScript\node_modules\selenium-webdriver\lib\webdriver.js:777:24)
at Function.createSession (D:\Balachander\DailyScript\node_modules\selenium-webdriver\chrome.js:709:29) at createDriver (D:\Balachander\DailyScript\node_modules\selenium-webdriver\index.js:167:33) at Builder.build (D:\Balachander\DailyScript\node_modules\selenium-webdriver\index.js:623:16)
at Hosted.getNewDriver (D:\Balachander\DailyScript\node_modules\protractor\lib\driverProviders\driverProvider.ts:60:29) at Runner.createBrowser (D:\Balachander\DailyScript\node_modules\protractor\lib\runner.ts:225:39) at q.then.then (D:\Balachander\DailyScript\node_modules\protractor\lib\runner.ts:391:27)
at _fulfilled (D:\Balachander\DailyScript\node_modules\q\q.js:834:54) at self.promiseDispatch.done (D:\Balachander\DailyScript\node_modules\q\q.js:863:30) at Promise.promise.promiseDispatch (D:\Balachander\DailyScript\node_modules\q\q.js:796:13) [11:42:23]
E/launcher - Process exited with error code 199
Versions of the executables used:
webdriver manager - 12.0.6
protractor - 5.1.2
chrome driver - 2.32
Java - 1.8
What I have tried:
1.Updating the webdriver to latest version
npm update -g protractor
webdriver-manager update
2.Editing Protractor's config file: node_modules/protractor/config.json
Changing the chrome driver version to whatever you need. eg. "chromedriver": "2.24".Run webdriver-manager update.
But for some reason webdriver-manager always uses chrome driver 2.32.
Any help or suggestion is appreciated. Thanks.

As per Below references you need to update your actual installed chrome.
Update chrome by :- About Google Chrome
Menu -> Help ->
Refer :-
https://github.com/appveyor/ci/issues/1600
Chromedriver error "Chrome version must be >= 52" using Nightwatch
Hope it will help you :)

Related

Protractor Not Running because of Firewall?

I'm trying to get Protractor working on Windows Server 2016. Using the tutorial on official protractor website, I've got it working on my laptop at home running Windows 10 and a work VM running Windows 7. I have local admin rights on all three. The work VM running Server 2016 just fails with error below when I run the conf.js
[16:36:25] I/launcher - Running 1 instances of WebDriver
[16:36:25] I/hosted - Using the selenium server at http://localhost:4444/wd/hub
[16:36:45] E/launcher - Timed out waiting for driver server to start.
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:25:53'
System info: host: 'APC', ip: 'x.x.x.x', os.name: 'Windows Server 2016', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_231'
Driver info: driver.version: unknown
[16:36:45] E/launcher - WebDriverError: Timed out waiting for driver server to start.
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:25:53'
System info: host: 'APC', ip: 'x.x.x.x', os.name: 'Windows Server 2016', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_231'
Driver info: driver.version: unknown
at Object.checkLegacyResponse (C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\error.js:546:15)
at parseHttpResponse (C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\http.js:509:13)
at C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\http.js:441:30
at processTicksAndRejections (internal/process/task_queues.js:93:5)
From: Task: WebDriver.createSession()
at Function.createSession (C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver.js:769:24)
at Function.createSession (C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\chrome.js:761:15)
at createDriver (C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\index.js:170:33)
at Builder.build (C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\index.js:626:16)
at Hosted.getNewDriver (C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\built\driverProviders\driverProvider.js:53:33)
at Runner.createBrowser (C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\built\runner.js:195:43)
at C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\built\runner.js:339:29
at _fulfilled (C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:834:54)
at C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:863:30
at Promise.promise.promiseDispatch (C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:796:13)
[16:36:45] E/launcher - Process exited with error code 199
The Server 2016 machine is an Azure Cloud VM. The Win7 machine is on-prem. Is this error any indication of a Firewall setting or something being blocked? I've been playing around with this for a few days and can't seem to figure it out. I know my company are all moving to Windows 10 eventually but my server would stay Server 2016 and we'd like to be able to make use of protractor for e2e testing of AngularJS and Angular 2+ apps.

E/launcher - unknown error: Chrome failed to start: crashed in headless mode

Face the following error
Google Chrome - 67.0
chromedriver - chromedriver_2.40
selenium standalone - selenium-server-standalone-3.12.0.jar
linux - CentOS Linux release 7.3
Protractor - 5.1.2
Nodejs - v6.14.2
config.ts
chrome: {
seleniumAddress: 'http://localhost:4444/wd/hub',
directConnect: true,
browserName: 'chrome',
chromeOptions:{
args: ['--headless','--disable-gpu','--disable-dev-shm-usage','--no-sandbox','window-size=1024,768']
}
10:37:07.923 [10:37:07] I/launcher - Running 1 instances of WebDriver
10:37:07.923 [10:37:07] I/hosted - Using the selenium server at http://localhost:4444/wd/hub
10:38:09.409 [10:38:09] E/launcher - unknown error: Chrome failed to start: crashed
10:38:09.409 (Driver info: chromedriver=2.40.565383 (76257d1ab79276b2d53ee976b2c3e3b9f335cde7),platform=Linux 3.10.0-514.26.2.el7.x86_64 x86_64) (WARNING: The server did not provide any stacktrace information)
10:38:09.409 Command duration or timeout: 60.39 seconds
10:38:09.409 Build info: version: '3.12.0', revision: '7c6e0b3', time: '2018-05-08T15:15:08.936Z'
10:38:09.409 System info: host: 'sigmagoagt-po-a1p.sys.comcast.net', ip: '147.191.72.189', os.name: 'Linux', os.arch: 'amd64', os.version: '3.10.0-514.26.2.el7.x86_64', java.version: '1.8.0_40'
10:38:09.410 Driver info: driver.version: unknown
10:38:09.410 [10:38:09] E/launcher - WebDriverError: unknown error: Chrome failed to start: crashed
10:38:09.410 (Driver info: chromedriver=2.40.565383 (76257d1ab79276b2d53ee976b2c3e3b9f335cde7),platform=Linux 3.10.0-514.26.2.el7.x86_64 x86_64) (WARNING: The server did not provide any stacktrace information)
10:38:09.410 Command duration or timeout: 60.39 seconds
10:38:09.410 Build info: version: '3.12.0', revision: '7c6e0b3', time: '2018-05-08T15:15:08.936Z'
10:38:09.411 System info: host: 'sigmagoagt-po-a1p.sys.comcast.net', ip: '147.191.72.189', os.name: 'Linux', os.arch: 'amd64', os.version: '3.10.0-514.26.2.el7.x86_64', java.version: '1.8.0_40'
10:38:09.411 Driver info: driver.version: unknown
10:38:09.411 at WebDriverError (/app/go-agent1/pipelines/UI-Automation-Testing/web/client-portal/node_modules/selenium-webdriver/lib/error.js:27:5)
10:38:09.411 at Object.checkLegacyResponse (/app/go-agent1/pipelines/UI-Automation-Testing/web/client-portal/node_modules/selenium-webdriver/lib/error.js:505:15)
10:38:09.411 at parseHttpResponse (/app/go-agent1/pipelines/UI-Automation-Testing/web/client-portal/node_modules/selenium-webdriver/lib/http.js:509:13)
10:38:09.412 at doSend.then.response (/app/go-agent1/pipelines/UI-Automation-Testing/web/client-portal/node_modules/selenium-webdriver/lib/http.js:440:13)
10:38:09.412 at process._tickCallback (internal/process/next_tick.js:109:7)
10:38:09.412 From: Task: WebDriver.createSession()
10:38:09.412 at Function.createSession (/app/go-agent1/pipelines/UI-Automation-Testing/web/client-portal/node_modules/selenium-webdriver/lib/webdriver.js:777:24)
10:38:09.412 at Function.createSession (/app/go-agent1/pipelines/UI-Automation-Testing/web/client-portal/node_modules/selenium-webdriver/chrome.js:709:29)
10:38:09.412 at createDriver (/app/go-agent1/pipelines/UI-Automation-Testing/web/client-portal/node_modules/selenium-webdriver/index.js:167:33)
10:38:09.412 at Builder.build (/app/go-agent1/pipelines/UI-Automation-Testing/web/client-portal/node_modules/selenium-webdriver/index.js:623:16)
10:38:09.413 at Hosted.getNewDriver (/app/go-agent1/pipelines/UI-Automation-Testing/web/client-portal/node_modules/protractor/lib/driverProviders/driverProvider.ts:60:29)
10:38:09.413 at Runner.createBrowser (/app/go-agent1/pipelines/UI-Automation-Testing/web/client-portal/node_modules/protractor/lib/runner.ts:225:39)
10:38:09.413 at q.then.then (/app/go-agent1/pipelines/UI-Automation-Testing/web/client-portal/node_modules/protractor/lib/runner.ts:391:27)
10:38:09.413 at _fulfilled (/app/go-agent1/pipelines/UI-Automation-Testing/web/client-portal/node_modules/protractor/node_modules/q/q.js:834:54)
10:38:09.413 at self.promiseDispatch.done (/app/go-agent1/pipelines/UI-Automation-Testing/web/client-portal/node_modules/protractor/node_modules/q/q.js:863:30)
10:38:09.413 at Promise.promise.promiseDispatch (/app/go-agent1/pipelines/UI-Automation-Testing/web/client-portal/node_modules/protractor/node_modules/q/q.js:796:13)
10:38:09.414 at /app/go-agent1/pipelines/UI-Automation-Testing/web/client-portal/node_modules/protractor/node_modules/q/q.js:556:49
10:38:09.414 at runSingle (/app/go-agent1/pipelines/UI-Automation-Testing/web/client-portal/node_modules/protractor/node_modules/q/q.js:137:13)
10:38:09.414 at flush (/app/go-agent1/pipelines/UI-Automation-Testing/web/client-portal/node_modules/protractor/node_modules/q/q.js:125:13)
10:38:09.414 at _combinedTickCallback (internal/process/next_tick.js:73:7)
10:38:09.414 at process._tickCallback (internal/process/next_tick.js:104:9)
You can run tests using selenium server or run them directly on browser. You should remove one of :
seleniumAddress: 'http://localhost:4444/wd/hub',
or
directConnect: true,
Uninstalling and re-installation of Chrome in centOS machine solved the issue. Followed installation procedure available in "https://intoli.com/blog/installing-google-chrome-on-centos/". Thank you.

I am getting 80% time error on running protractor scripts on IE 11

My protractor scripts are highly stable on chrome browser but the same scripts throws below mentioned for 20% of the test cases.
Failed: JavaScript error (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 100 milliseconds
Build info: version: '3.3.1', revision: '5234b32', time: '2017-03-10 09:04:52 -0800'
System info: host: 'LAPTOP-RNQ2JQBE', ip: '192.168.89.115', os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_121'
Driver info: org.openqa.selenium.ie.InternetExplorerDriver
Capabilities [{browserAttachTimeout=0, ie.enableFullPageScreenshot=true, enablePersistentHover=true, ie.forceCreateProcessApi=false, ie.forceShellWindowsApi=false, pageLoadStrategy=normal, ignoreZoomSetting=true, ie.fileUploadDialogTimeout=3000, version=11, platform=WINDOWS, nativeEvents=true, ie.ensureCleanSession=false, elementScrollBehavior=0, ie.browserCommandLineSwitches=, requireWindowFocus=false, browserName=internet explorer, initialBrowserUrl=http://localhost:41897/, javascriptEnabled=true, ignoreProtectedModeSettings=false, enableElementCacheCleanup=true, unexpectedAlertBehaviour=dismiss}]
Session ID: f32d0eb8-65d9-4161-9535-da5cde8b9a6c
Failed: Error while waiting for Protractor to sync with the page:
"Unable to get property '$$testability' of undefined or null
reference"

Chrome browser is not launching when launched on selenium webdriver

I have the following configuration :
Webdriver version : 3.3.0
Chrome version : 56
Chromedriver version : 2.24
OS Version : Windows 10
The exception I am facing is given below. I am quite new to selenium so not sure what could be the possible reason. I tried executing the same code with severla versions of chromedriver but with no luck
Starting ChromeDriver 2.24.417431 (9aea000394714d2fbb20850021f6204f2256b9cf) on port 45496
Only local connections are allowed.
Mar 13, 2017 8:27:43 PM org.openqa.selenium.remote.ProtocolHandshake createSession
INFO: Detected dialect: OSS
Exception in thread "main" org.openqa.selenium.NoSuchSessionException: no such session
(Driver info: chromedriver=2.24.417431 (9aea000394714d2fbb20850021f6204f2256b9cf),platform=Windows NT 10.0.14393 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 16 milliseconds
Build info: version: 'unknown', revision: 'b526bd5', time: '2017-03-07 11:11:07 -0800'
System info: host: 'DESKTOP-CU1N4JE', ip: '192.168.1.4', os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_121'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{message=unknown error: chrome failed to start
(Driver info: chromedriver=2.24.417431 (9aea000394714d2fbb20850021f6204f2256b9cf),platform=Windows NT 10.0.14393 x86_64), platform=ANY}]
Session ID: 0f4877e9d55cf1682ea6b45d0196319a
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:216)
at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:168)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:638)
at org.openqa.selenium.remote.RemoteWebDriver$RemoteWebDriverOptions$RemoteTimeouts.implicitlyWait(RemoteWebDriver.java:835)
at pkg_1302_02.Cl_1303_02.main(Cl_1303_02.java:19)
You are using an older version of chrome driver. Using latest chrome drive will solve the issue. Download latest chrome driver from Link to download Chrome driver

Getting "Error: read ECONNRESET" on reseting and launching the app

I am getting the following error on resetting the app [driver.resetApp()] and on launching the app on Appium (version: 1.4.16.1). I am using Java.
Eclispe console
org.openqa.selenium.WebDriverException: chrome not reachable
(Session info: chrome=50.0.2661.86)
(Driver info: chromedriver=2.18.343845 (73dd713ba7fbfb73cbb514e62641d8c96a94682a),platform=Windows NT 6.1 SP1 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 2.08 seconds
Build info: version: '2.48.2', revision: '41bccdd', time: '2015-10-09 19:59:12'
System info: host: 'IN2084073W1', ip: '192.168.56.1', os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1', java.version: '1.7.0_21'
*** Element info: {Using=id, value=password}
Session ID: 2968b7e9-948e-4b75-94ed-838d10a08c82
Driver info: io.appium.java_client.android.AndroidDriver
Capabilities [{platform=LINUX, app=C:/apk/appname.apk, javascriptEnabled=true, appActivity=.MainActivity, browserName=, networkConnectionEnabled=true, desired={newCommandTimeout=120, app=C:/apk/surveyorapp.apk, platformVersion=5.1, deviceName=TA93303Q2F, platformName=Android, appActivity=.MainActivity, browserName=, appPackage=com.axa.surveyorapp}, locationContextEnabled=false, appPackage=com.axa.surveyorapp, newCommandTimeout=120, platformVersion=5.1, databaseEnabled=false, deviceName=TA93303Q2F, platformName=Android, webStorageEnabled=false, warnings={}, takesScreenshot=true}]
Appium Log
error: Could not proxy command to remote server. Original error: Error: read ECONNRESET
error: Chromedriver: Chromedriver exited unexpectedly with code 3221225477, signal null
info: Chromedriver: Changed state to 'stopped'
warn: Chromedriver for context WEBVIEW_com.clientname.appname stopped unexpectedly
error: Chromedriver quit unexpectedly during session
Update
Thanks for the update Emna. I have tried your option.
Can you please let me know how exactly I need to add this. I am using AndroidDriver not AppiumDriver. I have tried with both, but I'm getting below error.
Try to use :
(AppiumDriver)driver.resetApp();
Instead of :
driver.resetApp();
You can have a look into this link: Appium java-client
and use this link also to download ;)

Resources