Repository navigation
[google_sign_in] Switch Android to Credential Manager #154205
Description
Use case
Proposal
there's already a community package but having an official one would be better, since it's such core concern
Metadata
Metadata
Assignees
Labels
High-priority issues at the top of the work listNothing broken; request for a new capabilityA detailed proposal for a change to FlutterFor the attention of Android platform teamThe Google Sign-In pluginflutter/packages repository. See also p: labels.Android applications specificallyIssue is closed as already fixed in a newer versionOwned by Ecosystem teamTriaged by Ecosystem team
Activity
Sliman-Baghouri commentedon Sep 8, 2024
Yes now the only way to do it is via custom method channels or using 3rd party community plugin, it would be nice to have an official source
stuartmorgan-g commentedon Sep 13, 2024
Based on this blog post Google Sign-In for Android will be removed in H2 2025 specifically.
google_sign_inplugin (although we may publish a direct wrapper separately as well). This is likely to be paired with significant changes to thegoogle_sign_inAPIs, since every platform now has a different recommended underlying, so the current API may not be a good match (see [google_sign_in] Reworkgoogle_sign_into reflect changes in underlying SDKs #119300)[-]officially support android jetpack credential manager[/-][+][google_sign_in] Switch Android to Credential Manager[/+]5 remaining items
stuartmorgan-g commentedon Jan 17, 2025
This is still planned for Q1.
stuartmorgan-g commentedon Mar 24, 2025
#119300 (comment) has a link to the design document that will be part of this transition. Unfortunately, after investigation, it is not possible to use
CredentialManagerto build a fully compatible replacement for the deprecated SDK, so just replacing the backend of the current API as a short-term transition isn't viable. (A semi-compatible shim is possible, but not one that could be released as a non-breaking change.)As a note on adoption timelines, while Google Sign-In for Android will be removed from new versions of the
com.google.android.gms:play-services-authlater this year, as noted in the link in the issue description, the service itself will continue to work past that point. This means that existing versions of thegoogle_sign_inplugin will continue to work past the SDK removal point, so long as applications using it don't have other dependencies on new versions ofcom.google.android.gms:play-services-auth, so the SDK-level removal should not be a hard deadline on most clients adopting the new version ofgoogle_sign_inwith its breaking changes.The expectation is still that we will have the new version of
google_sign_inavailable in advance of the removal from the SDK, however, so that adoption can begin before even edge cases could see compilation issues.fan123199 commentedon Apr 29, 2025
Is there any further status update? Q1 ended nearly a month ago. While the existing sign-in works, the new credential manager significantly shortens the sign-in flow on Android. I really don't want the sign-in experience in Flutter is worse than native Android.
stuartmorgan-g commentedon May 2, 2025
If anyone wants to try an in-progress version of the new implementation based on CredentialManager, please see this comment
ycv005 commentedon May 17, 2025
[google_sign_in] Redesign API for current identity SDKs (flutter#9267)
[google_sign_in] Redesign API for current identity SDKs (flutter#9267)
github-actions commentedon Jul 9, 2025
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.[google_sign_in] Redesign API for current identity SDKs (flutter#9267)
[google_sign_in] Redesign API for current identity SDKs (flutter#9267)
[google_sign_in] Redesign API for current identity SDKs (flutter#9267)