session not created: Chrome version must be between 71 and 75 - while running angular e2e in Concourse

wdio session not created chrome version must be between 71 and 75
protractor
protractor chromedriver
chrome version must be between 71 and 75 mac os
webdriver-manager
session not created: this version of chromedriver only supports chrome version 75
cannot find module 'chromedriver
chromedriver=74.0 3729

While executing e2e test in concourse, I'm getting the below error, where it looks like the chromedriver is not getting updated. While similar problems were discussing about chrome version falling behind, in my case, the chrome stable version is getting downloaded as expected (76.0.3809.100). But the chromedriver version thats getting pulled by protractor's webmanager driver is stuck in 2.46.

I tried to manually update the chromedriver from 2.46 to 76.0.3809.12, but it was still falling back to 2.46 during execution.

#!/bin/bash

set -e -u -x

wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add -

sh -c 'echo "deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google.list'

apt-get update && apt-get install -y google-chrome-stable

cd git-platformUI/ui

npm install

npm set progress=false && npm config set depth 0 && npm cache clean --force

$(npm bin)/ng e2e --configuration=$CONFIG

[07:33:13] E/launcher - session not created: Chrome version must be between 71 and 75 (Driver info: chromedriver=2.46.628388 (4a34a70827ac54148e092aafb70504c4ea7ae926),platform=Linux 4.15.0-36-generic x86_64) [07:33:13] E/launcher - SessionNotCreatedError: session not created: Chrome version must be between 71 and 75 (Driver info: chromedriver=2.46.628388 (4a34a70827ac54148e092aafb70504c4ea7ae926),platform=Linux 4.15.0-36-generic x86_64) at Object.checkLegacyResponse (/tmp/build/357f536d/git-platformUI/ui/node_modules/selenium-webdriver/lib/error.js:546:15) at parseHttpResponse (/tmp/build/357f536d/git-platformUI/ui/node_modules/selenium-webdriver/lib/http.js:509:13) at doSend.then.response (/tmp/build/357f536d/git-platformUI/ui/node_modules/selenium-webdriver/lib/http.js:441:30) at at process._tickCallback (internal/process/next_tick.js:188:7) From: Task: WebDriver.createSession() at Function.createSession (/tmp/build/357f536d/git-platformUI/ui/node_modules/selenium-webdriver/lib/webdriver.js:769:24) at Function.createSession (/tmp/build/357f536d/git-platformUI/ui/node_modules/selenium-webdriver/chrome.js:761:15) at Direct.getNewDriver (/tmp/build/357f536d/git-platformUI/ui/node_modules/protractor/built/driverProviders/direct.js:77:33) at Runner.createBrowser (/tmp/build/357f536d/git-platformUI/ui/node_modules/protractor/built/runner.js:195:43) at q.then.then (/tmp/build/357f536d/git-platformUI/ui/node_modules/protractor/built/runner.js:339:29) at _fulfilled (/tmp/build/357f536d/git-platformUI/ui/node_modules/q/q.js:834:54) at self.promiseDispatch.done (/tmp/build/357f536d/git-platformUI/ui/node_modules/q/q.js:863:30) at Promise.promise.promiseDispatch (/tmp/build/357f536d/git-platformUI/ui/node_modules/q/q.js:796:13) at /tmp/build/357f536d/git-platformUI/ui/node_modules/q/q.js:556:49 at runSingle (/tmp/build/357f536d/git-platformUI/ui/node_modules/q/q.js:137:13) [07:33:13] E/launcher - Process exited with error code 199

Delete your node_modules folder, add the below script to your package.json file and npm install. As posted in the comments above and on GitHub

"postinstall": "cd ./node_modules/protractor && npm i webdriver-manager@latest",

Update: The above script started breaking on me once the latest version started changed to webdriver-manager@12.1.7 so I had to be explicit with the version and set it to 12.1.6:

"postinstall": "cd ./node_modules/protractor && npm i webdriver-manager@12.1.6",

Can't specify ChromeDriver 76 or any other versions on webdriver , session not created: Chrome version must be between 71 and 75 on running Temporary fix to Travis webdriver chrome version DSpace/dspace-angular#441 >protractor folder and run npm i webdriver-manager@latest When you do not execute e2e tests on Chrome due to protractor incompatibility While executing e2e test in concourse, I’m getting the below error, where it looks like the chromedriver is not getting updated. While similar problems were discussing about chrome version falling behind, in my case, the chrome stable version is getting downloaded as expected (76.0.3809.100). But the chromedriver version thats getting pulled by protractor’s webmanager driver […]

