Open vdias38 opened 6 years ago
Sorry but I don't understand the fix. Please can you explain. On link you provided I read
If you need to navigate to a page which does not use Angular, you can turn off waiting for Angular by setting browser.waitForAngularEnabled(false)
In our case we use Angular then I don't understand why we should turn off waiting for Angular.
And on same page, to fix the issue I read
How to change: Add allScriptsTimeout: timeout_in_millis to your Protractor configuration file. You may also need to fix this problem with a change to your application.
Why don't we follow the recommendation and do stg out of our context ?
I recommend to migrate to at least angularfire2 5.0.0-rc.8, because the owner of project angulafire2 has recognized the error. I've tried to install angularfire2@5.0.0-rc.7 but raise another issue
$ npm install --save angularfire2@5.0.0-rc.7
Runtime Error
Zone Already loaded.
Fixed on angularfire2 5.0.0-rc.8: fix(): Zone already loaded, type implied (#1631)
I couldn't find a scenario when it not demands a lot of updates/breaking changes
Expected behaviour
Tell us what should happen
Actual behaviour
If I user mock of user-profile service, it works well, but with real service travis raises an error:
Failed: Timed out waiting for asynchronous Angular tasks to finish after 11 seconds.
Steps to reproduce
1. 2. 3.
Expected responses