CODEWITHSUNDEEP
selenium-webdriverprotractorselenium-chromedriver
sebap
sebap

Reputation: 1691

Protractor / Selenium Webdriver : Runtime.executionContextCreated has invalid 'context'

I use protractor to test Angular2 app. It was working fine and I think I didn't change nothing in conf but now it ends up with this:

...

super(opt_error);
    ^
SessionNotCreatedError: session not created exception
from unknown error: Runtime.executionContextCreated has invalid 'context': {"auxData":{"frameId":"4012.1","isDefault":true},"id":1,"name":"","origin":"://"}
  (Session info: chrome=54.0.2840.71)
  (Driver info: chromedriver=2.21.371459

...

I work on a Mac OSX 10.11.4, Chrome 54.0.2840.71.

Any suggestion? Thanks

--- EDIT 26/10

Since it depends on each one settings it looks like theres no absolute answer to this. The main idea is to update protractor/ chromedriver / webdriver-manager accordingly.

Saying that i now face another problem : every basic test i do, including ( for instance ) a browser.get() is failing with :

Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL

I don't know if it's an isolated case and if it fits here (I use jasmine2 as framework) so I start another question here

Upvotes: 11

Views: 11816

Answers (5)

Evers
Evers

Reputation: 223

If even after updating the webdriver to 2.25, the error is still occurring and if you are using the terminal app this should help :

I managed to fix the issue by unchecking “Set locale environment variables on startup” checkbox in advanced terminal app settings. Or try to launch your test with this prefix : 

LC_NUMERIC=”en_US.UTF-8″ npm test

Upvotes: 0

DevGrowth.Tech
DevGrowth.Tech

Reputation: 1563

I updated the selenium-standalone to the latest version 5.8.0 (from 5.1.0). It will install the newer version of chrome webdriver(2.25), instead of install chrome driver2.21. This solved the issue on my end.(no connection, session exception)

Upvotes: 0

wnordmann
wnordmann

Reputation: 301

I had a similar problem and solver it by forcing chromedriver 2.24 to install by manually removing webdriver-manager

delete the folder rm -rf /usr/local/lib/node_modules/webdriver-manager/

reinstall webdriver npm install -g webdriver-manager

Upvotes: 1

bindul
bindul

Reputation: 66

As mentioned by others, looks like it is a problem with the chromedriver installed in the system with the new version of chrome. For mac, I updated the chromedriver using 'chromedriver-update' and this fixed it.

Upvotes: 2

Kat Russo
Kat Russo

Reputation: 469

I installed ChromeDriver v2.24 and stored it in: /usr/local/Cellar/chromedriver/2.24/bin and it fixed the error for me.

Upvotes: 7

Related Questions