angular: CanActivate not called on redirectTo router rule; but no error either

The current workaround is to create a dummy component and call the redirect logic inside a guard. Not pretty but it does the job.

need updates on it. I am also facing same problem

Is there any update regarding this issue?

Do we have update on this?

i’ve the same problem, any news?

For me this issue was occurred due to incorrect position of ** route path. Whenever you are importing “**” route path make sure that you add this in the end of your import list. For example:

imports: [
    // RouterModule.forRoot(defaultRoute),
    RouterModule.forRoot(sharedRouteTable),
    RouterModule.forRoot(adminRouteTable),// this is secure route array with Canative
    RouterModule.forRoot(websiteRouteTable),
    RouterModule.forRoot([
      /*
        all available routes here and above this
      */
      {
        path: "notfound",
        component: ErrorpageComponent
      },
      {// this path should be at the end 
        path: "**",
        // component: ErrorpageComponent
        // , 
        redirectTo: "notfound"
      }])
  ]

Hi all, I’m updating this to be a feature request / use-case that doesn’t have a clear recommendation (docs needed, error message needed). In the meantime, maybe a cleaner solution than a dummy component would be to have a route with an empty children array. This route could still be “activated” and would run the guards, allowing you to redirect properly.

const routes = [
  {path: 'redirectMe', children: [], canActivate: [Redirector]},
  {path: 'redirected', component: Redirected},
];

https://stackblitz.com/edit/angular-ivy-router-base-nka13t?file=src%2Fapp%2Fapp.module.ts

I understand but it still doesn’t make it a fix lol. Glad you don’t need a fix but it is a part of making Angular better and why we have issue trackers here on Github. I doubt it is a priority to the devs but if you just want a workaround, there already is a site for it called Stackoverflow.

Oh, I agree…there should be bug fixes to make existing features work. I groan at the religious adherence to so-called “agile” thinking and doing multiple full version number releases a year…If were king the practice would be to make APIs stable, and functioning correctly before letting some newbie create new features and break old ones. (Of course, that should go also for all software from Apple, Google, Facebook, Microsoft, etc, etc, etc).

this is working solution for me in Angular 11

{
    path: '',
    canActivate: [DefaultRouteGuard],
    children: [],
    pathMatch: 'full'
  }

in the route guard you have the logic to redirect router however you like.

So it can be a temporary workaround until an actual fix for this bug comes around.

OMFG…until a fix…I am the one who wrote this original bug report and that was 3 and a half YEARS ago! I’ve actually retired since, and a good thing I didn’t hold my breath for this and many other bugs to be fixed over the years. I don’t know what IS being worked on but like most programmers, they want to work on new stuff rather than make the existing stuff work correctly.

this is working solution for me in Angular 11

{
    path: '',
    canActivate: [DefaultRouteGuard],
    children: [],
    pathMatch: 'full'
  }

in the route guard you have the logic to redirect router however you like.

Although this is technically working (and probably the workaround most people are using right now) it is not a solution because you are not using the redirectTo parameter, which handles the redirection logic. So it can be a temporary workaround until an actual fix for this bug comes around.