Google Sign in is not working after publishing app on google play console problem solved

If Google Sign-In works in debug but stops working after publishing on Google Play, the issue is usually misconfigured SHA-1 / OAuth settings.
Here’s the confirmed solution checklist that fixes it in most cases:

Solution: Fix Google Sign-In after Play Store release

1. Add Release SHA-1 to Firebase / Google Cloud

After publishing, Google uses the release signing key, not your debug key.

• Go to Google Play Console
• Open App → Setup → App integrity
• Copy the SHA-1 certificate fingerprint under App signing key
• Go to Firebase Console
  • Project Settings → General → Your Android App
  • Add the release SHA-1
• Download the updated google-services.json
• Replace the old file in your project

2. Enable correct OAuth client

In Google Cloud Console → APIs & Services → Credentials:

• Ensure an OAuth 2.0 Client ID (Android) exists
• Package name must match exactly
• SHA-1 must match the Play Console SHA-1

3. Update app and re-publish

• Clean & rebuild the project
• Upload a new release to Play Console
• Wait a few minutes (OAuth changes may take time to propagate)

4. Verify Google Sign-In API is enabled

In Google Cloud Console:

• Enable Google Sign-In API
• Enable People API (recommended)

5. Test with Play Store version (not local APK)

• Install the app directly from Play Store
• Google Sign-In will fail if tested with a locally signed APK

Most common cause

Missing Play Console SHA-1 in Firebase / Google Cloud