Possibly unhandled rejection with Angular 1.5.9

[skidvd]

When using ui-router v-0.2.18 and angularjs v-1.5.9 I keep getting this error 4 times:

Possibly unhandled rejection: {}
I was not getting this error with 1.4.x angular verisons, but am now that I have upgraded. Google searches are not turning up much related to this issue.

I also noticed this error shows up as soon as I insert the ui.router module.

[ave-sanket]

Same issue with me to using angular js v -1.5.9 and ui-router v-0.2.15.
Does reverting to 1.4.8 makes this go away?

[skidvd]

Yes, in my case I was a 1.4.2 before attempting the 1.5 upgrade. Reverting to 1.4.x does make the error go away.

[lucax88x]

happened the same upgrading from 1.5.8 to 1.5.9

this can be linked to #2699

anyway, a quick fix is to use this:

https://docs.angularjs.org/api/ng/provider/$qProvider

in order to set errorOnUnhandledRejections to false

[skidvd]

@lucax88x, I attempting to apply the workaround you mentioned but not having any luck. Likely, I'm not understanding what you intend for me to do. Apologies if I am missing something obvious, but there does not appear to be useful examples of how to do this via google search.

I have modified my application's .run() function to call $q.errorOnUnhandledRejections(false); However, it keeps telling me that errorOnUnhandledRejections is not a function. Changing to .run() to literally set the value ($q.errorOnUnhandledRejections = false) succeeds (does not produce an error), but does not have any affect on the possibly unhandled rejection {} errors. Is it nor possible to make this change globally in the application? Do I need to do something to each and every time I access $q?

TIA!

try $qProvider.errorOnUnhandledRejections(false)

[skidvd]

@danivarga,

I'm sorry for the basic question, but I am missing something obvious. I have tried to inject $qProvider in both the typical manner - .run(['$qProvider', function($qProvider) {....}]); as well as via the $injector

$injector.invoke(['$qProvider', function($qProvider) {
    $qProvider.errorOnUnhandledRejections(false);
}]);

Both approaches result in Unknown Provided $qProviderProvider errors. Of course, without injecting a reference somehow, the $qProvider.errorOnUnhandledRejections(false) fails with an unknown $qProvider error.

I've also add 'ng' to my module list as well as attempted via the following approach, without success:

var $injector2 = window.angular.injector(['ng']);
$injector2.invoke(['$qProvider', function($qProvider) {
    $qProvider.errorOnUnhandledRejections(false);
}]);

How do I get a reference to this bad boy in my .run() function?

[christopherthielen]

Not .run(), but rather .config()

[skidvd]

@christopherthielen Of course, that makes more sense. Thank you!

Does anyone know if an official 'fix' for this issue is/will be worked, or is this the proper solution?

[HascourAdrien]

Would like to know aswell if the 1.5.9 will have this error unless we don t set to false the errorOnUnhandledRejections

[akholodenko]

1.6.0-rc.0 has the same problem and is solved via the same workaround:

app.config(['$qProvider', function ($qProvider) {
    $qProvider.errorOnUnhandledRejections(false);
}]);

This error throwing ideally should be off by default and backward compatible.

[christopherthielen]

This is fixed in 1.0 branch

[christopherthielen]

closed by 66ab048