© 2026 Hedgehog Software, LLC

TwitterGitHubDiscord
More
CommunitiesDocsAboutTermsPrivacy
Search
Star
Setup for Free
SupabaseS
Supabase•3mo ago•
3 replies
Jerry Lin

Missing destination name scopes in *models.Session

auth
It looks like this issue is Supabase server-side bug. I found a related discussion here:
https://github.com/orgs/supabase/discussions/40036

However, it seems the bug still hasn’t been fixed. One of the suggested solutions was to upgrade GoTrue to version 2.18, but my Supabase instance is already running GoTrue v2.182.1.

Raw response:
{"version":"v2.182.1","name":"GoTrue","description":"GoTrue is a user registration and authentication API"}

This problem started after I upgraded PostgreSQL to 17.6.1.054, following Supabase’s recommendation to address a security issue.
message.txt7.23KB
GitHub
Bug Report: missing destination name oauth_client_id in *models.Ses...
Description After a successful Google OAuth sign-in, the session is created correctly, but when Supabase attempts to refresh the session (/token endpoint with grant_type=refresh_token), the server ...
Supabase banner
SupabaseJoin
Supabase gives you the tools, documentation, and community that makes managing databases, authentication, and backend infrastructure a lot less overwhelming.
45,816Members
Resources

Similar Threads

Was this page helpful?
Recent Announcements

Similar Threads

Supabase Auth refresh failing with 500: missing destination name scopes in *models.Session
SupabaseSSupabase / help-and-questions
3mo ago
Error: "missing destination name scopes in models.Session"after the PostgreSQL upgrade to 17.6
SupabaseSSupabase / help-and-questions
3mo ago
ERROR [AuthApiError: missing destination name refresh_token_hmac_key in *models.Session]
SupabaseSSupabase / help-and-questions
2mo ago
Auth session missing
SupabaseSSupabase / help-and-questions
11mo ago