"Cannot match any routes" after page refresh about localize-router HOT 19 CLOSED

@meeroslav
What about Angular 4.0.0 support?

from localize-router.

Resolved with Angular version 2.4.9

from localize-router.

The new version should be there in few days, I'm working on tests.

In the meantime, if you don't mind npm complaining, version 0.6.4 is fully functional with Angular Core 2.4.9 (and Angular Router 3.4.9).

from localize-router.

Version 0.7.0 supports Angular 4

from localize-router.

Can you provide more information:

• what route are you loading?
• how does your appRoutes look like?
• if possible provide link to your repo

Thanks

from localize-router.

@meeroslav It's part of enterprise project, so it's not available online.

My appRoutes is simple:

export const appRoutes: Routes = [
  {
    path: '',
    component: DashboardComponent
  },
  {
    path: 'admin',
    children: [
      {
        path: 'active-sessions',
        component: AdminActiveSessionsComponent
      }
    ]
  }
];

1. Load homepage
2. Go to admin/active-sessions
3. Refresh the page (F5)
4. Error

from localize-router.

Well, admin/active-sessions should be invalid.
Once localize-router kicks in, proper URL should be e.g. en/admin/active-sessions so the message you get is correct.
Do you navigate through the application to the given route or you modify the browser URL manually?
Former would be a bug in localize-router while later would be expected behavior.

Please note that there is possibility to add flag to exclude certain routes from the localization process, but it's not yet implemented.

from localize-router.

@meeroslav Sure, it's en/admin/active-sessions. I skipped this for clarity.
I navigate through the application. I just refresh the page by pressing F5.

from localize-router.

@mrzepinski This would notmaly happen if you would be using lazy loaded routes (#3). If this is not the case, then I will investigate it as soon as possible.

from localize-router.

@meeroslav It's not this case. I'm not using lazy loaded routes.

from localize-router.

This is caused by router version 3.4.8. Seems that navigation kicks in before APP_INITIALIZER finishes.

from localize-router.

Yeah, looked into the changes (angular/angular@2.4.7...2.4.8).
Looks like the process changed. They added a LOCATION_INITIALIZED which might help

from localize-router.

This will break the backwards compatibility unfortunately, not to mention 4.x.x versions.
I need to investigate more to find proper solution.

from localize-router.

Issue mentioned in angular/angular#14615

from localize-router.

Workaround for version 2.4.8. can be found here: angular/angular#14588.

Proper solution will be done soon.

from localize-router.

Any update on this?

from localize-router.

Nice.

Any plans to support the new process that is used in Angular 4? There will apparently be a legacy option that makes it work like in 2.x but you can't use that with Universal.

from localize-router.

@meeroslav
When are we going to have a new version supporting Angular 2.4.9?

from localize-router.

On it. Sorry for waiting.

from localize-router.