You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Working on trying to integrate the Observable signal sources I've bumped into a bug that's causing my sessions to get closed down right after returning from login.
The problem seems to be in the service handling code that is attempting to use setTimeout( ) in order to schedule a callback to pushTokenExpired( ) at the calculated expiration time. The calculated time seems to be correct, but instead of passing a reference to pushTokenExpired for future callback, the code is calling pushTokenExpired() and scheduling some behavior for whatever it returns.
All that pushTokenExpired() does is fire one of the expiration observables, so I'm reasonably certain that calling it instead of passing it as a reference is a mistake and the intended logic is:
A workaround for the moment could be to just ignore the observables for token expiration. The Observables that fire on successful login are separate from those that manage expiration, so I can just disregard the expiration signals for now, but it would be better if they just behaved correctly.
The text was updated successfully, but these errors were encountered:
Working on trying to integrate the Observable signal sources I've bumped into a bug that's causing my sessions to get closed down right after returning from login.
The problem seems to be in the service handling code that is attempting to use
setTimeout( )
in order to schedule a callback topushTokenExpired( )
at the calculated expiration time. The calculated time seems to be correct, but instead of passing a reference topushTokenExpired
for future callback, the code is calling pushTokenExpired() and scheduling some behavior for whatever it returns.All that
pushTokenExpired()
does is fire one of the expiration observables, so I'm reasonably certain that calling it instead of passing it as a reference is a mistake and the intended logic is:A workaround for the moment could be to just ignore the observables for token expiration. The Observables that fire on successful login are separate from those that manage expiration, so I can just disregard the expiration signals for now, but it would be better if they just behaved correctly.
The text was updated successfully, but these errors were encountered: