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
Describe the bug
It appears that when a user's JWT expires locally, the token is neither refreshed if they are still actively logged in or logged out due to inactivity.
To Reproduce
Steps to reproduce the behavior:
Login or register at root url. Stay logged in for at least 10hrs, attempt to refresh the browser at any page in the application and the error should appear.
Expected behavior
User should be redirected to main login page or token should be refreshed if user has not actively logged out.
Screenshots
Additional context
It appears that part of the issue stems from the conditional that is presented inside the ComponentDidMount() portion of the App.js file:
Because a user is technically 'logged_in' when the token expires it returns the error because there is no user information to attempt to setState for. Not sure if the issue lies more on the frontend or backend or both.
The text was updated successfully, but these errors were encountered:
Describe the bug
It appears that when a user's JWT expires locally, the token is neither refreshed if they are still actively logged in or logged out due to inactivity.
To Reproduce
Steps to reproduce the behavior:
Login or register at root url. Stay logged in for at least 10hrs, attempt to refresh the browser at any page in the application and the error should appear.
Expected behavior
User should be redirected to main login page or token should be refreshed if user has not actively logged out.
Screenshots
Additional context
It appears that part of the issue stems from the conditional that is presented inside the ComponentDidMount() portion of the App.js file:
Because a user is technically 'logged_in' when the token expires it returns the error because there is no user information to attempt to setState for. Not sure if the issue lies more on the frontend or backend or both.
The text was updated successfully, but these errors were encountered: