Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

ScriptTimeoutError: asynchronous script timeout: result was not received in 0 seconds

See original GitHub issue

I’m getting this error occasionally, making all previously-passed tests failed. I saw this code driver.manage().timeouts().setScriptTimeout(5, TimeUnit.SECONDS); from

http://stackoverflow.com/questions/11646586/unable-to-execute-selenium-asynchronous-script

but I don’t know how to run something like that from my protractor test. How should I proceed with this?

Issue Analytics

State:
Created 10 years ago
Comments:10 (4 by maintainers)

Top GitHub Comments

6reactions

pulkitsinghalcommented, Jun 10, 2014

@juliemr - with latest versions of protractor, you may want to update the docs again by replacing ptor.driver with browser

onPrepare: function() {
    // Override the timeout for webdriver.
    browser.manage().timeouts().setScriptTimeout(60000);
  },

0reactions

harin10commented, May 15, 2018

I am getting a similar error could you please help me out. I tried the above options but I still see the issue.

[18:00:34] E/plugins - ScriptTimeoutError: asynchronous script timeout: result was not received in 60 seconds (Session info: chrome=66.0.3359.139) (Driver info: chromedriver=2.38.552522 (437e6fbedfa8762dec75e2c5b3ddb86763dc9dcb),platform=Windows NT 6.1.7601 SP1 x86_64) at Object.checkLegacyResponse (X:\projects\Protractor\COSTCO_APP\node_modules\selenium-webdriver\lib\error.js:546:15) at parseHttpResponse (X:\projects\Protractor\COSTCO_APP\node_modules\selenium-webdriver\lib\http.js:509:13) at doSend.then.response (X:\projects\Protractor\COSTCO_APP\node_modules\selenium-webdriver\lib\http.js:441:30) at process._tickCallback (internal/process/next_tick.js:109:7) From: Task: WebDriver.executeScript() at Driver.schedule (X:\projects\Protractor\COSTCO_APP\node_modules\selenium-webdriver\lib\webdriver.js:807:17) at Driver.executeAsyncScript (X:\projects\Protractor\COSTCO_APP\node_modules\selenium-webdriver\lib\webdriver.js:891:17) at run (X:\projects\Protractor\COSTCO_APP\node_modules\protractor\built\browser.js:59:33) at ProtractorBrowser.to.(anonymous function) [as executeAsyncScript] (X:\projects\Protractor\COSTCO_APP\node_modules\protractor\built\browser.js:67:16) at Object.waitForPromise (X:\projects\Protractor\COSTCO_APP\node_modules\protractor-xhr-only-plugin\index.js:60:10) at resolver (X:\projects\Protractor\COSTCO_APP\node_modules\protractor\built\plugins.js:194:51) at new ManagedPromise (X:\projects\Protractor\COSTCO_APP\node_modules\selenium-webdriver\lib\promise.js:1077:7) at Plugins.safeCallPluginFun (X:\projects\Protractor\COSTCO_APP\node_modules\protractor\built\plugins.js:210:20) at promises.pluginObjs.filter.map.pluginObj (X:\projects\Protractor\COSTCO_APP\node_modules\protractor\built\plugins.js:219:40) at Array.map (native)

Top Results From Across the Web

Protractor - ScriptTimeoutError: asynchronous script timeout ...

So it's kind of a software bug, not a protractor error. ... Timed out waiting for asynchronous Angular tasks to finish after 20...

Script timeout - WebDriver - MDN Web Docs

The script timeout error is a WebDriver error that occurs when a script the user has provided did not complete before the session's...

Script timeout in Protractor - SQA Stack Exchange

I think ,the element was not located and the system tries to locate it for 150000 millisec but after 120000 throws timeout error....

Protractor – ScriptTimeoutError: asynchronous script timeout ...

Javascript – Protractor – ScriptTimeoutError: asynchronous script timeout: result was not received in 20 seconds. automationjasminejavascriptprotractor.

angular/protractor - Gitter

and I'm getting this error: ScriptTimeoutError: asynchronous script timeout: result was not received in 11 seconds. Why would I get a timeout after...