-
Notifications
You must be signed in to change notification settings - Fork 436
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
forceRefreshSession prematurely completes its observable #767
Comments
@PartyArk We have a bug here, which we fix now for the next version. Thanks for reporting Greetings Damien |
Hi thanks for taking a look at this; I jumped the gun a bit earlier, but now have had a look at your fix. I tried it out but there are a couple of issues I found
Here's what I did -
Hope that helps, I'd do a pull but can't from here. |
fixed in version 11.1.3, thanks for reporting |
I'm having difficultly subscribing to forceRefreshSession with consistent results - here's what I think is happening -
forceRefreshSession
observesrefreshSessionWithIFrameCompleted$
refreshSessionWithIFrameCompleted$
is internally the Subject forsilentRenewEventHandler
silentRenewEventHandler
is triggered - it fires a status back torefreshSessionWithIFrameCompleted$
viafireRefreshWithIframeCompleted
(all this works as expected)fireRefreshWithIframeCompleted
correctly updates the internalrefreshSessionWithIFrameCompleted$
Subject, it then sets the Subject to completeforceRefreshSession
, even though it works (ie refreshes the session), you don't get anything back to observe, because, even thoughfireRefreshWithIframeCompleted
tries to set the Subject value, it's already complete and so doesn't do anything.It's a bit obscure - I picked it up because I'm doing a session refresh immediately when a browser tab comes back into focus. Thanks.
The text was updated successfully, but these errors were encountered: