vue-router — Uncaught (in promise) Error: Redirected from "/login" to "/" via a navigation guard

I spent hours debugging this and got to the following results for the ugly Uncaught (in promise) Error: Redirected when going from ... Error.

Note that the error is not for the "redirect". It's for the initial caller of the first navigation. Keep reading...

It's by design. Why?

Read this comment.

TL;DR: Let's say you are on page A, and click on a button to take you to page B (kinda like method: goToB() { router.push('/B'); } on page A). But there is a Navigation Guard for page B, that sends you to page C.

This error is a way for letting that goToB() function know that the router hasn't been able to fulfill the desired task, and the user hasn't landed on /B.

It's nasty, but informative

The biggest confusion here is that the redirect (landing on Page C) is, both:

• an "expected" outcome to you, the architect of the system. But, at the same time,
• an "unexpected" event to the caller of goToB in page A (i.e. router.push), who expects the router to go to page B.

That's why when it's popped as Error, it's confusing and frustrating to "you", who looks at the system entirely and thinks nothing is wrong or erroneous!

Urrrgh... So, what should I do?

Solution 1: Use router-link if you can

I ran into a case that <router-link> was working fine, but router.push was complaining. (I think router-link internally suppresses such errors.)

Solution 2.1: Individual suppress errors on each router.push call

The router.push function is returning a Promise (as it can be considered, or will be, an asynchronous job). All you need to do is to suppress any Error it might throw via

router.push('/B').catch(() => {});//     Add this: ^^^^^^^^^^^^^^^^

Solution 2.2: Augment Router.prototype.push to always suppress errors

If you think you have multiple instances of this, you can augment the push function on the prototype of the Router via the snippet on the same comment to apply this to all the router.push calls on the entire app.

The good news is it's giving you granularity level to choose which error you want to suppress (e.g. only NavigationFailureTypes.redirected ones, for example. The enum is here)

If you are on TypeScript, be my guest on the conversion and typing https://gist.github.com/eyedean/ce6ab6a5108a1bd19ace64382144b5b0 :)

Other tips:

1. Upgrade your vue-router! Your case might be solved by the time you read this. (As they have a plan to do so, apparently.)
2. Make sure you are not forking or reaching to dead-end in your Navigation Guards, if you have multiple ones. Follow them one by one and track them step by step. Note that, double redirecting is fine (thanks to this answer), you just need to be double careful!
3. I also got a playground here: https://codepen.io/eyedean/pen/MWjmKjV You can start mimicking this to your need to figure out where your problem happens in the first place.

The error message is getting updated in the next version of vue-router. The error will read:

Redirected when going from "/login" to "/" via a navigation guard

Somewhere in your code, after being redirected to "/login", you are redirecting back to "/". And vue-router is complaining about. You'll want to make sure you only have one redirect per navigation action.

I had a similar error, but for an onboarding redirect in .beforeEach, which was resolved by replacing in the .beforeEach conditional logic:

next({ name: "Onboarding" });

with

router.push({ path: 'Onboarding' });