If the error comes up in a reasonable amount of time (minutes of using the application) easiest thing is to get your developer tools to break and enter debug mode on error. That way you can catch it when it happens and hopefully find the issue.
With callbacks and promises and delayed code it can be hard to find the source of a bug. The Angular team is working on "Zones" http://thechangelog.com/zone-js/ which can help address this. Haven't personally played with it, but watching the talks looks promising. On Thursday, 6 March 2014 13:13:11 UTC-8, Orlando Cardoso wrote: > > Hi, > > I've got an internal Angular App in production that's working really well > - except from logs I can tell there are 2 sporadic issues. Unfortunately I > can't reproduce them, and I haven't noticed any particular pattern (page, > browser, data, etc). Does anyone have any suggestions, other than Googling > (which hasn't born any fruit), for how I can go about better > troubleshooting these types of issues? Is there something else I can and > should be logging? Is there something I can do in the Exception > interceptor to get a better idea of what's triggering these? > > To get an idea of what I am logging, here's the issues (I don't expect > anyone to know what's going on just from these.. so i'm just looking for > tips on how to figure it out). > > > <https://lh6.googleusercontent.com/-qMgbm_I2Ah4/UxjijyfSUtI/AAAAAAAAAwo/QBT8zLdC3JM/s1600/2014-03-06_12-55-30.png> > > > > <https://lh4.googleusercontent.com/-ErPsXapURqI/UxjkXudhLXI/AAAAAAAAAw8/wXLnPAoVHLk/s1600/2014-03-06_13-10-36.png> > > > > thanks in advance, > > Orlando > -- 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.
