🐞 bug report

Affected Package

@angular/router

Description

The state passed to router.navigate is lost when doing multiple navigations.

🔬 Minimal Reproduction

https://stackblitz.com/edit/angular-nrjzxe

Pressing 'FOO' will call router.navigate with state { foo: true }.
If you press it once, you will see in the console that the resolver can see this state (via getCurrentNavigation).
If you press it multiple times quickly (the resolver takes two seconds), all but the last navigation are canceled and during the navigations past the initial one, the resolver can no longer see this state.

I would expect to always be able to access the state from the resolver.

🌍 Your Environment

Angular version 7.2.5

EDIT: Some more info:
Looks like currentNavigation is set to null here:

It is then null here, contradicting the '!' non-null assertion operator:

Thus you are left with a currentNavigation only containing finalUrl.