Add Google Service Account Keys using FCM V1

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.

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

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

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

EAS CLIexpo.dev

• Run eas credentials
• Select Android > production > Google Service Account
• Select Manage your Google Service Account Key for Push Notifications (FCM V1)

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

• Click Add a service account key
• Under Upload new key, upload your JSON credential and click Save

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. If you're using version control, add it to your ignore file (for example, .gitignore) as it contains sensitive data.

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

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

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

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

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.

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

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

EAS CLIexpo.dev

• Run eas credentials
• Select Android > production > Google Service Account
• Select Manage your Google Service Account Key for Push Notifications (FCM V1)

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

• Click Add a service account key
• Upload your JSON credential and click Save

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. If you're using version control, add it to your ignore file (for example, .gitignore) as it contains sensitive data.

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

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

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

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