AI & TechnologyGoogle Sign-In for Android Is Deprecated: Moving to Credential Manager

Google Sign-In for Android is deprecated, and Sign in with Google now runs through Credential Manager. If your app still uses GoogleSignInClient and GoogleSignInOptions from play-services-auth, or One Tap, move it to Credential Manager before Google removes the old code from the SDK. In a Flutter app the move is an upgrade to google_sign_in 7, which is a breaking release. Much of the work is in the code, and some of the bugs afterwards are in the setup.

If you landed here from an old link to Google's Android sign-in guide, that address now redirects to the Credential Manager overview. The dates and behavior below come from Android Developers, the Android Developers Blog and the Flutter plugin pages, as listed in the sources. I checked each page on October 18, 2026.

Disclosure: App369 is my studio. I build and fix Flutter and Firebase apps, and the last section mentions what I sell. Google doesn't pay me for anything on this page.

What changed, and when

The two sources don't give the same date. The 2024 post gave half-year targets; the migration page, last updated March 6, 2026, gives none. What both say is the same: the old APIs are on their way out, and new work belongs on Credential Manager.

What the old addresses do today

Checked on October 18, 2026:

• developers.google.com/identity/sign-in/android/start-integrating, the old setup guide, redirects to the Android Credential Manager overview.
• developers.google.com/identity/sign-in/android/sign-in redirects there too.
• developers.google.com/identity/sign-in/android/legacy-gsi-migration returned 404. The live migration page is on developer.android.com, linked in the sources.
• developers.google.com/identity/one-tap/android/overview redirects to a page that says One Tap for Android is deprecated.

Moving a native Android app to Credential Manager

The steps follow Google's Sign in with Google implementation guide:

1. Add the dependencies. Add androidx.credentials:credentials, androidx.credentials:credentials-play-services-auth and com.google.android.libraries.identity.googleid:googleid. Check the androidx.credentials release page for the current stable version: on October 18, 2026 the newest stable release listed was 1.6.0, while Google's sample used a 1.7.0 alpha.
2. Use your web client ID. Google's guide passes the Web client ID you set up for OAuth in your Google Cloud project as the server client ID, even in an Android app. The project also has to know your Android app: the Flutter plugin's docs list a wrong package name or a missing signing SHA as common causes of failed sign-in.
3. Build the request. For the bottom-sheet flow, use GetGoogleIdOption with your web client ID. Google's guide first sets setFilterByAuthorizedAccounts(true) to offer accounts that already signed in, with setAutoSelectEnabled(true) for returning users. For a "Sign in with Google" button, use GetSignInWithGoogleOption.
4. Call Credential Manager. Create it with CredentialManager.create(context) and call getCredential with the request. When the result is a GoogleIdTokenCredential, read it with GoogleIdTokenCredential.createFrom(credential.data).
5. Verify the ID token on your server. Send the ID token to your backend and verify it there. If you use Firebase Authentication, use the Google ID token with Firebase Auth.
6. Move scopes to AuthorizationClient. Google says sign-in and authorization are separate actions now. If your app reads Drive, Calendar or another Google API, request those scopes with the AuthorizationClient API when the user needs that feature, not at sign-in.
7. Replace silent sign-in. Google's migration page says to use a request with filterByAuthorizedAccounts set to true and auto-select on, in place of silentSignIn.
8. Remove the old code. Once the new path works, remove GoogleSignInClient, GoogleSignInOptions and any One Tap code, so an old error can't be mistaken for a new one.

Moving a Flutter app to google_sign_in 7

On Android, google_sign_in_android 7.0.0 switched to Credential Manager. Its changelog says it removed the deprecated Google Sign In for Android SDK. google_sign_in 7.0.0 is a breaking release, and its changelog lists the main changes:

• GoogleSignIn is a singleton. Use GoogleSignIn.instance instead of creating your own GoogleSignIn(...).
• Initialize first. Call and await initialize, passing serverClientId where needed, before any other method.
• Sign-in is authenticate(). Check supportsAuthenticate() first, because not every platform supports it. attemptLightweightAuthentication() covers returning users.
• Authentication and authorization are separate. Access tokens and server auth codes come from separate calls through the account's authorizationClient, with authorizationForScopes to check and authorizeScopes to ask, from a user interaction.

Plan for the upgrade to touch every place your app signs in, reads the current user or asks for scopes. It isn't a version bump you can make in one line.

When sign-in breaks after the move

Need a hand?

If sign-in still fails after the move, or it works on your phone but not for your users, the App Fix Ticket covers it in two fixed-price steps. A $450 Diagnosis gives you the root cause with evidence and a fixed repair quote within 3 business days, credited toward the fix. If you go ahead, the $1,200 Fix takes 5 business days. For a related Android change, see SafetyNet is gone: moving to Play Integrity and App Check, or send me a short description.