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
It seems like users are sometimes mysteriously no longer able to use Premium features, even though they have a valid Premium membership, and the app thinks they are logged-in.
One thing that could possibly help is, when a logged-in user receives a 401 response, then we can assume that user no longer has a valid logged-in session, so we can render a "You have been logged out of Podverse. If you would like to resume using Podverse Premium, please log back in..." message, and then remove the auth token from local storage, so the app doesn't get confused by thinking the user still has a valid auth token.
The text was updated successfully, but these errors were encountered:
It seems like users are sometimes mysteriously no longer able to use Premium features, even though they have a valid Premium membership, and the app thinks they are logged-in.
One thing that could possibly help is, when a logged-in user receives a 401 response, then we can assume that user no longer has a valid logged-in session, so we can render a "You have been logged out of Podverse. If you would like to resume using Podverse Premium, please log back in..." message, and then remove the auth token from local storage, so the app doesn't get confused by thinking the user still has a valid auth token.
The text was updated successfully, but these errors were encountered: