zone.js 0.8.18 - Protractor tests failed - Timed out waiting for asynchronous Angular tasks

[DosiaKroll]

We updated version for zone.js from 0.8.12 to 0.8.18. After this, all our e2e tests with Protractor stopped work. When test had to resolve any instructions with expect, finally finished with the same error, ex.:

Failed: Timed out waiting for asynchronous Angular tasks to finish after 60 seconds.
This may be because the current page is not an Angular application. Please see the FAQ for more details:
https://github.com/angular/protractor/blob/master/docs/timeouts.md#waiting-for-angular While waiting for
element with locator - Locator: By(xpath, //div[@id="dashboardBoxes"]/div)

We checked all versions since 0.8.12 to 0.8.17 and we hadn't issue with them, only with version 0.8.18. We couldn't find any workaround for this, so we're still using version 0.8.17, but if new Angular will be released, then I guess will use the new version of zone.js and our issue with e2e tests will come back.

[JiaLiPassion]

@DosiaKroll , could you post a reproduce sample? thanks.

[DosiaKroll]

What do you mean, do you want a complete project or part of configuration ex. protractor.conf.js, or part of a code? I'm asking because this company application, so I can't provide that info and if I create some small app then the issue may not occur because it is random, sometimes issue in the first step of test and sometimes somewhere in the midst of the test.

[JiaLiPassion]

@DosiaKroll , I want a project which can reproduce this issue, if you can make a sample project which can describe the issue, that will help a lot!

[DosiaKroll]

I tried to create a sample project for this, but everything is fine. In our general project is too much dependence and too many functionalities which are connected and I can't reproduce the issue in my project.

Is there any way to print currently active tasks? I am facing similar issue and I can see that 1 macroTask remains active for 30 seconds after app launch only when executing e2e tests.

[JiaLiPassion]

@surajbarkale-dolby , it is possible, could you provide a reproduce repo?

It turned out to be an issue with Firebase (angular/angularfire#1345). So, I do not think my issue is related to OP.

[jooreek]

We have same problem after update to 0.8.18. According to our investigation, it seems to be the same cause as described in #934

[adrienverge]

For your information, I have the same problem and pull request #935 solves it. Let's hope it can be merged soon!

[JiaLiPassion]

close for fixed.