Before you fix this issue, it is worthwhile to understand the knock-on effects of the failing API call:
- Observe the console errors:
Dev Tools Console Error Context
The first element of note here is the ERROR CONTEXT object, which has a property named DebugContext_. The DebugContext_ contains a detailed snapshot of the current state of your Angular application when the error happened. The information contained within DebugContext_ is light years ahead of the amount of mostly unhelpful error messages AngularJS generates.
Properties that have the value (...) are property getters, and you must click on them to load ...
