-
Notifications
You must be signed in to change notification settings - Fork 27.4k
10 $digest() iterations reached using $locationWatch #3915
Comments
Just to help anybody who has this issue out, I had to make a line addition to the Angular lib after line 11221 with: headless = $window.navigator.appName == "Node.js jsDom" ? true : false, and later on line 11253 made the change: history: !!($window.history && $window.history.pushState && !(android < 4) && !headless), |
So the issue is that $location doesn't play well when the browser URL is changed by something outside of the control of Angular. For instance, the browser itself on Android or if you are using some 3rd party library such as jQuery. |
I totally agree, I'm only attempting to help those that may be in specific situation, Using Nodejs with Zombie. Its not a universal fix, and there has been a Boxee Box fix that is as specific as mine stated above, its was merged into the master branch of angular. I disagree with that move as well, since as you stated, it needs to be a universal fix. |
Please, can we reopen this issue to add more vintage Webkit browsers? My konqueror 4.6.5 + webkit 1.0 (=533.3, productSub = 20030107) has the same issue. |
Had the same issue when using browser.history API directly. In case you need to change the URL without using $location service etc. you can invoke
|
Hi, Could you check if this issue is still there? |
Angular you're not making my testing life easier :(. I'm using:
If i do
Error trace:
https://docs.angularjs.org/error/$rootScope/infdig I'll end up doing somethig awful like:
Any better idea? |
@cortezcristian |
@cortezcristian - this is possibly related to #9635. Can you look at #9923 - to see if that fixes it? |
This should now be fixed by @assaf in assaf/zombie@d5f92bd |
Sounds like this issue probably can be closed now. |
Thanks |
Oh noes! Not this issue again!
I'm using the Zombie headless browser, Nodejs, Angular 1.2.0rc1 and i'm getting the same iteration loop error.
It seems as though this issue is related to #2815
as well as this thread:
https://groups.google.com/forum/#!topic/angular/mRIo8LaTh4M
and the recent change for Boxee Box.
My thought is that there has to be some sort of universal fix instead of making exceptions for each instance where this comes up?
Anybody?
The text was updated successfully, but these errors were encountered: