BestPaid guides · Android · Google Play Games Services

Play Games Services v1 shuts down in May 2027: moving Android and Unity games to PGS v2

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.

Sources: Google's PGS v1 deprecation schedule (updated October 6, 2026), migration overview, Android and Unity migration guides, Platform authentication (updated November 18, 2026), Android sign-in, server-side access, Cloud save, Android and Unity saved games, Unity setup and Play Console setup guides; the GamesSignInClient reference, the Google Play services release notes (updated November 9, 2026) and the legacy Google Sign-In page; the play-services-games-v2 packages on Google's Maven repository; Google's June 30, 2025 blog post; the Unity plugin's GitHub releases, upgrade notes and source; Play Console Help on target API level requirements. Checked on November 21, 2026. This page is our own summary; follow the vendor's documentation for every detail.

What changes and when

v1 signs players in through Google Sign-In (GSI) in play-services-auth; v2 needs no play-services-auth.

WhenWhat happens
May 2025New apps using PGS v1 can no longer be published (Google's blog post).
September 2025v1 deprecated in play-services-games 24.0.0 and Unity plugin 0.10.15; existing v1 titles keep working.
June 2026play-services-games 25.0.0: an empty, non-functional library without the v1 APIs.
August and September 2026GSI 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 2027Shutdown: all v1 traffic blocked, v1 APIs stop working in production.
June 2027v1 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.

Who is affected

Check a project

# 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.

Android: games v1 to v2

  1. Swap the dependency for 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.
  2. Keep or add the com.google.android.gms.games.APP_ID manifest meta-data and call PlayGamesSdk.initialize(this) in Application.onCreate().
  3. Replace 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.
  4. Get clients from PlayGames instead of Games, without an account. GamesClient and GamesMetadataClient have no replacement; GoogleApiClient code moves to clients such as AchievementsClient.
  5. 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()
    }
}

Player accounts: bind them to Google OpenID

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.

Server-side access

// 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) }

Unity: plugin 2.3.0

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.

  1. Remove the old plugin: Google lists 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.
  2. Import the package from the repository's 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.
  3. Replace 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.

Saved games

Order of work

  1. Inventory: the checks above, the plugin version, how accounts are keyed and what your server does with auth codes.
  2. Protect today's build: pin 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).
  3. Play Console: the Android credential must match the package name and the Play App Signing SHA-1, or authentication fails. Add the Game server credential and testers as needed.
  4. Migrate the client, then account linking and the server.
  5. Meet today's Play rules in the same release: since August 31, 2026, new apps and app updates must target Android 16 (API level 36) or higher (Wear OS, Android Automotive OS, Android TV and Android XR have lower minimums). Plugin 2.2.0, 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.
  6. Internal testing, the tests below, then a staged rollout, well before May 2027.

What to test

Still on Play Games Services v1 or Unity plugin 0.10.x? We update native, Unity, Flutter, React Native and Xamarin apps to current SDKs and store rules at a fixed price. You keep your signing keys. It starts with a $290 check and a fixed quote within 2 business days.
See the app update offer