Hi, I am running a reasonably high traffic mobile site written in angular (currently 1.2.15). I have hooked into the angular exception logging pipeline so that I can send any unexpected client side errors back to the server to log them. One of the main remaining sources of error are frequent tpload and tplrt errors coming from angular.
There is nothing wrong with the templates being loaded because the problem is generally not happening and has never been noticed in test. The errors tend to come in flurries for the same user, i.e. I might see 5 or 10 tpload errors for the same user with the same timestamp. It is as if the user is changing routes and all templates for that route have failed. There do not appear to be any correlated errors on the server. My first though that this might be some sort of temporary network issue, but that begs the question, how are we able to successfully replay the error back to the server if there is no network? I have modified the angular source temporarily to trace the response, status code and headers as well as the url of the failing template lookup. Interestingly the response, status and headers are always empty (or at least they are falsey so they could be 0 I guess). Has anyone else experienced this? Has anyone got any ideas about what might be going on or any advice for further diagnosis? I would love to get to the bottom of this. Thanks in advance. Julian Jelfs. -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
