Google Sign-In Works in Debug but Fails in Production on Android? Check This Hidden SHA-1
Google Sign-In worked on my development build. It worked on my preview build. On the version Google Play delivered to real testers, tapping "Sign in with Google" did absolutely nothing — no account picker, no error message, no crash. Just a button that did nothing. It took me several days to find. The answer turned out to be a fingerprint that Play Console doesn't show you anymore. If you're here…
My Google Sign-In function worked flawlessly during development, but encountered an issue when deployed to production on Android. The button to sign in with Google remained dormant, displaying no account selection, error messages, or crashes, despite my numerous attempts to troubleshoot. Upon conducting extensive research, I discovered the resolution relied on a hidden SHA-1 fingerprint.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
