Update supabase-js dev to match new auth system #55
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello RA team,
Supabase update their authSystem last week resulting in throwing a 403 error instead of a 401+logout as before.
It makes that when we connect, sometimes we get stuck in a limbo between trying to connect and accessing React-Admin.
I addressed that issue to Supabase team and this is their answer:
**This error is returned when we detect that the session_id claim in the access token doesn't exist in the auth.sessions table. It was introduced in this PR (supabase/auth#1538) because we realised that we were returning the wrong error when the session is missing. Before this PR was merged, the sign out API would return a panic and fail silently, returning a 5xx error to the client which can't be handled.
You can fix this by doing either one of these options:**
This push updates the devDependencies version of both supabase-js and @raphiniert/ra-data-postgrest in supabase-core package.sjon
Kind regards,