Skip to content
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

timeout and idleStart function executing multiple times #106

Open
ZahraFatima opened this issue Jul 19, 2018 · 1 comment
Open

timeout and idleStart function executing multiple times #106

ZahraFatima opened this issue Jul 19, 2018 · 1 comment

Comments

@ZahraFatima
Copy link

I'm submitting a ... (check one with "x")

[ ] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/HackedByChinese/ng2-idle/blob/master/CONTRIBUTING.md#getting-help

Current behavior
Timeout and IdleStart function executing multiple times, sometimes its executing twice and sometimes its 6 times too. This results in multiple logout calls on timeout and multiple warning messages on idleStart.

Please Advice.

Expected behavior

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

  • @ng-idle version: 2.x I am using @ng-idle version: 2.0.0-beta.15
  • Angular version: 2.x
    I am using angular 5
  • Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

In all browsers this issue can reproduce.

  • Language: [all | TypeScript X.X | ES6/7 | ES5]
    Typescript version ~2.5.3

  • Node: node --version = v9.11.1

@Prinsn
Copy link

Prinsn commented Jan 10, 2020

Angular 7

I'm currently looking into a case when in one deployed environment, onTimeoutWarning is firing in excess of 100 times.

Currently have no information to offer (as I have no idea, am currently researching).

Works correctly in all testing environments except where it is occurring.

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