The credential succeeds while the browser return loses the session.
Passkey adoption depends on a clean callback flow, while existing OAuth redirects must remain unchanged.
Who you’d be doing this for
“The passkey prompt says it worked, then I’m right back on the sign-in page.”
Naing Hashim · Application Developer
Maintains a Next.js product that is trialing passkey sign-in through supabase-js.
What is at stake
Verified passkey users return without a session, even though password sign-in still works. You must improve the return flow without destabilizing existing OAuth callbacks.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- passkey completion vs callback integrity
- browser recovery vs redirect safety
- client diagnostics vs server simplicity
- rapid patch vs regression coverage
Why Supabase
Supabase Auth passkeys depend on supabase-js and Next.js behavior that application developers carry directly into their sign-in flows.
Written with these in mind
Not your kind of problem? 23 more at Supabase, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.