Games using the Play Games Services (PGS) v1 SDK for sign-in, achievements, leaderboards, saved games or events have a deadline: Google's schedule blocks all v1 traffic in May 2027. v1 also relies on legacy Google Sign-In, which Google has already removed from the play-services-auth and play-services-base libraries. Here is the timeline, who is affected and the move to PGS v2 as Google documents it for Android and Unity.
v1 signs players in through Google Sign-In (GSI) in play-services-auth; v2 needs no play-services-auth.
| When | What happens |
|---|---|
| May 2025 | New apps using PGS v1 can no longer be published (Google's blog post). |
| September 2025 | v1 deprecated in play-services-games 24.0.0 and Unity plugin 0.10.15; existing v1 titles keep working. |
| June 2026 | play-services-games 25.0.0: an empty, non-functional library without the v1 APIs. |
| August and September 2026 | GSI removed from play-services-auth 22.0.0 (August 26) and play-services-base 18.11.0 (September 17). Google says the Google Sign-In for Android API has been unsupported since September 2026. |
| May 2027 | Shutdown: all v1 traffic blocked, v1 APIs stop working in production. |
| June 2027 | v1 SDK removed; calls fail even from builds on older SDK versions. |
Google's pages disagree. Its June 2025 blog post and September 2025 release notes put the end of v1 calls in 2028 (Q3 2028 in the blog, July 2028 at the earliest in the notes); the blog also said v1 games couldn't be updated after May 2026, which the schedule doesn't repeat. The blog dates the block on new v1 apps to May 2025, while the schedule mentions it only in its note on the period after September 2025. The schedule dates the GSI removal from play-services-auth to May 2026 and 25.0.0 to June 15, 2026; the release notes say August 26 and June 11. Plan for the earliest dates.
com.google.android.gms:play-services-games (not -v2) for sign-in, achievements, leaderboards, saved games, events or player stats, typically with GoogleSignInClient and calls like Games.getLeaderboardsClient(activity, account).play-services-auth 22.0.0 or later: Google warns of compile errors and says to roll that SDK back. play-services-base 18.11.0 also dropped its GSI surfaces.play-services-games:+, which now resolves to 25.0.0.# Games, auth and base artifacts in the release build (use your module name)
./gradlew :app:dependencies --configuration releaseRuntimeClasspath | grep -E "play-services-(games|auth|base)"
# v1-era code and config, Unity C# scripts included
grep -rnE "play-services-games:|GoogleSignIn|DEFAULT_GAMES_SIGN_IN|(^|[^A-Za-z])Games\.get[A-Za-z]*Client|GoogleApiClient|PlayGamesClientConfiguration" \
--include='*.gradle' --include='*.kts' --include='*.xml' --include='*.java' --include='*.kt' --include='*.cs' .
A hit on PlayGamesClientConfiguration means a v1 Unity plugin; the current plugin has no such class.
com.google.android.gms:play-services-games-v2:22.1.0, the newest release (September 15, 2026). Google says v1 builds may go up to 24.0.0, never 25.0.0.com.google.android.gms.games.APP_ID manifest meta-data and call PlayGamesSdk.initialize(this) in Application.onCreate().GoogleSignInClient with GamesSignInClient: v2 tries to sign the player in at launch, isAuthenticated() returns the result and signIn() backs a sign-in button if that fails. Delete sign-out code; players switch profiles in device settings.PlayGames instead of Games, without an account. GamesClient and GamesMetadataClient have no replacement; GoogleApiClient code moves to clients such as AchievementsClient.requestServerSideAccess() replaces getServerAuthCode().// Application.onCreate()
PlayGamesSdk.initialize(this)
// Game activity: read the result of the automatic sign-in
val signInClient = PlayGames.getGamesSignInClient(this)
signInClient.isAuthenticated().addOnCompleteListener { task ->
if (task.isSuccessful && task.result.isAuthenticated) {
val leaderboards = PlayGames.getLeaderboardsClient(this)
// likewise getAchievementsClient, getEventsClient, getSnapshotsClient
} else {
// hide PGS features, or show a button that calls signInClient.signIn()
}
}
Google's v2 docs say the Player ID is for platform features such as achievements, leaderboards and events, and PGS must not be your primary identity system for accounts, progress or inventory. Bind in-game accounts to a primary ID that doesn't come from PGS: Google recommends the OpenID from Sign in with Google (Credential Manager), and your own backend or another provider also works. Keep the Player ID as a secondary link for restoring the last account on a new device or after a reinstall.
games_lite scope for the chosen account through the Authorization API. A token returned without UI means an earlier v1 grant: use it to get the Player ID and, if an in-game account is linked to that Player ID, link that account to the player's OpenID. A returned PendingIntent means no v1 account: discard it unseen. Google's guides include a CredManBridge.java sample.GoogleSignInClient login to Credential Manager.requestServerSideAccess with that server's client ID, not the Android one; your server exchanges the one-time code. Refresh tokens need forceRefreshToken set to true and a player with auto sign-in enabled.DRIVE_APPFOLDER and GAMES_LITE. Since play-services-games-v2 21.0.0 and Unity plugin 2.1.0 you can add EMAIL, PROFILE and OPEN_ID; if the player declines, you still get a code. Google recommends this call when you need extra OAuth scopes; it offers only those three.Players.get and me.// One-time code for your server, which exchanges it for tokens
signInClient.requestServerSideAccess(GAME_SERVER_CLIENT_ID, /* forceRefreshToken= */ false)
.addOnCompleteListener { task -> if (task.isSuccessful) sendToServer(task.result) }
Google says plugin versions 10 and earlier use v1. The current 2.3.0 (September 29, 2026) uses play-services-games-v2 22.1.0; 2.2.0 raised minSdkVersion to 24, and 2.2.1 fixed build errors in Unity 2021 and 2022 caused by Java version requirements.
Assets/GooglePlayGames, Assets/GeneratedLocalRepo/GooglePlayGames, Assets/Plugins/Android/GooglePlayGamesManifest.androidlib and Assets/Plugins/Android, and the upgrade notes add the old play-services-games .aar. Check Assets/Plugins/Android for other plugins and Gradle templates before deleting it.current-build folder, switch to Android, and paste the Android (XML) resources from Play Console into Android Setup (Window, Google Play Games, Setup), plus the web client ID for server-side access.PlayGamesClientConfiguration and InitializeInstance with Authenticate, and delete SignOut; the current plugin has none of the three. Activate() is only needed for Unity's Social API.using GooglePlayGames;
using GooglePlayGames.BasicApi;
void Start() {
PlayGamesPlatform.Instance.Authenticate(OnAuthenticated);
}
void OnAuthenticated(SignInStatus status) {
if (status == SignInStatus.Success) {
// PGS is available; one-time code for your server, if you have one
PlayGamesPlatform.Instance.RequestServerSideAccess(false, code => SendToServer(code));
} else {
// hide PGS features, or show a button that calls
// PlayGamesPlatform.Instance.ManuallyAuthenticate(OnAuthenticated)
}
}
No PGS call works until Authenticate succeeds, so Google recommends a standby screen until its callback is called. For extra scopes, RequestServerSideAccess also takes a list of AuthScope values.
drive.appdata): up to 3 MB per save and 800 KB per cover image.PlayGames.getSnapshotsClient(activity), then open, writeBytes and commitAndClose. Unity: PlayGamesPlatform.Instance.SavedGame, open with automatic or manual conflict resolution, then CommitUpdate; v1's EnableSavedGames() is gone.play-services-games at 24.0.0 or lower (never +) and hold back SDK updates that bring play-services-auth 22.0.0 or play-services-base 18.11.0 (or any later version).play-services-games-v2 22.0.0 (per the library's own manifest) and play-services-base 18.11.0 raised the minimum to minSdkVersion 24, and their current versions keep it.adb logcat | grep com.google.android. should show returning true for shouldShowWelcomePopup.