Returning a rejected promise in router Resolver throws an error

[jasonaden]

Rejecting a resolve will cause an error ERROR Error: Uncaught (in promise): TypeError: Cannot read property 'ngNavigationCancelingError' of null. This effectively stops navigation, but is an unintended error.

The problem with this error is that creating an instance of NgNavigationCancelingError is a private API. Therefore in user-land there doesn't seem to be a way to reject a resolve.

[nikkwong]

I can also confirm the presence of this bug, but for now I got it to work by returning Observable.fromPromise() and then using resolve or reject from that promise as per you usually would.

[daniel-mcassey-tmsuk]

Having the same issue

[mahmood-sajjadi]

yes same issue here
I found another ugly workaround!

https://github.com/angular/angular/blob/master/packages/router/src/router.ts#L735
if (isNavigationCancelingError(e)) {
https://github.com/angular/angular/blob/master/packages/router/src/shared.ts#L100:L104
export function navigationCancelingError(message: string) { const error = Error('NavigationCancelingError: ' + message); (error as any)[NAVIGATION_CANCELING_ERROR] = true; return error; }

so ugly solution is:
return Observable.throw({message: 'some message', ngNavigationCancelingError: true});

the important part is :
ngNavigationCancelingError: true
becuse:
https://github.com/angular/angular/blob/master/packages/router/src/shared.ts#L98

Hope it helps someone

[Dashue]

+1

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}