Source: https://docs.expo.dev/guides/google-authentication

Hide navigation

Ctrl K

Home Guides EAS Reference Learn

Archive Expo Snack Discord and Forums Newsletter

Using Google authentication

Edit page

Copy page

A guide on using @react-native-google-signin/google-signin library to integrate Google authentication in your Expo project.

Edit page

Copy page

The @react-native-google-signin/google-signin library provides a way to integrate Google authentication in your Expo app. It also provides native sign-in buttons and supports authenticating the user as well as obtaining their authorization to use Google APIs. You can use the library in your project by adding the config plugin in the app config .

This guide provides information on how to configure the library for your project.

Prerequisites

The @react-native-google-signin/google-signin library can't be used in the Expo Go app because it requires custom native code. Learn more about adding custom native code to your app .

Installation

See @react-native-google-signin/google-signin documentation for instructions on how to install and configure the library:

React Native Google Sign In: Expo installation instructions

Configure Google project for Android and iOS

Below are instructions on how to configure your Google project for Android and iOS.

Upload app to Google Play Store

We recommend uploading the app to the Google Play Store if your app intends to run in production. You can submit your app to the stores for testing even if your project is still in development. This allows you to test Google Sign In when your app is signed by EAS for testing, and when it is signed by Google Play App Signing for store deployment. To learn more about the app submission process, see the guides below in the order they are specified:

Create your first EAS Build Build your project for app stores Manually upload Android app for the first time

Configure your Firebase or Google Cloud Console project

Refer to the library's documentation for a more in-depth configuration guide.

For Android, once you have uploaded your app, you need to provide the SHA-1 certificate fingerprint values when asked while configuring the project in Firebase or Google Cloud Console. There are two types of values that you can provide:

Fingerprint of the .apk you built (on your machine or using EAS Build). You can find the SHA-1 certificate fingerprint in the Google Play Console under Release > Setup > App Integrity > Upload key certificate.
Fingerprint(s) of a production app downloaded from the play store. You can find the SHA-1 certificate fingerprint(s) in the Google Play Console under Release > Setup > App Integrity > App signing key certificate.

With Firebase

For more instructions on how to configure your project for Android and iOS with Firebase:

Firebase

Upload google-services.json and GoogleService-Info.plist to EAS

If you use the Firebase method for Android and iOS (as shared in sections above), you'll need to make sure google-services.json and GoogleService-Info.plist are available in EAS for building the app. You can check them into your repository because the files should not contain sensitive values, or you can treat the files as secrets, add them to .gitignore and use the guide below to make them available in EAS.

Upload a secret file to EAS and use in the app config

With Google Cloud Console

This is an alternate method to configure a Google project when you are not using Firebase .

For more instructions on how to configure your Google project Android and iOS with Google Cloud Console:

Expo without Firebase