AppifyWebsite
All guides

Google sign-in with the account picker

Let people sign in with one tap using the Google accounts already on their phone, instead of typing their email and password.

About 15–20 minutes

Before you start

  • A Google account
  • Your app's package name and SHA-1 (shown in the Google sign-in tab)
  • Your website already supports 'Sign in with Google'
  1. 1

    Open Google Cloud Console

    Go to console.cloud.google.com and sign in.

    At the top, open the project picker. If your website already uses Google sign-in, choose that same project — this is important, both client IDs must be in one project.

    Otherwise click New project, name it after your app and click Create.

  2. 2

    Set up the consent screen

    Left menu → APIs & Services → OAuth consent screen (may be called 'Google Auth Platform → Branding').

    Fill in the app name, support email and your website's domain. Save.

    Under Audience, choose External and click Publish app so anyone can sign in (not only test users).

  3. 3

    Create (or find) the Web client ID

    APIs & Services → Credentials → Create credentials → OAuth client ID.

    Application type: Web application. Add your website address under Authorised JavaScript origins.

    Click Create and copy the Client ID (ends in .apps.googleusercontent.com).

    If your website already has a Web client, just copy that one instead.

  4. 4

    Create the Android client ID

    Credentials → Create credentials → OAuth client ID → Application type: Android.

    Paste your package name and SHA-1 exactly as shown below (or in the Google sign-in tab).

    Click Create. You don't need to copy anything else from here — its ID is only used to prove the app is yours.

    Package name:Open this guide from your app's builder to see yours
    SHA-1:Open this guide from your app's builder to see yours
  5. 5

    Paste both IDs into AppifyWebsite

    Open your app → Google sign-in tab.

    Paste the Web client ID and the Android client ID into their boxes. A green tick means the format is right.

    Click 'Detect from my website' so the app knows how to finish sign-in on your site, then click 'Check Google sign-in'.

  6. 6

    Rebuild and install

    Click Build, then install the new version on your phone (uninstall the old one first if it was signed differently).

    Tap your website's 'Sign in with Google' button — the account picker should slide up from the bottom.

  7. 7

    After uploading to Google Play: add Google's fingerprint

    Google Play re-signs your app, which gives it a second SHA-1.

    Play Console → your app → Test and release → App integrity → App signing. Copy the 'App signing key certificate' SHA-1.

    Back in Google Cloud, create another Android client ID with the same package name and this second SHA-1.

    Without this, sign-in works from the file you downloaded but not from the Play Store version.

How to check it worked

  • The account picker appears from the bottom of the screen
  • After picking an account you land signed in on your website
  • It still works after closing and reopening the app

Common problems

I see Google's normal login page instead of the picker

The package name or SHA-1 in Google Cloud doesn't match the app. Copy them again from the Google sign-in tab and make sure you installed the newest build.

'Developer console is not set up correctly' or error 10

The Web and Android client IDs are in different Google projects, or the Android client's SHA-1 is wrong.

Works when installed from the file, fails from Play Store

You skipped the last step — add the Play app signing SHA-1 as another Android client.

The picker shows, but I'm not signed in on the site

Click 'Detect from my website' again and rebuild. If your site uses its own login backend, contact us with the app name.

Still stuck? Contact support — we reply within one business day.