I’m using @ngrx/router-store in my Angularv5 app and I recently started running into a an error:
Navigation ID X is not equal to the current navigation id Y (where X and Y are integers).
This problem happens consistently when I navigate to route A from a specific route B. Navigating to route A from any other route seems to work fine.
The only other S.O. issue related to this which I’ve found, offers up the possibility that the issue could be caused by rapidly updating the navigation multiple times. To test if this was happening (it shouldn’t be), I subscribed to router navigation events inside my root component, set a breakpoint inside the subscription, and opened up a debug session to step through the problem. Doing this, I can see that
Say the current navigation ID is 11. When I navigate to the problem route, the router starts navigation, successfully executes every navigation event including
NavigationEndand then immediately @ngrx/router-store throws an
'ROUTER_CANCEL'action stating that:
Navigation ID 12 is not equal to the current navigation id 13. As far as I can tell, 12 is the correct navigation ID (again, navigation ID 11 completes and immediately
'ROUTER_CANCEL'is thrown without the router emitting any further navigation events). Furthermore, the
'ROUTER_CANCEL'action payload contains both the router navigation event that caused the problem, as well as the state of the store when the problem was caused. The event which caused the problem has an ID of 12, the router state in the store at the time had an ID of 11. So again, 12 seems to be the correct navigation ID and should not be throwing an error.
On navigation to the user profile route from a problem route, no other navigation occurs until @ngrx/router-store cancels navigation. (i.e. I am not rapidly updating the navigation route)
Other than ngrx dispatching a
'ROUTER_CANCEL'action, no errors are reported (and no errors are thrown).
Again, the route experiencing problems works fine unless navigation begins from a specific route B. As far as I can tell, there is nothing different or unusual about this specific route B (nor does the problem route A care where people are coming from–the two routes have no association with each other).
One last thing: triggering the bug outside of a debug session always seems to cause errors in the form
Navigation ID X is not equal to the current navigation id X+1, however triggering the bug inside a debug session might cause
Navigation ID 11 is not equal to the current navigation id 15 or
Navigation ID 13 is not equal to the current navigation id 20, etc.
Does anyone have any ideas what is going on? I’m not familiar enough with @ngrx/router-store to really guess how this might be happening. My assumption is that the navigation ID value in the store increases synchronously when
NavigationEnd events are received by @ngrx/router-store, so I’m not even sure how the ids could ever get out of order—let alone in this case where the ids appear to be correct.
Any thoughts are greatly appreciated!
PS: I’m happy to post code, but my app is large and I don’t have any clues as to where this bug is being triggered from.
I figured it out! There was code in a component that was calling
router.navigate() on a
NavigationEnd event. So the answer was similar to the answer in this S.O. issue (rapidly changing the route).
I got this error because I was calling router.navigate twice in quick succession, (1 to append queryParams, 1 to append a fragment) so had to refactor my code to only call navigate once.
Answered By – John
Answer Checked By – Katrina (BugsFixing Volunteer)