Firebase options are a set of parameters required by services in order to successfully communicate with Firebase server APIs and in order to associate client data with your Firebase project and Firebase application.
Firebase services rely on valid Firebase options being available from the Firebase common SDK FirebaseApp, created during Firebase initialization.
Different Firebase services require different Firebase options to function properly, but all Firebase services require the following Firebase options:
- API key - Note: this is not an FCM server key, see below.
Example value:AIzaSyDOCAbC123dEf456GhI789jKl012-MnO - Project ID
Example value:android-myapp-123 - Application ID, a.k.a.
mobilesdk_app_id,GOOGLE_APP_ID, "AppId" - Note: this is not an Android package name!
Example value:1:1234567890:android:321abc456def7890
To improve security Firebase SDK updates on February 27 and afterwards replaced the Firebase Instance ID service with a dependency on the Firebase Installations API.
Firebase Installations enforces the existence and validity of mandatory Firebase options API key, Project ID, and Application ID in order to associate client data with your Firebase project.
If you are reading this message, most likely your application is initializing Firebase without the required set of Firebase options.
Your application may be using an incomplete or erroneous google-services.json configuration file; or your app is programmatically initializing Firebase without the full set of required Firebase options.
As a result, Firebase services like Firebase Cloud Messaging (FCM) will malfunction for end-users who installed your app after it was released with the updated Firebase SDKs. Additionally, repeated failing requests to Firebase may slow down the end-user experience of your app.
To fix malfunctioning Firebase services for your applications, please take the following steps as soon as possible:
- Update your application by initializing Firebase with a valid API key of your project, a valid Project ID, and a valid Application ID (a.k.a. mobilesdk_app_id, GOOGLE_APP_ID, or simply "App Id").
- Default initialization process using a Firebase config file: Download your
google-services.jsonconfig file from the Firebase console, then replace the existing file in your app. - Programmatic initialization using a
FirebaseOptionsobject: Download yourgoogle-services.jsonconfig file from the Firebase console to find your API key, Project ID, and Application ID, then update these values in theFirebaseOptionsobject in your app.
- Default initialization process using a Firebase config file: Download your
- Release a new version of your app to the Play Store.
If your app is using an FCM Server key rather than a Cloud API key, this could cause a security vulnerability in case you are using the same FCM Server key to send push notifications via FCM.
In this case, we strongly recommend that you revisit how your server authenticates send requests to FCM.
Please note that FCM Server Keys (not the same as the Firebase / Cloud API key) must not be included in applications as they can be abused to send push-notifications in the name of your project.
You can reach out to support at any time if you have any questions.