Google登录DEFAULT_GAMES_SIGN_IN与DEFAULT_SIGN_IN差异及Debug APK测试Play排行榜

Hey there, let's break down your questions clearly—I’ve dealt with these exact Play Games integration headaches before, so this should help:

These two constants are used to configure the Google Sign-In client for distinct use cases:

• DEFAULT_SIGN_IN is the general-purpose authentication setup. It lets users sign in with their Google account and grants access to basic profile data (name, email, profile picture) but doesn’t include any Play Games Services-specific permissions or scopes. It’s designed for apps that only need standard Google account auth, not games-focused features.
• DEFAULT_GAMES_SIGN_IN is purpose-built for Play Games Services. It automatically requests all the necessary scopes to access games-related functionality: leaderboards, achievements, saved game data, and more. If your app uses any Play Games features (like your leaderboard test), this is the configuration you must use—without it, the auth token won’t have the permissions needed to interact with those services.

Let’s unpack why switching to DEFAULT_GAMES_SIGN_IN fixed your vague "bad stuff" error:

• Missing Critical Scopes: When you used DEFAULT_SIGN_IN, your authentication flow didn’t ask for the scopes required to access Play Games leaderboards. Even though you set up the Debug OAuth Client ID and linked the app correctly, the user’s auth token lacked the necessary permissions. Instead of a clear "missing scopes" error, the SDK threw that generic "bad stuff" message (frustrating, I know).
• Double-Check Debug Setup Details: Since you’re using a Debug APK, confirm these key points to avoid future issues:
  • The SHA-1 fingerprint you used for the Debug OAuth Client ID is an exact match from your Android Studio debug keystore. You can fetch it with this command in your terminal:

    keytool -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android -keypass android
    

    (On Windows, replace the keystore path with C:\Users\[YourUsername]\.android\debug.keystore.)
  • In the Play Games Services Console, ensure you’ve linked both your Debug and Release OAuth Client IDs if you plan to test both builds later.
• Pro Tip for Debugging: To avoid vague errors like this in the future, enable verbose logging for Google Sign-In and Play Games Services. Add these meta-data tags to your AndroidManifest.xml:

  <meta-data
      android:name="com.google.android.gms.games.APP_ID"
      android:value="@string/games_app_id" />
  <meta-data
      android:name="com.google.android.gms.version"
      android:value="@integer/google_play_services_version" />
  

  Then check Logcat for tags like GoogleSignIn or Games—they’ll usually spell out the root cause (invalid client ID, unlinked app, missing scopes, etc.) instead of hiding behind generic messages.

内容的提问来源于stack exchange，提问作者gloo