Angular 1 6 0 Possibly unhandled rejection error

Question

We have a pattern for resolving promises in our Angular app that has served us well up until Angular 1 6 0       resource get    promise          then function  response               do something with the response            function  error                   pass the error the the error service             return errorService handleError error                 And here is how we are triggering the error in Karma       resourceMock get   function              var deferred    q defer            deferred reject error           return    promise  deferred promise             Now  with the update to 1 6 0  Angular is suddenly complaining in our unit tests  in Karma  for rejected promises with a  Possibly unhandled rejection  error  But we are handling the rejection in the second function that calls our error service   What exactly is Angular looking for here  How does it want us to  handle  the rejection

User · Answer

I had this same notice appear after making some changes. It turned out to be because I had changed between a single $http request to multiple requests using angularjs $q service.

I hadn't wrapped them in an array. e.g.

$q.all(request1, request2).then(...)

rather than

$q.all([request1, request2]).then(...)

I hope this might save somebody some time.

User · Answer

The first option is simply to hide an error with disabling it by configuring errorOnUnhandledRejections in  qProvider configuration as suggested Cengkuru Michael  BUT this will only switch off logging  The error itself will remain   The better solution in this case will be - handling a rejection with  catch fn  method   resource get    promise      then function  response           catch function  err         LINKS    Promise Angular     Migrating Angular 1 5 to 1 6  http  remove deprecated callback methods   success   error

User · Answer

Found the issue by rolling back to Angular 1 5 9 and rerunning the test  It was a simple injection issue but Angular 1 6 0 superseded this by throwing the  Possibly Unhandled Rejection  error instead  obfuscating the actual error

User · Answer

Try adding this code to your config   I had a similar issue once  and this workaround did the trick   app config    qProvider   function   qProvider         qProvider errorOnUnhandledRejections false

User · Answer

Please check the answer here   Possibly unhandled rejection in Angular 1 6     This has been fixed with 316f60f and the fix is included in the v1 6 1 release

User · Answer

It may not be your speficic situation  but I had a similar problem    In my case  I was using angular-i18n  and getting the locale dictionary asynchronously  The problem was that the json file it was getting was incorrectly indented  mixing spaces and tabs   The GET request didn t failed    Correcting the indentation solved the problem

User · Answer

The code you show will handle a rejection that occurs before the call to  then  In such situation  the 2nd callback you pass to  then will be called  and the rejection will be handled    However  when the promise on which you call  then is successful  it calls the 1st callback  If this callback throws an exception or returns a rejected promise  this resulting rejection will not be handled  because the 2nd callback does not handle rejections in cause by the 1st  This is just how promise implementations compliant with the Promises A  specification work  and Angular promises are compliant   You can illustrate this with the following code   function handle p        p then               gt                   This is never caught              throw new Error  bar                        err    gt                console log  rejected with   err                  handle Promise resolve 1       We do catch this rejection  handle Promise reject new Error  foo        If you run it in Node  which also conforms to Promises A   you get   rejected with Error  foo     at Object  lt anonymous gt    tmp t10 test js 12 23      at Module  compile  module js 570 32      at Object Module  extensions  js  module js 579 10      at Module load  module js 487 32      at tryModuleLoad  module js 446 12      at Function Module  load  module js 438 3      at Module runMain  module js 604 10      at run  bootstrap node js 394 7      at startup  bootstrap node js 149 9      at bootstrap node js 509 3  node 17426  UnhandledPromiseRejectionWarning  Unhandled promise rejection  rejection id  2   Error  bar

User · Answer

You could mask the problem by turning off errorOnUnhandledRejections  but the error says you re needing to  handle a possible rejection  so you just need to add a catch to your promise   resource get    promise      then function  response           do something with the response        catch function  error                pass the error to the error service         return errorService handleError error             Reference  https   github com angular-ui ui-router issues 2889

User · Answer

To avoid having to type additional  catch function        in your code in multiple places  you could add a decorator to the  exceptionHandler   This is a more verbose option than the others but you only have to make the change in one place   angular      module  app        config configDecorators    configDecorators  inject      provide    function configDecorators  provide          provide decorator   exceptionHandler   exceptionHandler        exceptionHandler  inject      delegate     injector        function exceptionHandler  delegate   injector            return function  exception  cause                 if   exception toString   toLowerCase    includes  Possibly unhandled rejection  toLowerCase                       console log exception      optional to log the  Possibly unhandled rejection                     return                             delegate exception  cause

User · Answer

I was also facing the same issue after updating to Angular 1 6 7 but when I looked into the code  error was thrown for  interval cancel interval   for my case  My issue got resolved once I updated angular-mocks to latest version 1 7 0

User · Answer

I have observed the same behavior during test execution  It is strange that on production code works fine and fails only on tests   Easy solution to make your tests happy is to add catch angular noop  to your promise mock  In case of example above it should looks like this    x000D   x000D  resourceMock get   function      x000D      var deferred    q defer    x000D      deferred reject error   x000D      return    promise  deferred promise catch angular noop     x000D     x000D   x000D   x000D

[javascript] Angular 1.6.0: "Possibly unhandled rejection" error

Examples related to javascript

Examples related to angularjs

Examples related to karma-runner

Examples related to angular-promise

Examples related to angularjs-1.6