Protractor encountering a session creation exception for chrome

Question

Protractor encountering a session creation exception for chrome

Encountering an error while trying to execute a Protractor test in Chrome.

Here is my conf.ts file:

import {Config} from 'protractor'

export let config: Config = {
    framework: 'jasmine',
    multiCapabilities: [
        {
            browserName: 'chrome',
            chromeOptions: {
                args: ['--start-maximized']
            },
        }],
    seleniumAddress: 'http://127.0.0.1:4444/wd/hub',
    seleniumPort: null,
    seleniumArgs: [],
    specs: [
        './Protractor/Login/*.spec.js',

Error Message:

Protractor conf.js
[17:19:07] I/hosted - Using the selenium server at http://127.0.0.1:4444/wd/hub
[17:19:07] I/launcher - Running 1 instances of WebDriver
[17:19:09] E/launcher - session not created exception
from unknown error: Runtime.executionContextCreated has invalid 'context': {"auxData":{"frameId":"8800.1","isDefault":true},"id":1,"name":"","origin":"://"}
  (Session info: chrome=54.0.2840.59)
  (Driver info: chromedriver=2.22.397933 (1cab651507b88dec79b2b2a22d1943c01833cc1b),platform=Windows NT 6.3.9600 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 1.07 seconds
Build info: version: '2.53.1', revision: 'a36b8b1', time: '2016-06-30 17:37:03'
System info: host: 'MAL000009416062', ip: '192.168.1.4', os.name: 'Windows 8.1', os.arch: 'amd64', os.version: '6.3', java.version: '1.8.0_73'
Driver info: org.openqa.selenium.chrome.ChromeDriver
[17:19:09] E/launcher - SessionNotCreatedError: session not created exception
from unknown error: Runtime.executionContextCreated has invalid 'context': {"auxData":{"frameId":"8800.1","isDefault":true},"id":1,"name":"","origin":"://"}
  (Session info: chrome=54.0.2840.59)
  (Driver info: chromedriver=2.22.397933 (1cab651507b88dec79b2b2a22d1943c01833cc1b),platform=Windows NT 6.3.9600 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 1.07 seconds
Build info: version: '2.53.1', revision: 'a36b8b1', time: '2016-06-30 17:37:03'
System info: host: 'MAL000009416062', ip: '192.168.1.4', os.name: 'Windows 8.1', os.arch: 'amd64', os.version: '6.3', java.version: '1.8.0_73'
Driver info: org.openqa.selenium.chrome.ChromeDriver
    at WebDriverError (C:\Users\392811\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\error.js:27:5)
    at SessionNotCreatedError (C:\Users\392811\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\error.js:308:5)

conf.ts:

multiCapabilities: [
        {
            browserName: 'chrome',
            chromeOptions: {
                args: ['--start-maximized']
            },
        }],

Seeking advice as most discussions online revolve around the version, yet I am using the latest versions available.

Any help would be greatly appreciated.

Cheers

selenium-webdriver typescript protractor selenium-chromedriver

Answer 1

Answer №1

To modify the version of chromedriver that is downloaded by webdriver-manager, simply adjust the config.json file within Protractor's directory...

Locate and open Protractor's config file: node_modules/protractor/config.json
Update the chrome driver version to the desired one. For example, change "chromedriver": "2.24".
Execute webdriver-manager update to apply the changes.

Based on the error message provided, it seems that protractor is currently utilizing an outdated version of the chrome driver. The stack trace indicates that the chrome driver version being used is displayed as 2.21.

Answer 2

To modify the version of chromedriver that is downloaded by webdriver-manager, simply adjust the config.json file within Protractor's directory...

Locate and open Protractor's config file: node_modules/protractor/config.json
Update the chrome driver version to the desired one. For example, change "chromedriver": "2.24".
Execute webdriver-manager update to apply the changes.

Based on the error message provided, it seems that protractor is currently utilizing an outdated version of the chrome driver. The stack trace indicates that the chrome driver version being used is displayed as 2.21.

Answer 3

Answer №2

I have not yet gained enough reputation to comment on Sudharsan's answer, but I wanted to clarify the location of the configuration file you need to modify.

node_modules/protractor/node_modules/webdriver-manager/config.json

It's not the Protractor tsconfig file, but the webdriver-manager config.json that needs to be edited.

While Sudharsan's solution may work for a one-time installation, I encountered a recurring issue in my setup. In our TFS builds, the working directory is cleared and a fresh repository is pulled in for each build. Modifying the webdriver config directly did not resolve the problem as it always reverted to the older version of chromedriver.

Instead, I added chromedriver to my devDependencies in the package.json, deleted the webdriver-manager installed version, and moved the updated chromedriver with a gulp task. In the devDependencies section of my package.json:

"chromedriver": "~2.24.1"

Then, I used a gulp task to delete and move the files like this:

(gulp task code here)

After these steps, Protractor still looked for the old chromedriver. I had to specify the location of the chromedriver.exe in protractor conf.js to make it work.

chromeDriver: "../node_modules/protractor/node_modules/webdriver-manager/selenium/chromedriver.exe",

It may seem complex, but it was necessary because chromedriver 2.22 didn't function properly with Chrome 53+. If you only need a one-time install, Sudharsan's solution is simpler. But for continuous installation like my setup, consider this alternative method.

Answer 4

I have not yet gained enough reputation to comment on Sudharsan's answer, but I wanted to clarify the location of the configuration file you need to modify.

node_modules/protractor/node_modules/webdriver-manager/config.json

It's not the Protractor tsconfig file, but the webdriver-manager config.json that needs to be edited.

While Sudharsan's solution may work for a one-time installation, I encountered a recurring issue in my setup. In our TFS builds, the working directory is cleared and a fresh repository is pulled in for each build. Modifying the webdriver config directly did not resolve the problem as it always reverted to the older version of chromedriver.

Instead, I added chromedriver to my devDependencies in the package.json, deleted the webdriver-manager installed version, and moved the updated chromedriver with a gulp task. In the devDependencies section of my package.json:

"chromedriver": "~2.24.1"

Then, I used a gulp task to delete and move the files like this:

(gulp task code here)

After these steps, Protractor still looked for the old chromedriver. I had to specify the location of the chromedriver.exe in protractor conf.js to make it work.

chromeDriver: "../node_modules/protractor/node_modules/webdriver-manager/selenium/chromedriver.exe",

It may seem complex, but it was necessary because chromedriver 2.22 didn't function properly with Chrome 53+. If you only need a one-time install, Sudharsan's solution is simpler. But for continuous installation like my setup, consider this alternative method.

Answer 5

Answer №3

All I had to do was:

npm update -g protractor
webdriver-manager update

After that, everything was back to normal.

Answer 6

All I had to do was:

npm update -g protractor
webdriver-manager update

After that, everything was back to normal.

Answer 7

Answer №4

Exciting news from Protractor with the latest release version 4.0.10, featuring an updated webdriver-manager (version 10.2.6) and the new Chromedriver. Simply run "webdriver-manager update" to get the latest Chromedriver. Don't forget to update the Protractor version in your package.json file by changing "protractor": "^4.0.9" to "protractor": "^4.0.10".

Stay up to date with the latest Protractor updates! :)

Answer 8

Exciting news from Protractor with the latest release version 4.0.10, featuring an updated webdriver-manager (version 10.2.6) and the new Chromedriver. Simply run "webdriver-manager update" to get the latest Chromedriver. Don't forget to update the Protractor version in your package.json file by changing "protractor": "^4.0.9" to "protractor": "^4.0.10".

Stay up to date with the latest Protractor updates! :)

Answer 9

Answer №5

To update the WebDriver, simply execute the command below:
Projectdirectory:/>webdriver-manager update --versions.chrome=ChromeVersion
Replace "ChromeVersion" with the version of your Google Chrome Browser. You can find the version by going to "Help>>About Google Chrome>>For Example: Version 76.0.3809.100 (Official Build) (64-bit)".

I trust this solution will resolve your issue.

Answer 10

To update the WebDriver, simply execute the command below:
Projectdirectory:/>webdriver-manager update --versions.chrome=ChromeVersion
Replace "ChromeVersion" with the version of your Google Chrome Browser. You can find the version by going to "Help>>About Google Chrome>>For Example: Version 76.0.3809.100 (Official Build) (64-bit)".

I trust this solution will resolve your issue.

Answer 11

Answer №6

To resolve the issue, I found that updating both chromedriver and protractor-conf.js did the trick.

First, download the latest version of chromedriver that is compatible with your operating system (feel free to adjust the minor version if necessary). You can find it here: http://chromedriver.storage.googleapis.com/index.html?path=2.24/
Next, extract the files to the /usr/local/bin/chromedriver directory.
Then, locate the protractor-conf.js file (usually in the app's root directory) and include the line
```
config.chromeDriver = '/usr/local/bin/chromedriver';
```

Answer 12

To resolve the issue, I found that updating both chromedriver and protractor-conf.js did the trick.

First, download the latest version of chromedriver that is compatible with your operating system (feel free to adjust the minor version if necessary). You can find it here: http://chromedriver.storage.googleapis.com/index.html?path=2.24/
Next, extract the files to the /usr/local/bin/chromedriver directory.
Then, locate the protractor-conf.js file (usually in the app's root directory) and include the line
```
config.chromeDriver = '/usr/local/bin/chromedriver';
```

Answer 13

Answer №7

Make sure to locate the package.json file within your webdriver-manager directory in the users folder and update the webdriver version to the most recent one available. This adjustment should resolve the issue

"name": "webdriver-manager", "version": "15.3.2",

Answer 14

Make sure to locate the package.json file within your webdriver-manager directory in the users folder and update the webdriver version to the most recent one available. This adjustment should resolve the issue

"name": "webdriver-manager", "version": "15.3.2",

Protractor encountering a session creation exception for chrome

Answer №1

Answer №2

Answer №3

Answer №4

Answer №5

Answer №6

Answer №7

Similar questions

When the React Native Expo app is running, the TextInput form is covered by the keyboard

Inform the component of an error detected in the Angular service

Pattern matching for validating multiple email addresses

What is the best way to reference class variables and methods within a callback function in Typescript?

Commit to choosing an option from a dropdown menu using TypeScript

In Typescript, it mandates that a string value must be one of the values within the object

Issues with implementing Selenium WebDriver on Chrome have caused errors to occur during the initiation and completion of running Python tests

Step-by-step guide on how to stop CDK Drop depending on a certain condition

`How to locate elements by ClassName and their values in Java`

The Angular Router is continuing to show the HomeComponent upon navigation, rather than just displaying the ChildComponent

Transferring data from a child component to a parent component in Vue without the need for a click

Sorry, the element could not be located in the cache. It is possible that the page has been modified

Managing events like onClick for custom components in Next.js and React: A Beginner's Guide

Creating a stream of observables in RxJs and subscribing to only the latest one after a delay: A comprehensive guide

How can you incorporate a module for typings without including it in the final webpack bundle?

What causes the Angular child component (navbar) to no longer refresh the view after a route change?

Utilizing Angular 2's ngModel feature for dynamic objects and properties

Tips for effortlessly incorporating a new chip while maintaining a neat arrangement and ensuring button alignment

Angular2 authguards encountering issues when trying to run asynchronous functions

Steps for updating the value of a button in Typescript and React