[google_sign_in_web] Migrate from Google Sign-In JavaScript Platform Library to Google Identity Services

[jmagman]

---

TL;DR:

Note

• Fix released in package: google_sign_in: ^6.0.0.
• Read the migration notes in the google_sign_in_web README.

---

Original issue below:

Internal: b/233812803

Internal: b/259309242

Google Sign-In JavaScript Platform Library used by the google_sign_in web plugin will be discontinued on March 31, 2023.

It is being replaced by Google Identity Services

https://github.com/flutter/plugins/blob/b548ae18646d1725a8e1f004c26bf42e4d362aa8/packages/google_sign_in/google_sign_in_web/lib/google_sign_in_web.dart#L24

See also

• [google_sign_in] web implemented uses deprecated APIs #101004

[jmagman]

\cc @ditman

[Levi-Lesches]

See also #82980

[ditman]

Thanks for reporting! I'll take a look at this ASAP; apologies for the nagging emails, I wasn't aware that this migration was going to happen or that we'd send out emails to eeeevery user of the plugin :)

Speaking of the email, here's the full text we all received (included for SEO purposes on this issue :P)

Google Developers

One or more of your web applications uses the legacy Google Sign-In JavaScript library. Please migrate your project(s) to the new Google Identity Services SDK before March 31, 2023.

Hello Google Developer,

As announced earlier this month, the legacy Google Sign-In web solution will no longer be supported after March 31, 2023. You are receiving this message because one or more of your web applications uses the legacy Google Sign-In web solution.

We’re writing to let you know that migration to the new Google Identity Services - our new family of Identity APIs that consolidate multiple identity offerings under one software development kit (SDK) - will be necessary to sign in users using their Google Account to your platform, after that date. The SDK will use the new Sign In With Google client library.

What do I need to know?

To help you find out which of your web apps or environments are affected, we’re sharing a list of your client ID(s) that use the legacy Google Sign-In web solution. This list should help you evaluate user impact and prioritize the migration work more efficiently:

App Name	client ID
Your App Name	00000000-y0urg00gl3s1gn1n4p1k3y.apps.googleusercontent.com

What do I need to do?

At your earliest convenience, migrate to the new Google Identity Services by following the migration guide.

How can I find more information or share feedback?

Be sure to read through the Sign-In With Google resources guide. If you have migration specific feedback to share, send an email to gis-migration-feedback@google.com.

Sincerely,

The Google Identity Services team

Luckily we have until 2023 to get this done ;P

Since google_sign_in is federated, we can start a new package for web that uses the new SDK. People will be able to test the new plugin while it's being developed, and once the new plugin is ready and tested, we can just change the endorsement to the new one.

I am not sure if we want to use this opportunity to rewrite the core plugin (a completely new platform interface, etc...). Any ideas @jmagman @blasten @stuartmorgan ?

[stuartmorgan-g]

I am not sure if we want to use this opportunity to rewrite the core plugin (a completely new platform interface, etc...). Any ideas @jmagman @blasten @stuartmorgan ?

Is this using the new two-phase flow like the latest iOS SDK? If so, then we should seriously consider a set of breaking changes to all the interfaces across platforms to pick up that model. (We're waiting a bit to see what happens with the feedback that the new iOS SDK has received though in case anything changes as a result.)

[ditman]

I'm going to try and follow-up with somebody in the Google Identity Services team for a little bit more insight into this matter, and to see if they have any preference/suggestion in the future direction of the plugin API.