How to make app routing allow access to /ngsw/state

[Jun711]

📚 Docs or angular.io bug report

Description

The document doesn't specify how to access ngsw/state if we use routing module.

🔬 Minimal Reproduction

What's the affected URL?**

https://gist.github.com/alxhub/76aa639d9a37cdca30938f7938d9146c

🔥 Exception or Error

core.js:15713 ERROR Error: Uncaught (in promise): Error: Cannot match any routes. URL Segment: 'ngsw/state'
Error: Cannot match any routes. URL Segment: 'ngsw/state'
    at ApplyRedirects.push../node_modules/@angular/router/fesm5/router.js.ApplyRedirects.noMatchError (router.js:2469)
    at CatchSubscriber.selector (router.js:2450)
    at CatchSubscriber.push../node_modules/rxjs/_esm5/internal/operators/catchError.js.CatchSubscriber.error (catchError.js:34)
    at MapSubscriber.push../node_modules/rxjs/_esm5/internal/Subscriber.js.Subscriber._error (Subscriber.js:79)
    at MapSubscriber.push../node_modules/rxjs/_esm5/internal/Subscriber.js.Subscriber.error (Subscriber.js:59)
    at MapSubscriber.rxjs.Subscriber.error (zone-patch-rxjs.js:167)
    at MapSubscriber.push../node_modules/rxjs/_esm5/internal/Subscriber.js.Subscriber._error (Subscriber.js:79)
    at MapSubscriber.push../node_modules/rxjs/_esm5/internal/Subscriber.js.Subscriber.error (Subscriber.js:59)
    at MapSubscriber.rxjs.Subscriber.error (zone-patch-rxjs.js:167)
    at MapSubscriber.push../node_modules/rxjs/_esm5/internal/Subscriber.js.Subscriber._error (Subscriber.js:79)
    at resolvePromise (zone.js:831)
    at resolvePromise (zone.js:788)
    at zone.js:892
    at ZoneDelegate.push../node_modules/zone.js/dist/zone.js.ZoneDelegate.invokeTask (zone.js:423)
    at Object.onInvokeTask (core.js:17279)
    at ZoneDelegate.push../node_modules/zone.js/dist/zone.js.ZoneDelegate.invokeTask (zone.js:422)
    at Zone.push../node_modules/zone.js/dist/zone.js.Zone.runTask (zone.js:195)
    at drainMicroTaskQueue (zone.js:601)

[gkalpak]

You don't need to do anything special other than navigate to that URL. It should work the same regardless if your app uses routing or not.
If you are running into issues, please provide a minimal reproduction (and exact steps to use to reproduce the issue) and I'd be happy to look into it.

(BTW, since /ngsw/state is handled by the SW, it will only work if the SW has already been activated. So, you need to visit your page once, wait for a few seconds for the SW to be registered/installed/activated and then navigate to /ngsw/state.)

[Jun711]

@gkalpak
right, when I tried with ng serve, it didn't work as no service worker was installed.
it worked when I used http-server.
it wouldn't on my production website because of redirection so I have to make ngsw/state accessible then.

thanks.

[gkalpak]

Not sure why it wouldn't work on your production, though 😕

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}