Skip to content

TimeoutError when making a request without a token #589

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
linjie997 opened this issue Jul 25, 2019 · 1 comment
Closed

TimeoutError when making a request without a token #589

linjie997 opened this issue Jul 25, 2019 · 1 comment

Comments

@linjie997
Copy link
Contributor

linjie997 commented Jul 25, 2019

Describe the bug
With the latest release, 8.0.0, when I make a simple request while I'm not authenticated yet, the request does not start and it gives a TimoutError:

Error: Uncaught (in promise): TimeoutError: Timeout has occurred at resolvePromise (zone.js:852) at resolvePromise (zone.js:809) at zone.js:913 at ZoneDelegate.push../node_modules/zone.js/dist/zone.js.ZoneDelegate.invokeTask (zone.js:423) at Object.onInvokeTask (core.js:26760) 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) at push../node_modules/zone.js/dist/zone.js.ZoneTask.invokeTask (zone.js:502) at ZoneTask.invoke (zone.js:487)

If I make a valid authentication so I have an access_token, the problem does not happen.
The problem does not happen also when setting sendAccessToken to false in the import of the module

Stackblitz example
https://stackblitz.com/edit/angular-pqssn1?embed=1&file=src/app/app.component.ts

To Reproduce
Steps to reproduce the behavior:

  1. Launch the stackblitz example
  2. Open the console
  3. See the error

Expected behavior
Should make the request without the token

Desktop (please complete the following information):

  • OS: Windows 10
  • Browser: Tested on Chrome and Firefox
  • Version: Latest stable

Additional context
Might be related to
#587
and
#515

@manfredsteyer
Copy link
Owner

Thanks for this info and this great error description.

It should work now with the version 8.0.2 which just landed on npm.

If not, feel free to reopen this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants