How are you guys refreshing the user's access_token for infinite sessions? (Supabase auth)
I 'm not using the Supabase SDK on the frontend , so it seems like I need to call supabase .auth .refreshSession ( ) from an edge function ? Is this how you guys are doing it ? I .e . every time the user goes to the dashboard , call this endpoint to refresh their auth ? Or could store the expiry date in local storage to avoid calling the endpoint as often . thats a good question I 'm looking for a good solution too you could look up on page load , wheter the token is like 30 minutes or less away from expiration (assuming a user will be no longer than 30 minutes on one page , so that it is always "right on time " ) and if true , given that on page load , fire the refresh 👍1I 'm storing the refresh _token as an http cookie , but I 'm having trouble passing it to my edge function . Is there anything special I need to do in my API request to pass the cookie ? In the network tab under "Request Headers " I can see the refresh _token is there along with the access _token , but the cookie shows up as null in my edge function log : console .log ( 'Raw Cookie Header R e c e i v e d : ' , req .headers .get ( 'cookie ' ) ) ; Are you trying to pass both ? If so they might need their own headers or to pass it in the body if that ’s where the edge function is expecting it
.jpeg/public)