Agile Testing, Browser, Chrome, Exception, protractor, Selenium

protractor- session not created: Chrome version must be between 70 and 73

DevTools listening on ws://127.0.0.1:57284/devtools/browser/f4efc932-01f3-4ac5-8a77-b19e65f2849b
[14:36:42] E/launcher – session not created: Chrome version must be between 70 and 73
(Driver info: chromedriver=2.45.615291 (ec3682e3c9061c10f26ea9e5cdcf3c53f3f74387),platform=Windows NT 10.0.17134 x86_64)
[14:36:42] E/launcher – SessionNotCreatedError: session not created: Chrome version must be between 70 and 73
(Driver info: chromedriver=2.45.615291 (ec3682e3c9061c10f26ea9e5cdcf3c53f3f74387),platform=Windows NT 10.0.17134 x86_64)
at Object.checkLegacyResponse (C:\Users\khyati.sehgal\source\Workspaces\QA\SAND-DEV-1\node_modules\protractor\node_modules\selenium-webdriver\lib\error.js:546:15)
at parseHttpResponse (C:\Users\khyati.sehgal\source\Workspaces\QA\SAND-DEV-1\node_modules\protractor\node_modules\selenium-webdriver\lib\http.js:509:13)
at doSend.then.response (C:\Users\khyati.sehgal\source\Workspaces\QA\node_modules\protractor\node_modules\selenium-webdriver\lib\http.js:441:30)
at

While working in current project I encountered an issue, which was not allowing at all my IDE to run anything.

This issue has something to do with the chrome version where in I discovered some traits of protractor which ultimately helps me in understanding how is selenium and protractor are  different in their implementation as well as execution.

Problem?

[14:36:42] E/launcher – session not created: Chrome version must be between 70 and 73
(Driver info: chromedriver=2.45.61529

Solution!!

Check the webdriver version

webdriver-version

npm update -g protractor

webdriver-manager update

webdriver-update

Take Away.

Though protractor supports multiple browser in different variations like headless, maximize, etc. 

But to support the browser with protractor version we need to manually update the version of it.  In-fact, the command npm update -g protractor updates all the coupled libraries of it like jasmine, etc Again, just in case if the dependencies are not compatible with the newly loaded version then they have to be explicitly updated by the npm update command mentioning the specific version of the dependency like jasmine, etc.

This is a drawback of using protractor in such cases when you are dealing with multiple browsers or different versions of same browser.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s