Bhagavad Gita — Auth Rescue
Diagnosed and fixed a production-only Google Sign-In failure that had locked out 50,000+ users — tracing it to OAuth and Firebase misconfiguration, then restoring login on the live app.
Google Sign-In worked perfectly in development — and failed silently in production, locking out 50,000+ users.
A live Bhagavad Gita app with over 50,000 users had its Google Sign-In break in production mode only — working fine in development, failing for real users. Tens of thousands could no longer log in.
Debugging an auth failure that only reproduces in a live environment is the hard kind: no easy local repro, real users affected, and a root cause buried in OAuth, API, and token configuration rather than the app code itself.
Investigate the production-only failure
Dug through logs and debugging tools to analyse the sign-in failure, then worked through the suspects — OAuth settings, API restrictions, and token handling — to narrow down why production behaved differently from development.
Find the misconfiguration
Traced the root cause to misconfigurations in the Google Cloud Console and Firebase Authentication settings — the real reason, not a surface-level patch on the app code.
Fix, test & restore
Applied the correct OAuth credentials and adjusted API permissions for production, then tested thoroughly across both development and production until sign-in was stable — restoring access for 50,000+ users.