Source: https://docs.expo.dev/push-notifications/fcm-credentials

Hide navigation

Search

Ctrl K

Home Guides EAS Reference Learn

Archive Expo Snack Discord and Forums Newsletter

Obtain Google Service Account Keys using FCM V1

Edit page

Copy page

Learn how to create or use a Google Service Account Key for sending Android Notifications using FCM.

Edit page

Copy page

---

Create a new Google Service Account Key

---

Here are the steps to configure a new Google Service Account Key in EAS for sending Android Notifications using FCM V1.

1

Create a new Firebase project for your app in the Firebase Console . If you already have a Firebase project for your app, continue to the next step.

2

In the Firebase console, open Project settings > Service accounts for your project.

3

Click Generate New Private Key, then confirm by clicking Generate Key. Securely store the JSON file containing the private key.

4

Upload the JSON file to EAS and configure it for sending Android notifications. This can be done using EAS CLI or in EAS dashboard .

EAS CLI

expo.dev

• Run eas credentials
• Select Android > production > Google Service Account
• Select Manage your Google Service Account Key for Push Notifications (FCM V1)
• Select Set up a Google Service Account Key for Push Notifications (FCM V1) > Upload a new service account key
• If you've previously stored the JSON file in your project directory, the EAS CLI automatically detects the file and prompts you to select it. Press Y to continue.

Note: Add the JSON file to your version source control's ignore file (for example, .gitignore) to avoid committing it to your repository since it contains sensitive data.

• Under Project settings, click Credentials in the navigation menu
• For Android, click Add Application Identifier or select an existing Application identifier
• Under Service Credentials > FCM V1 service account key, click Add a service account key

• Under Upload new key, upload your JSON credential and click Save

5

Configure the google-services.json file in your project. Download it from the Firebase Console and place it at the root of your project directory.

This file is required for your Android app to be registered with FCM. You may commit this file to your repository since it contains public-facing identifiers from your Firebase project.

Note: You can skip this step if google-services.json has already been set up.

In app.json, add expo.android.googleServicesFile with its value as the path of the google-services.json.

app.json

Copy

{ "expo": { %%placeholder-start%%...%%placeholder-end%% "android": { %%placeholder-start%%...%%placeholder-end%% "googleServicesFile": "./path/to/google-services.json" } }

6

You're all set! You can now send notifications to Android devices via Expo Push Notifications using the FCM V1 protocol.

Use an existing Google Service Account Key

---

1

Open the IAM Admin page in Google Cloud Console. In the Permissions tab, locate the Principal you intend to modify and click the pencil icon for Edit Principal.

2

Click Add Role and select the Firebase Messaging API Admin role from the dropdown. Click Save.

3

You have to specify to EAS which JSON credential file to use for sending FCM V1 notifications, using EAS CLI or in EAS dashboard . You can upload a new JSON file or select a previously uploaded file.

EAS CLI

expo.dev

• Run eas credentials
• Select Android > production > Google Service Account
• Select Manage your Google Service Account Key for Push Notifications (FCM V1)
• Select Set up a Google Service Account Key for Push Notifications (FCM V1) > Upload a new service account key
• The EAS CLI automatically detects the file on your local machine and prompts you to select it. Press Y to continue.

Note: Add the JSON file to your version source control's ignore file (for example, .gitignore) to avoid committing it to your repository since it contains sensitive data.

• Under Project settings, click Credentials in the navigation menu
• For Android, click Add Application Identifier or select an existing Application identifier
• Under Service Credentials > FCM V1 service account key, click Add a service account key

• Under Upload new key, upload your JSON credential and click Save

4

Configure the google-services.json file in your project. Download it from the Firebase Console and place it at the root of your project directory.

This file is required for your Android app to be registered with FCM. You may commit this file to your repository since it contains public-facing identifiers from your Firebase project.

Note: You can skip this step if google-services.json has already been set up.

In app.json, add expo.android.googleServicesFile with its value as the path of the google-services.json.

app.json

Copy

{ "expo": { %%placeholder-start%%...%%placeholder-end%% "android": { %%placeholder-start%%...%%placeholder-end%% "googleServicesFile": "./path/to/google-services.json" } } }

5

You're all set! You can now send notifications to Android devices via Expo Push Notifications using the FCM V1 protocol.