CRITICAL: cannot log in (client report via pluto)

Sub-tickets

Questions

Activity

• system created · 2026-05-12
  wi cli
• coder-ayudarg-cc assigned · 2026-05-12
  assigned to coder-ayudarg-cc
• system statusChanged · 2026-05-12
  PM URGENT dispatch
• coder-ayudarg-cc assigned · 2026-05-12
  assigned to coder-ayudarg-cc
• system statusChanged · 2026-05-12
  P0 login break
• rob questionAsked · 2026-05-12
  q#19 to=elazar: Coder finds zero auth errors/POSTs in last hour — no smoking gun. Need: (a) which user account, (b) exact error text (toast/modal/inline?), (c) Google sign-in vs email+password, (d) device (mobile/des
• rob blocked · 2026-05-12
  awaiting elazar
• wi-cli-venus questionAnswered · 2026-06-12
  Resolved via forensics 2026-06-12 (db + code). (a) Belén belengalvan@catedraldelafe.org; (b) error='Error de Autenticación / Ocurrió un error durante la autenticación' = generic fallback on /error-auth; (c) GOOGLE sign-in (only the OAuth callback reaches /error-auth; email+pwd fails inline); (d) likely mobile/WhatsApp in-app browser; (e) failed earlier 2026-06-11, SUCCEEDED 18:29 UTC same day. Root cause: transient exchangeCodeForSession failure (PKCE/cookie), self-resolved on retry. Not an outage.
• wi-cli-venus statusChanged · 2026-06-12
  Root cause = transient Google OAuth callback failure (self-resolved). Reclassify pri0->1 (recommend). Actionable fix: add error logging to auth/callback/route.ts so recurrence is diagnosable.
• wi-cli-venus commented · 2026-06-12
  FIX SPEC (Elazar go 'fix'): in src/app/auth/callback/route.ts, log the swallowed Supabase error from exchangeCodeForSession (line 36) BEFORE redirecting to /error-auth (line 64), and the no-user case (line 42), using the app's backend logger (writes to logs table) incl user email if available. Goal: next OAuth failure records the real error. Small. Can follow CR24/#303.
• wi-cli-venus commented · 2026-06-12
  Narrow OAuth-callback logging fix SUBSUMED by AYUD-1 (urgent: app logger dead since 2026-05-28). Coder folding the callback logging into the broader logger restore. #340 stays open pending that + confirms login works.
• wi-cli-venus commented · 2026-06-12
  Auditor PASS on bac3d86/v7.26.2: callback now calls prismaLog on all 4 failure paths (missing code/exchange error/no-user/no-roles), captures supabase error+email/userId, redirects preserved, deploy READY (dpl_53ew5SYxDQWFnyU92JXd4LpiJk53, SHA matches HEAD), 0 runtime errors. Logging code DONE but inert until AYUD-1 (insertLog) fixed. KEEP #340 OPEN until AYUD-1 lands + logs confirmed capturing.
• wi-cli-venus commented · 2026-06-12
  Auditor live-confirmed end-to-end logging on prod: id 850 backend/error CCBACK (callback path firing) + id 849 frontend/warn CCFRONT. Login failure is now fully diagnosable. Root cause of original incident = PKCE code verifier missing (AuthPKCECodeVerifierMissingError, pkce_code_verifier_not_found, 400) — in-app-browser/cookie. Login works; intermittent. HOLDING close pending Elazar decision on whether to add a PKCE/in-app-browser mitigation.
• wi-cli-venus completed · 2026-06-12
  Login works + now fully diagnosable (callback logging live, v7.26.2, auditor-verified end-to-end). Original incident root cause identified = PKCE verifier missing (in-app browser). Hardening tracked separately in AYUD-2. Logging gap that blinded us = closed.