Try the below commands:

npm install protractor@5.4.2 --save-dev
ng e2e

It will work and download the latest chrome driver chromedriver_78.0.3904.70.zip.

Update Protractor to use Latest Chromedriver (Otherwise it can't run , I could not figure out a more elegant way to update the chromedriver being Node Version: 8.4.0; Protractor Version: 5.3.0; Angular Version: 1.6.9; Browser(s): Chrome It looks like it installs but when Protractor runs it uses the old version You only need to use the lastest selenium-webdriver version to  session not created: Chrome version must be between 71 and 75 – while running angular e2e in Concourse 0 While executing e2e test in concourse, I’m getting the below error, where it looks like the chromedriver is not getting updated.

Updated the protractor devDependency to latest (5.4.2) worked for me.

Session not created exception: Chrome version must be >= 62.0 , You could do $(npm bin)/webdriver-manager to run it, or just include it as part of your script for running your e2e tests in your package.json . session not created: Chrome version must be between 71 and 75 – while running angular e2e in Concourse 0 While executing e2e test in concourse, I’m getting the below error, where it looks like the chromedriver is not getting updated.

In my case, I just installed a missing package and reinstall all deps:

npm i -D webdriver-manager
rm -rf node_modules
npm install

... and run end-to-end tests one more time:

npm run e2e

Protractor + Firefox + docker: invalid argument: can't kill an exited , I used to work but since a week, my angular E2E tests fail to start when running in docker. It still works OK if I run them directly though. protractor. SessionNotCreatedError: session not created: Chrome version must be >= 69.0.3497.0 #340 jakehockey10 opened this issue Oct 28, 2018 · 12 comments Assignees

I had a similar problem that is why I am here, I tired everything until below

npm install chromedriver

Bug #41075: nautilus: mgr/dashboard: ceph dashboard Jenkins job , error: "session not created: Chrome version must be between 71 and 75" When we install google-chrome-stable on the system it would install issue: https://github.com/angular/webdriver-manager/issues/404 Update webdriver-​manager manually and run 'ng e2e --no-webdriver-update' instead. Hi, Bug report Protractor 5.4.2 can't work with new Chrome versions like 76.0.3809.87 Feature Request Add support for new chromedriver versions naming convention to Protractor 5.4.2 due to issues with Protractor 6 (My tests are executing

Changelog, Upgraded Chrome browser version used during cypress run and when selecting Electron has been updated to distinguish differences between it and Cypress. This should not affect tests, as tests will still re-run on a superdomain change. We now capture environment variables set from Concourse CI when recording​  I had a similar problem to this, however my issue was with Chrome 81. E/launcher - session not created: This version of ChromeDriver only supports Chrome version 81. My solution was the below two steps: 1) Dont let Angular install the latest available webdriver for you when running ng e2e, by using the --webdriverUpdate flag and setting it to

Newest 'concourse' Questions, Unanswered. Cancel. concourse. For questions related to pipeline-based CI system Concourse written in Go. How to run maven command in Concourse task run config · maven concourse session not created: Chrome version must be between 71 and 75 - while running angular e2e in Concourse · angular protractor  Google doesn't offer an easy way to work with old versions. The best way is to work with 76 and get the associated driver version. Also, chrome drivers are not compatible with Chrome that is not same major version as the driver. For ex. driver v75 wont work with Chrome v76. Chrome drivers are available here for download via driver-manager.

Our company has a whole Code base of Automated scripts that we run on Protractor, and now that Chrome automatically updated to version 74, the test cases are not getting executed. We have the following versions of applications: Chrome is 74.0.3729.131, Protractor is 5.4.2, webdriver-manager is 12.1.4, node is v8.12.0, chromedriver is 74.0.3729.6.

Comments
  • Have you tried updating webdriver-manager?
  • Possible duplicate of When using Protractor 5.4.2, webdriver-manager downloads 2.46 which is not compatible with Chrome 74
  • The solution in the above link did not work for me. But the solution in the github issue github.com/angular/protractor/issues/5289 worked for me. "postinstall": "cd ./node_modules/protractor && npm i webdriver-manager@latest && cd ../.. && ./node_modules/.bin/webdriver-manager update"
  • Before removing node_modules folder, first try runing cd ./node_modules/protractor && npm i webdriver-manager... because it worked for me without removing node_modules
  • protractor is a dev dependency. I think it should be --save-dev