User Guide

Creating and Uploading a Firebase Key

To send mobile push notifications via Firebase Cloud Messaging (FCM), register the project in Google Firebase, create a key, and upload it to Reteno.

Creating a Project

  1. Go to the Google Firebase service page and click Get started.
Firebase homepage with the Get started button highlighted.
  1. Click the Create a project button.
Firebase console welcome page with the Create a project button highlighted.
  1. Name the project and accept the terms of use; click Continue.
Create a project step 1 of 3 with a project name entered, terms checkboxes selected, and the Continue button highlighted.
  1. Activate or deactivate the use of Google Analytics for the project; click Continue.
Create a project step 2 of 3 with the Enable Google Analytics toggle turned on and the Continue button highlighted.

If you have agreed to use Google Analytics, select or create a Google Analytics account; click Create project.

Create a project step 3 of 3 with the Google Analytics account selector and Create project button highlighted.
  1. Your new project is ready; click Continue.
Confirmation screen showing the new Firebase project is ready, with the Continue button highlighted.

Generating a Key

  1. In the left panel, click the settings wheel next to Project Overview and go to the Project settings menu.
Firebase project overview page with the settings menu open and Project settings highlighted.
  1. Go to the Service accounts tab and click the Generate new private keybutton.
Project settings Service accounts tab with the Generate new private key button highlighted.
  1. Click Generate key In the dialog box.
Generate new private key dialog with a security warning and the Generate key button highlighted.
  1. Download the key to your device.

Uploading a Key to Reteno

Go to your Reteno account settings to the Mob Push tab, open one of the previously created applications or create a new one and upload a key file.

Reteno mobile app setup page showing Android and iOS platforms configured via FCM, with the Upload file button highlighted for the Firebase private key.

More on connecting mobile app >

Troubleshooting: Push Sent But Not Delivered to Device

If a push doesn't arrive on the device during testing, but the send didn't produce any error in the Reteno UI, this means FCM accepted the request ā€” the issue is not on Reteno's side. In this case, check the contact's device list: a contact with a large number of accumulated devices (for example, from repeated reinstalls or multiple test devices over time) can have unreliable delivery to any single one of them. See Error Codes for Mobile Push Notifications for other push delivery error scenarios.

Updated 10 days ago

Did this page help you?