Google Sign-In

Last updated: Oct 28, 2026

The Google Sign-In module enables native Google authentication inside your app. Instead of filling out a login form, users pick a Google account already saved on their device — no password required. Your website opens the native account picker through the JavaScript Bridge and receives the user's Google ID token back, which your backend verifies to log the user in.

Note: The app does not take over your website's existing Google login automatically. Your website needs a small change so that, inside the app, its "Sign in with Google" button triggers native sign-in through the JavaScript Bridge.

How It Works

  1. The user taps your website's "Sign in with Google" button inside the app.
  2. Your website sends a google_sign_in message to the app through the JavaScript Bridge.
  3. The app opens the native Google account picker and the user selects an account.
  4. The app sends the user's profile and Google ID token back to your website.
  5. Your website sends the ID token to its backend, which verifies it with Google and logs the user in.

In a regular browser the JavaScript Bridge does not exist, so your website keeps using its normal web Google login there.

Android / iOS Client ID

The OAuth 2.0 Client ID for your Android or iOS app, created in Google Cloud Console.

Steps to create it:

  1. Go to Google Cloud Console and open the same project where your website's Web Client ID is created.
  2. Navigate to APIs & Services → Credentials.
  3. Click Create Credentials → OAuth Client ID.
  4. Choose Android or iOS as the application type.
  5. For Android, enter your package name and SHA-1 fingerprint (shown in your Appilix dashboard).
  6. For iOS, enter your Bundle ID.
  7. Save and copy the generated Client ID.

Important: The Android/iOS Client ID must belong to the same Google Cloud project as your Web App Client ID. If they are in different projects, sign-in fails with a configuration error.

After Publishing to Google Play (Android)

When you publish your app to Google Play and enable Play App Signing, Google re-signs your app with their own key. This means the SHA-1 fingerprint changes from the one in your Appilix dashboard, and Google Sign-In will stop working for users who installed from the Play Store.

Getting the SHA-1 from Play Console

  1. Open Google Play Console and select your app.
  2. In the left sidebar, click Protected with Play.
  3. Under Play Store protection, expand the section and click Manage Play app signing.
  4. On the App signing page, find the App signing key certificate section.
  5. Copy the SHA-1 certificate fingerprint.

Once you have the SHA-1, open your existing Android OAuth Client ID in Google Cloud Console and replace the SHA-1 fingerprint with the one from Play Console, then save.

Note: After replacing, Google Sign-In will work for Play Store installs but will no longer work for direct APK installs, since the SHA-1 no longer matches the Appilix keystore. This is expected — your published app on the Play Store is what matters at this stage. If you ever need to test using a direct APK again, simply update the SHA-1 back to the one shown in your Appilix dashboard.

Web App Client ID

Your website's Web application OAuth Client ID, from the same Google Cloud project. The ID token and auth code the app returns to your website are issued for this Client ID, so your backend verifies them against it.

Where to find it: In Google Cloud Console, go to APIs & Services → Credentials and copy the Client ID whose type is Web application. If your website already uses Google login, use that same Client ID. If you don't have one, click Create Credentials → OAuth Client ID and choose Web application.

  • Maximum length: 200 characters

Scopes (Optional)

The Google account permissions requested during sign-in, separated by spaces. Leave blank to use the default.

  • Default: email profile
  • Example: email profile https://www.googleapis.com/auth/calendar.readonly
  • Maximum length: 200 characters

Extra scopes beyond email profile are only useful when your backend requests a server auth code to call Google APIs on the user's behalf. Scopes can only be set here — they cannot be changed from the JavaScript Bridge.

Triggering Sign-In from Your Website

Inside the app, your website's "Sign in with Google" button must trigger native sign-in through the JavaScript Bridge, then send the returned ID token to your backend for verification.

See Google Sign-In JS Bridge for the code, response fields, and backend verification examples.