Supabase refresh access token
Hey Jose . Would this not be down to RLS (Row Level Security ) ? You can enable Supabase RLS for different roles , so you could have some data be available for a non -authenticated user vs an authenticated user . See https://supabase.com/docs/guides/database/postgres/row-level-security I 'm a bit rusty on auth with Supabase , but assuming you 're making an API call on your pages to get certain table data , it will return data based on those RLS policies . If you 're not authenticated but RLS policies allow read of table data for anon , this data would be fetched . If authenticated , you should then get additional data based on your authenticated user . Video examples of your issue would be helpful for context so the community can help you as best they can . We are using the Supabase Connect package . supa -refresh -session -handler refreshes expired access tokens correctly . However , on public pages we have APIs that use Authorization : Bearer { {cookies .access _token } } . Those APIs frequently execute before the refresh completes , so they run anonymously and return different data . What is the recommended way to delay authenticated API requests until the refresh handler has finished ? Is there an event , promise , context value , or recommended pattern for waiting on session initialization ?
.jpeg/public)