You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Diagnosis so far (staging Supabase auth logs): the browser click never
issues the /auth/v1/authorize request — GoTrue itself is correctly
configured (a direct probe 302s to the bitcode.exchange
/tps/wallet/authorize page). The stall is client-side between building
the authorize URL and the navigation leaving the page.
The panel now logs the exact authorize URL ([Bitcode QA]
'oauth-redirect' / 'oauth-redirect-stalled' events) and, when the
redirect watchdog fires, renders an 'Open Bitcoin authentication
manually' link carrying that URL inside the error alert — a
user-gesture navigation that both works around and pinpoints whatever
is cancelling the programmatic assign.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
'The Supabase Bitcoin authentication page did not open. Check redirect blocking and that the Supabase this environment points at has the custom:bitcode-bitcoin provider configured, then retry.',
419
+
'The Supabase Bitcoin authentication redirect has not completed — the request never left this page. Continue manually below, and check the [Bitcode QA] console trace (?bitcode_verbose=true) for the exact redirect target.',
0 commit comments