This repository was archived by the owner on Jan 23, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Jan 23, 2026. It is now read-only.
callback error url parameters are formatted incorrectly #739
Description
Activity
+1
Did you find a solution?I'm parsing just the description for now. Here is my SvelteKit example. This needs to be fixed internally in GoTrueJS.
import { error, redirect } from '@sveltejs/kit'; import type { PageServerLoad } from './$types'; export const load = (async ({ url, locals: { supabase } }) => { const _error = url.searchParams.get('error_description'); if (_error) { const description = _error || 'Authentication Provider Error'; error(400, description); } const code = url.searchParams.get('code'); const next = url.searchParams.get('next') || '/dashboard'; if (code) { const { error: codeError } = await supabase.auth.exchangeCodeForSession(code); if (!codeError) { redirect(303, next); } error(400, codeError.message); } }) satisfies PageServerLoad;
Bug report
When I login with a Magic Link, or with Oauth, there can sometimes be an error. In the case of Oauth, there could be an error if the client secret is wrong. In the case of a Magic Link, there could be an error if the code has expired or already been used.
The searchParam parameters are not formatted correctly. For example I get this:
Notice there is a hash
#instead of a&or?. If I need to parse these error messages to display them to the user, I would have to use a url hack. It is also differently formatted with login with oauth. It should be formatted correctly in any case so that I can display theerror,error_code, anderror_descriptionrespectively.Describe the bug
See above.
To Reproduce
Login with a magic link that has expired. Make sure the server component (in React, SvelteKit, whatever) does not redirect to another page and look at the URL.
Expected behavior
The url parameters should be correctly formatted in both cases (oAuth and magic link). Then I could display the correct error messages to the user simply by parsing the URL.
System information
Additional context
I would also like this formatted correctly when I pass additional parameters. For example
next:This may result in double
?instead of the correctly formatted?and&for parameters.Thanks,
J