The problem might be that your routes are not available at resolve time. You can go load the things later, but it doesn't matter any more, the router already failed.
You could put the router loader config into app initializer though. Then routes would get loaded before the app starts. Can't create an example for you on the phone, but Google got me here, looks good, you just need to adjust it: https://stackblitz.com/edit/angular-app-initializer-load-config?file=app%2Fapp.module.ts. Alternatively, if this doesn't work for you, you can do tricks. Step 1: Have a catchall route (`path: '**'`) that renders some dummy component ("Loading, please wait..."). So if you go to root path, you get your app component, and if you go to anything else, you land here - and start loading router config. Step 2: Add a bit of extra work to the loader, tell it to check the router state, and if you're at the dummy component, take the url and renavigate to it. Hope those ideas can give you a hint. Zlatko -- You received this message because you are subscribed to the Google Groups "Angular and AngularJS discussion" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
