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

Question

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

Try re-installing protractor. even i was facing the same issue today. — Sudharsan Selvaraj, CommentedOct 25, 2016 at 8:51
Or install protractor with below version npm install [email protected] -g — Sudharsan Selvaraj, CommentedOct 25, 2016 at 8:54
I haven't changed anything in my setup and I'm experiencing the same thing this morning... only on chrome. Firefox and others run fine, must be a driver issue. — Gunderson, CommentedOct 25, 2016 at 12:26
this might be a duplicate of stackoverflow.com/questions/38918486/… — adam, CommentedOct 25, 2016 at 17:43

Kat Russo · Accepted Answer · 2016-10-25 18:30:28Z

7

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

answered Oct 25, 2016 at 18:30

Kat Russo

4694 silver badges8 bronze badges

That worked for me too. The important part is to put the chromedriver on your path as described here: watir.github.io/docs/chrome Just that the version linked to in the watir documentation is confusing. Using chromedriver.storage.googleapis.com/index.html?path=2.25 should work.
– Robert
CommentedNov 1, 2016 at 19:40

Add a comment |

bindul · Accepted Answer · 2016-10-25 19:27:49Z

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.

wnordmann · Accepted Answer · 2016-10-26 01:08:41Z

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

DevGrowth.Tech · Accepted Answer · 2016-10-27 20:29:06Z

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)

Evers · Accepted Answer · 2016-11-08 16:12:26Z

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

Collectives™ on Stack Overflow

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

5 Answers 5

Linked

Hot Network Questions

Collectives™ on Stack Overflow

5 Answers 5

Linked

Related