Google SignIn

The Google SignIn add​on implements Google Play login features into your mobile application, on both Android and iOS.

Features include google authentication, silent google authentication, getting the google profile information, like the display name, email address, family name, given name, image url and user id.

It also supports requesting server credentials for server implementations or services like PlayFab, credentials like the id token and server authentication code.

It will integrate the native mobile Google Account features into your mobile application.



1. The first step is to add the Google SignIn addon into the project.

2. Enable debug mode to log errors in the console. This is useful for mobile usb debugging using Chrome inspect devices on Android or Safari web inspector on iOS.

3. To be able to get the server credentials like the id token or the server auth code, the web client id must be filled, which is useful for server implementations or for using server services like PlayFab. Thus, adding the web client id is required. 

This can be found on your project's API credentials page on the Google Developer Console.

4. The Reversed Client ID is a field that varies depending on the platform.

  • Android - Input the reverse value of the Client ID on your Google application's Android generated configuration file. 

    From the Google Developer Console, this would be :

    Example: would become com.googleusercontent.apps.123-abc123.​

  • iOS - The value can be found on your Google application's iOS generated configuration file.




The Google SignIn is an addon that integrates the native mobile Google Plus SDK into an application made by Construct 2 or Construct 3 with support for both android and ios.
It allows you to use the various auth and profile tools Google provides to implement for your applications.

Features :

  • Full native Android SDK integration.

  • Full native iOS SDK integration.

  • Google account authentication.

  • Google account profiling.

  • Easy to use and no programming required.

  • Well-supported and fully tested.

  • Login & Silent Login.

  • Display Name, Email Address,

  • Family Name, Given Name,

  • Profile Image URL & User ID .

  • Server ID Token

  • Server Auth Code

  • Construct 2 editor support.

  • Construct 3 editor support.

  • Construct 2 runtime.

  • Construct 3 runtime.

  • C3 Build Service, PhoneGap.

  • Cordova CLI & Android Studio.


Additional Configuration

The get the configuration file for your Google application on both Android and iOS, you need to enable Google-Sign In your application and the necessary credentials will be automatically generated.

  • Android - To configure Android, generate a configuration file here. Once Google Sign-In is enabled, Google will automatically create the necessary credentials in the Developers Console.

  • iOSTo configure iOS, generate a configuration file here. This GoogleService-Info.plist file contains the revered client id you'll need.
    The reversed client id for iOS is also known as the iOS URL Scheme on the Apple XCode.


Browser Features

The get the web client id for your Google application on both Android and iOS, you may generate it at the project's API credentials on the Google Developer Console.

If you plan to run this on a browser, ensure to also add your url address (example: http://localhost:3000) into the Authorized JavaScript origins section.


Android Build Registration

The Android setup has a bit more steps to do, but everyone who integrates the native Google Play login into their games have to go through these steps, as required by Google. So, please persist a little bit more, we're almost finished!

Credentials for  Google Registration

It is important to register your .apk or .aab credentials to Google, otherwise it will fail to authenticate. This needs to be done for both a debug .apk / .aab or a release .apk / .aab. For more info, click here.

You basically need to execute the keytool on a terminal to get your digitally signed .apk's / ..aab's SHA1 fingerprint. 
Fortunately there are two (2) ways to do this! The quick way for beginners and the advanced way for experienced programmers.

  • Quick way - is to use the C3 Build Service's built-in SHA1 fingerprint automatic generator when you make a release .apk. This is quite convenient, although you would only be able to test the Mobile Google Plus on a release .apk / .aab.

    But beginners might not yet even need the debug
    .apk's debugging tools and we constantly maintain the plugin, so in normal circumstances, there should be nothing to debug.

    Henceforth, we recommend this quick and easy approach, even for advanced users.

  • Advanced way - is to generate the SHA1 fingerprint manually using the previously mentioned keytool utility on the terminal.

    • Syntax:
      $ keytool -exportcert -keystore <path-to-debug-or-production-keystore> -list -v -alias <alias-name>

    • For more information, it's best to read the exact documentation.

Register Credentials to Google

Now that you have the build credentials, to be specific, the SHA1 fingerprint of your build. You need to register it to the Credentials page in the API Console. Follow the steps below:

  • Click Create credentials > OAuth client ID.

  • Select Android.

  • In the Package name field, enter your Android app's package name.

  • Paste the SHA1 fingerprint into the form where requested.

  • Click Create.

And then now you're done!


Publishing  to the Play Store

In publishing for Android, Google resigns your application with a different certificate once published to the Play Store.

Copy that resigned SHA-1 fingerprint from the App signing section, under the Release Management of the Google Play Console, then paste the copied SHA-1 fingerprint into the OAuth client ID of the release credential from the Google Credentials Manager.

Actions, Conditions & Expressions


Authentication :

  • Login - Login to Google.

  • Silent Login - Silently Login to Google. But check if already signed in to the app and sign in silently if true.

  • Logout - Logout from Google. This will clear the OAuth2 token.

  • Disconnect - Disconnect from Google. This will clear the OAuth2 token, forget which account was used to login, and disconnect that account from the app.


Login :

  • On Login - Triggered when the "Login" has succeeded.

  • On Login Failed - Triggered when the "Login" has failed.

Silent Login :

  • On Silent Login - Triggered when the "Silent Login" has succeeded.

  • On Silent Login Failed - Triggered when the "Silent Login" has failed.

Logout :

  • On Logout - Triggered when the "Logout" has finished.

Disconnect :

  • On Disconnect - Triggered when the "Disconnect" has finished.

General :

  • Is Logged In - Checks if the "Google Login" has been established.


Authentication :

  • getEmail - Return the "Email Address" from the login.

  • getUserID - Return the "User ID" from the login.

  • getDisplayName - Return the "Display Name" from the login.

  • getFamilyName - Return the "Family Name" from the login.

  • getGivenName - Return the "Given Name" from the login.

  • getImageURL - Return the "Image URL" from the login.

  • getIDToken - Return the "ID Token" from the login. This requires the "Web Application Client ID" input on the Properties Bar.

  • getServerAuthCode - Return the "ServerAuthCode" from the login. This requires the "Web Application Client ID" input on the Properties Bar.

  • getAccessToken - Return the OAuth2 "Access Token" from the login.

  • errorMessage - Return the "Error Message" from a failed login attempt.


Universal - General Plugin Properties.

  • Debug Mode - If "Enabled", the runtime will log errors. This should be "Disabled" on production.

    • Enabled

    • Disabled

Browser - Web Browser Credentials.

  • Web App Client ID - The Browser platform requires a valid WEB_APPLICATION_CLIENT_ID that is generated at the Google Developer Console.

Mobile - Google Sign-In Credentials.

  • Reversed Client ID - The Mobile iOS platform requires a valid REVERSED_CLIENT_ID that is contained at the GoogleService-Info.plist.


Feature Showcase

The Google SignIn is an addon that integrates the native mobile Google Account SDK into an application made by Construct 3 or Construct 2, with support for both android and ios.
It allows you to use the various tools Google provides to implement for your application.


Game Project

Sample Setup Project


  • Instructions - The sample project has comments and instructions on how to use the addon and its features.

  • A.C.E. Coverage - It covers the implementation of each action, condition and expression.

  • Tips and Tricks - It provides some tips and tricks to a better use of the addon and of the event-sheet system alongside it.



Get the tools

for your pro games!

Constuct Master Collection -
Constuct Master Collection - Discord
Constuct Master Collection - Construct 3

© Construct Master Collection 2021 • All rights reserved

Contact Information: