-
Notifications
You must be signed in to change notification settings - Fork 27.6k
[1.1.5] HTML5 mode causes the dreaded "10 $digest iterations reached" error #3397
Comments
I'm also having the same issue with the
|
👍 |
Also getting this issue on IE 7/8/9 and compatibility modes, here, is Stackover flow link : http://stackoverflow.com/questions/19276261/script5022-10-digest-iterations-reached-aborting-and-redirecting-to-index
|
@ravishtiwari This is fixed in 1.2, I applied the patch to our local version of 1.1.5, and we are serving that locally instead of using the CDN version. The 1.2 commit that fixes it is dca2317 |
@jrabbe thanks for update, I'll try upping my version of Angular JS/patching my local Angular JS version, and see if this resolves problem for me. |
@jrabbe I updated my version of Angular, and this seems to resolve this "10 $digest() iterations reached. Aborting!", however, it still seems to be triggering URL change, leading it to redirect to home page. Let me explain my scenario here, so that others can suggest me if this is exactly related to this or not: After upping the version of Angular, now, Modal seems to loading the app for a second, then, redirect happens, and it goes to home page. FYI, I am also using jQuery on the page that is used to launch the Angular App, is there any chance of conflict due to this? |
@Ravish make sure you investigate your routes in details since that is what can redirect your app, especially if you have an |
I'm going to close this since I believe it has been fixed in |
I am getting this on the latest version of angularjs also when I use ng-include in my code |
@chaudhary my experience so far with this error has been : it's caused by either route configuration, or if you have some js/mark up that is freaking out angular.compile, so, dig deeper ;) |
I do see that there are several issues on the 1.1.5 URL routing, but this specific issue doesn't seem to have been reported.
We are using a setup combining Require.js and angular together. After I turned on minification a problem that we had been seeing occasionally suddenly started occurring always. As I was removing template code it eventually went away after I removed the last trace of angular in the code. Just adding back a simply
ng-include
element would cause the problem to re-appear.It might be that the require.js connection is a red herring, because I discovered that removing
$locationProvider.html5Mode(true);
from our app caused the problem to come back. We can probably survive without html5mode, but it would be much much better to have it.Logs: (don't worry, jonas.radius.com is just a localhost alias, not public)
The text was updated successfully, but these errors were encountered: