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
Currently when a user loses connection to our app (closing their laptop lid, losing internet connection, etc), a user could resume their connection but try to make API calls with expired tokens. Instead of being taken to a 500 page, they should be redirected to the home page as a MVP solution.
Since it looks like users are getting redirected to the /500 url itself, and not just the url staying the same but showing the 500 page, seems like it's probably related to the useError500 function. It's used 3 or so times in the app.
I'll message you with the recording with me showing this behavior.
Let me know if you want any help re-creating the issue, I wrote up how to adjust the keycloak timeout over here in this PR.
Just redirecting these users to the unauthenticated home page seems like a good place to start.
The text was updated successfully, but these errors were encountered:
Currently when a user loses connection to our app (closing their laptop lid, losing internet connection, etc), a user could resume their connection but try to make API calls with expired tokens. Instead of being taken to a 500 page, they should be redirected to the home page as a MVP solution.
/500
url itself, and not just the url staying the same but showing the 500 page, seems like it's probably related to the useError500 function. It's used 3 or so times in the app.The text was updated successfully, but these errors were encountered: