ApplicationRef.isStable is always false when using this package #965
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe the bug
When you kick-off the setup (with checkAuth) then this package will create intervals and timeouts. When using Service workers it's important to get the application into stable mode or else the new version isn't downloaded. However this is not possible because this package is making it unstable and it will never turn stable.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
intervals and timeouts should be run outside the NgZone so that it wont interfere with the "stability" of Angular.
This package reaches stable for me when these two culprits are run outside angular:
angular-auth-oidc-client/projects/angular-auth-oidc-client/src/lib/callback/intervall.service.ts
Line 18 in 710af82
angular-auth-oidc-client/projects/angular-auth-oidc-client/src/lib/iframe/check-session.service.ts
Line 132 in 03aa2ad
#961