Error to Logout - Inconsistent 403 Forbidden about supabase-js HOT 6 CLOSED

A quick update, supabase support got back to me the following message:

You can fix this by:
- Manually ignore 403s returned and just clear the local session stored on the browser.
- Upgrade to supabase-js v2.43.1 which contains the changes to ignore the 403s returned.

I try to repeat the error, but it happens intermittently, in the end I ended up updating to the latest version ^2.43.4 ⚡️

"clear the local session" I don't know how I would do this since the supabase session is stored in cookies secure and http , which cannot be modified or deleted due to the browser's security policies...

from supabase-js.

Hey! Just got absolutely the same error. Have deployed to Vercel and now catch the bug (on both production and localhost).

Well, it seems like I have successfully logged out on the backend of Supabase, but the session hasn't been removed on the frontend.

const user = useSupabaseUser();
const supabase = useSupabaseClient();

if (user.value) {
  console.log(user.value) // logs a User
  const { error } = await supabase.auth.signOut();
  console.log('error', error); // AuthApiError: Session from session_id claim in JWT does not exist
}

System information

• Nuxt 3 + official Supabase module ("@nuxtjs/supabase": "^1.2.2")
• Node.js 20
• Browser: Chrome Desktop
• OS: MacOS

from supabase-js.

Same issue to me on https://avatarify-ai.com/
Any solution or workaround?

from supabase-js.

I'm getting the same exact error message using supabase-swift, so the issue doesn't appear to be isolated to this library.

from supabase-js.

I'm experiencing a similar issue with edge function authorization.

from supabase-js.

I solved upgrading the dependencies

from supabase-js.