AuthApiError: Session from session_id claim in JWT does not exist about supabase

[JOsacky]

I am also running into this issue and users are not able to logout using the iOS client and instead throws an error because the response is a 403.

Force log outs only happen for 404s and 401s on the iOS client, perhaps updating the response to a 401 would make more sense

Here is the a reference to the swift supabase client code that throws
https://github.com/supabase/supabase-swift/blob/f1e17ee7ceef4e9da56c57fdd299fa1cf1641381/Sources/Auth/AuthClient.swift#L714-L723

Here is a photo of the error in the xcode debugger:

Edit: there has already been a PR to address this by force logging out from 403s.

supabase/supabase-swift@7c4e62b

[otang]

I am experiencing the same issue

[erasmusa]

Hi there everyone,

I am currently having the same issue. I am developing a react-admin web application for internal usage. I use the 'ra-supabase' npm package. I host the app on Firebase but use the Supabase backend. I'm experiencing this error during the implementation of my "forgot password" workflow. The first step where I get the email with the link back to my app works 100%.

This link contains the needed parameters i.e. access_token (JWT) and the refresh_token. I pass these to the function provided by the useSetPassword hook. Behind the scenes it calls the setPassword method in the authProvider which in turn calls setSession which checks if the token had expired and if not tries to fetch the user by calling _getUser giving it the access_token.

It is this _getUser (/v1/user) call that eventually throws a 403 error and returning "AuthApiError: Session from session_id claim in JWT does not exist".

To me it looks like an issue on the Supabase API side. Any ideas?