Closed AJamesPhillips closed 3 years ago
In supabase_update_knowledge_view
, the result
object from await args.supabase.rpc("update_knowledge_view", ...
is:
{
body: null,
count: null,
data: null,
error: {message: 'JWT expired'},
status: 401,
statusText: ""
}
Implemented with check_and_handle_connection_and_session
Describe the bug
You can use the application, go away, come back, start to use the application and then realise it is not working as your sessions has expired.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
On every action, update the time the application was last used. On returning / refocussing a tab, check this datetime and if longer than 5 (?) minutes, go and check (from the UserInfo component?) with supabase (how?) that the session is still working. If not then reload the page / set the user to
undefined
.