You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm seeing other people used to have this issue, then it was supposedly fixed in 0.1.0 and then reintroduced in 0.1.1. But even downgrading to 0.1.0 doesn't stop it from occurring. It fails at the very first expect and raising the timeout doesn't fix it either.
The text was updated successfully, but these errors were encountered:
I had the same issue when some of libraries where setting $timeouts for some time in future. Angular was treating this as if some actions were still in progress and capybara-angular eventually timed out. Same behavior might occur if you have pending $http request. Here is from protractor docs Before performing any action, Protractor asks Angular to wait until the page is synchronized. This means that all timeouts and http requests are finished. If your application continuously polls $timeout or $http, it will never be registered as completely loaded. You should use the $interval service (interval.js) for anything that polls continuously (introduced in Angular 1.2rc3).
I'm seeing other people used to have this issue, then it was supposedly fixed in 0.1.0 and then reintroduced in 0.1.1. But even downgrading to 0.1.0 doesn't stop it from occurring. It fails at the very first expect and raising the timeout doesn't fix it either.
The text was updated successfully, but these errors were encountered: