ADDEDb590rel/engines-tools3 min read

Google opens Unity 6.5 sign-in plugin for Android and iOS

Google's open-source Unity 6.5 plugin brings native Google account sign-in to Android and iOS, retrieves ID tokens for Firebase, Supabase, Auth0 and custom backends.

Google releases open-source Sign in with Google plugin for Unity
Google releases open-source Sign in with Google plugin for UnityPexels / pixabay

Patch notes

  • Google released an open-source Sign in with Google plugin for Unity 6.5 on GitHub.

  • The Android build uses Credential Manager through Kotlin; the iOS build uses GIDSignIn SDK through Objective-C++.

  • Developers configure a Web Client ID and iOS Reversed Client ID inside the Unity Editor.

  • Unity C# scripts can pass signed Google ID tokens to Firebase Authentication, Supabase, Auth0 or custom backends.

  • The plugin retrieves tokens rather than replacing studios' existing player-account systems or providing complete account management.

By Priya Raman

Google has released an open-source Sign in with Google plugin for Unity 6.5, giving mobile-game developers Google account sign-in on Android and iOS through a GitHub-hosted replacement for an older integration.

Google said the new implementation reduces integration work and addresses compatibility problems that affected older versions with modern Android development tools. For studios, this is an authentication-layer upgrade, not a replacement for player accounts or backend services.

What does this change for Unity studios?

The plugin uses the native sign-in route on each mobile platform:

  • Android: The integration connects to Credential Manager, Google's native credential API, through Kotlin.
  • iOS: The integration calls the GIDSignIn SDK, Google's iOS sign-in software development kit, through Objective-C++.
  • Backends: The plugin retrieves a signed Google ID token (a credential carrying the authentication result) that Unity C# scripts can pass to Firebase Authentication, Supabase, Auth0 or a studio's own backend service.

That token bridges Google and the game's existing account infrastructure. Developers can add Google sign-in without replacing their current player-account system, then reuse the returned credential inside whichever backend the studio already operates.

The boundary is operational. The plugin primarily retrieves Google ID tokens rather than supplying complete player account management. The studio's chosen backend still handles the account system, while Unity C# code reads the Google credential and makes it available to that service.

Configuration stays inside the Unity Editor, the engine's in-project development environment. Developers can enter their Web Client ID and iOS Reversed Client ID directly there, without manually changing platform files for the two mobile targets. The two identifiers connect the Unity package to Google's respective Android and iOS integrations.

Google made the plugin's code available on GitHub as part of the open-source release. Engineering teams can inspect the platform bridges and token handoff before adopting the package, rather than treating the native sign-in flow as a black box. That visibility also gives studios a clearer basis for maintaining the integration as their project changes.

Unity 6.5 is the stated compatibility target. The replacement tackles the earlier implementation's problems with modern Android tooling, while the iOS path runs through Google's GIDSignIn SDK. Teams can use one Unity package across both mobile operating systems without assembling separate Google sign-in integrations themselves.

Google said: “The new implementation is designed to reduce integration work and address compatibility problems found in older versions.”

For an engineering lead, adoption work is specific: use the supported Unity 6.5 plugin, add the Web Client ID and iOS Reversed Client ID in the editor, and access the returned token from Unity C# scripts. Those scripts can send the token to Firebase Authentication, Supabase, Auth0 or an existing in-house backend.

The choice of backend remains separate from the choice of sign-in provider. Google supplies the credential; the studio's backend determines how it fits into the player-account system. That structure preserves existing account services while adding Google as another authentication route.

The scope remains narrow: native mobile sign-in, token retrieval and editor-based setup, packaged as open source for Unity 6.5. Studios keep their existing player-account infrastructure and gain a supported Google sign-in path without taking on a new account platform.

The market signal worth watching is adoption across Android and iOS releases. If studios standardize on the package, the old Android compatibility problem becomes less likely to push teams toward separate, hand-built native integrations.

via github.com (Original)

Share this article:

More from Priya Raman

Priya Raman

Show full bio

Market editor covering technology and product news in video game industry at Game Dev Wire.

227 articles