Refresh Tokens Experiencing an Unexpected Failure

Hi all, I am developing an app using Supabase and Nordcraft as my front-end. All was going well until about two weeks ago. My project was frozen as I hadn't worked on it for two weeks (busy with personal matters). When I came back however my authentication token refresh was no longer working. Logging in and all other functionalities work, but when POSTing to https://<project>.supabase.co/auth/v1/token?grant_type=refresh_token, I get:
{
"code": 500,
"error_code": "unexpected_failure",
"msg": "missing destination name oauth_client_id in *models.Session",
"error_id": "9a37b289b0ca2b28-DUR"
}
{
"code": 500,
"error_code": "unexpected_failure",
"msg": "missing destination name oauth_client_id in *models.Session",
"error_id": "9a37b289b0ca2b28-DUR"
}
Looking online this seems to be a known bug, but I'm not really sure how I could have caused it, or what needs to be done to fix it. As far as I can see my Supabase infrastructure is up to date on the dashboard. Attached are screenshots of my service versions, as well as my enabled plugins Any suggestions would be appreciated!
Nordcraft — The Web Development Engine
The Nordcraft Engine lets designers and developers collaborate to create immersive and interactive web experiences. We use Nordcraft to build Nordcraft.
No description
No description
9 Replies
garyaustin
garyaustin4d ago
You should not be using orioleDB unless you are specifically testing/debugging it. Where do you see this as a known bug. Link? The latest version of "normal" postgres is 17.6.1.054. They don't keep the orioledb in sync.
Ethan
EthanOP4d ago
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 ...
Ethan
EthanOP4d ago
I thought this might be an issue, I figured it would pretty stable by the time I released my app
garyaustin
garyaustin4d ago
That error says upgrading to latest resolves it. I don't know how often they upgrade the orioleDB one for you to be able to upgrade on hosted, but know it is out of sync from an auth issue the other day... https://github.com/orioledb/orioledb/issues/653#issuecomment-3564115136
GitHub
"Unsupported keybitmap type" when trying to verify a token hash in ...
Hello. I implemented basic Supabase Authentification with a PKCE flow and got the error when clicking on the verification link sent via email. It seems to happen during the exchange of the token ha...
Ethan
EthanOP4d ago
I see, so is only option to wait until they update then?
garyaustin
garyaustin4d ago
IF that issue you posted was resolved with a new release (I only read it quickly) then makes sense you would need a new release of the OrioleDB version. This was from a Supabase dev awhile back. The intent is not for you do be using this for apps right now... Seems like it may not be part of their release of other features so you will always be subject to these kinds of issues until it is a more mainstream thing.
No description
Ethan
EthanOP4d ago
IF that issue you posted was resolved with a new release (I only read it quickly) then makes sense you would need a new release of the OrioleDB version
From what I read this was the case. Regarding transitioning away from oriole, is it possible to do this with "Recover to new project"?
garyaustin
garyaustin4d ago
Sorry I've only seen a few OrioleDB things here and they were similar to yours with things not working right. If there is no option to change it in that process I would not think so.
Ethan
EthanOP4d ago
I see, this is unfortunate I will mark this as solved, thanks.

Did you find this page helpful?