Why Google Play Games Login Works in APK but Fails in Play Store (Canceled Status)



 

Why Google Play Games Login Works in APK but Fails in Play Store (Canceled Status)

If you’re using Google Play Games Services in Unity, you might hit a frustrating issue:

  • APK build → login works

  • Play Store build (AAB) → login fails with:

    AUTH STATUS: Canceled
    

No popup. No error. Just silent failure.


Root Cause

This is not a code issue. It’s a signing identity mismatch.

When you install your app:

EnvironmentSigning Key Used
APK (local)Your upload keystore
Play StoreGoogle Play App Signing key

Google Play Games authentication validates:

package name + SHA-1 certificate

If the SHA-1 doesn’t match → authentication is rejected silently → Canceled.


The Mistake

Most developers register the SHA-1 from their keystore:

Upload key SHA ❌

But Play Store builds use:

App signing key SHA ✅

The Fix

1. Get the correct SHA-1

Go to:

Play Console → App → Test and release
→ App Integrity → App signing key certificate → (Copy) SHA-1

2. Update OAuth client

Go to:


Google Cloud Console → APIs & Services → Credentials

https://console.cloud.google.com/apis/credentials

Edit your Android OAuth Client and replace the SHA-1 with the App Signing SHA.


3. Reinstall

  • Wait a few minutes

  • Uninstall app

  • Install again from Play Store


Result

AUTH STATUS: Success
IsAuthenticated: true

Debug Rule (Remember This)

If APK works but Play Store build returns Canceled, your SHA-1 is wrong.


Common Distractions (Ignore These)

You do NOT need to debug:

  • Play Integrity API

  • Unity Authentication

  • Cloud Save

  • Proguard / R8

  • Play Games configuration


Final Takeaway

APK success only proves your upload key is correct.

Play Store uses a different signing key, and that’s the one Google Play Games validates.


Always register the App Signing SHA — not just your keystore SHA.

Comments

Popular posts from this blog

The difference between unity 2D Core VS unity 2D URP template