What is the purpose of the Google-service file and Private Certificate/Key? These files are used to enable FCM (Firebase Cloud Messaging). FCM is a cross-platform messaging solution that lets you reliably deliver messages at no cost. It inherits the reliable and scalable GCM infrastructure, plus Push notification enhancements for Android and iOS users!

We’ll break these down into two sections, one for each file: the Google Service File and the Private Key. First, we’ll show you how to create your Google Service File.

**VERY IMPORTANT**

Once you have uploaded both files to your Control Panel, your iOS and Android app must be updated to include them. Make sure to let us know that you’ve uploaded these files and we’d be happy to resubmit your app to Google Play and the Apple App Store.

How do I create my Google Service File?

Step 1. Go to https://firebase.google.com/ and click Get Started.

Step 2. Log into the same account you used to register your Google Developer account.

Step 3. Select Add Project.

Step 4. Under Project Name, input the name of your Android app, agree to Google’s terms, then click Create Project.

**Please note that if you have already added the project to your Firebase Console there is no need to re-add it. Simply select the existing project and move on to Step 5 below.**

Step 5. From the main dashboard of your Firebase Console, select "+Add app."

Step 6. From here, select either the iOS button or the Android button, based on which Firebase certs you are creating. The steps afterwards are the same.

Step 7. The next screen will display a number of fields to fill out.

Head back to your Control Panel, go to Advanced > Certificates and Keys.

Here, copy the App Bundle ID. Please note, you're Bundle ID may differ or be the same between iOS and Android.

Step 8. Return to Firebase console and paste your App Bundle ID under the Android Package Name field or the Apple Bundle ID, depending on which platform you're creating Firebase certificates for. Then, click Register App.

iOS:

Android:

Note: The App nickname is an optional field. Here, you can input a name to help you identify your project or simply use the name of your app. Additionally, the Debug Signing Certificate SHA-1 is also an optional step. If you are familiar with setting this up, you are welcome to do so. However, it is advised to keep this blank until absolutely necessary. This is because you are unable to have the same combination of Package names and SHA-1 Hashes in more than one place. This can cause issues with multiple projects in which you will have to track down the original project and delete the original signature.

Step 9. Download your google-services.json or your GoogleService-info.plist file and click Next. The .json file is for Android and the .plist file is for iOS.

iOS:

Android:

Step 10. At the bottom of the screen click Next > Continue to Console.

Step 11. In your Control Panel, head to the Advanced Tab on the left and click Certificates and Keys. Click "Select File" and insert the newly downloaded Google .json file for Android. For iOS, upload the downloaded .plist file. Then, click upload at the bottom.


How do I create my Private Certificate/Key?

Step 1. On the Firebase console under Project Settings, go to the Service Accounts tab.

Step 2. Under Firebase Admin SDK click Generate New Private Key.

Step 3. From the prompt, select Generate Key

Step 4. Upload your Private Certificate/Key to your app’s Control Panel. Click Upload to finish.

Congratulations! You've successfully created and uploaded your Firebase Certificates for both iOS and Android. As a reminder, remember that the steps to create these are the same for both platforms. The only difference is selecting the appropriate platform, Android or iOS, at the beginning of certificate creation.

Have questions? No problem! Reach out to us and we’ll be ready to help :)

Did this answer your question?