Skip to content
This repository has been archived by the owner on Jul 25, 2021. It is now read-only.

Caches aren't invalidated on disconnect or logout #73

Open
amishshah opened this issue Sep 21, 2020 · 0 comments
Open

Caches aren't invalidated on disconnect or logout #73

amishshah opened this issue Sep 21, 2020 · 0 comments
Labels
bug Something isn't working

Comments

@amishshah
Copy link
Collaborator

amishshah commented Sep 21, 2020

When switching accounts without logging in, some weird caching issue is preventing new data from being loaded. This isn't due to the code itselfm but a configuration error.

When disconnected from the gateway, everything except the current JWT should be invalidated as we are no longer sure that the information is true - this is a technical error.

@amishshah amishshah added the bug Something isn't working label Sep 21, 2020
@amishshah amishshah changed the title Invalidate caches on disconnect Invalidate caches on disconnect or logout Oct 4, 2020
@amishshah amishshah changed the title Invalidate caches on disconnect or logout Caches aren't invalidated on disconnect or logout Oct 19, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant