[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["缺少我需要的資訊","missingTheInformationINeed","thumb-down"],["過於複雜/步驟過多","tooComplicatedTooManySteps","thumb-down"],["過時","outOfDate","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["示例/程式碼問題","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-04 (世界標準時間)。"],[],[],null,["If you initialize your app without a valid set of Firebase options, new users of\nyour application will experience serious issues.\n\nFirebase options are a set of parameters required by services in order to\nsuccessfully communicate with Firebase server APIs and to associate client data\nwith your Firebase project and Firebase application. Firebase services rely on\nvalid Firebase options being available from the Firebase core/common library\ncreated during Firebase initialization.\n\nDifferent Firebase services require different Firebase options to function\nproperly, but all Firebase services require the following Firebase options:\n\n- **[API key](https://cloud.google.com/docs/authentication/api-keys)** - Note: this is **not** an FCM server key, see [FCM server keys](#fcm_server_keys). \n Example value: `AIzaSyDOCAbC123dEf456GhI789jKl012-MnO`\n- **[Project ID](/docs/projects/learn-more#project-id)** - Example value: `myapp-project-123`.\n- **Application ID (\"AppID\")** - Unique identifier for your app whose format depends on platform:\n - For Android: `mobilesdk_app_id`---Note: **this is not an Android package name** . \n Example value: `1:1234567890:android:321abc456def7890`\n - For iOS+: `GOOGLE_APP_ID`---Note: **this is not an Apple Bundle ID** . \n Example value: `1:1234567890:ios:321abc456def7890`\n\nTroubleshoot Android apps\n\nTo improve security, Firebase SDK updates [on February 27](/support/release-notes/android#2020-02-27) and\nafterwards replaced the Firebase Instance ID service with a dependency on the\n[Firebase Installations API](https://console.cloud.google.com/apis/library/firebaseinstallations.googleapis.com).\n\nFirebase installations enforces the existence and validity of mandatory Firebase\noptions API key, Project ID, and Application ID in order to associate client\ndata with your Firebase project. See [`FirebaseOptions`](/docs/reference/android/com/google/firebase/FirebaseOptions) for more\ninformation.\n\nFirebase Cloud Messaging (FCM) with Firebase Instance ID (IID)\n\nIf new users of your app are experiencing issues with FCM, it's\npossible that you are initializing Firebase without the required set of Firebase\noptions.\n\nYour application may be using an incomplete or erroneous\n[google-services.json](/docs/reference/android/com/google/firebase/FirebaseApp)\nconfiguration file; or your app is\n[programmatically initializing Firebase](/docs/projects/multiprojects) without the full set of required\nFirebase options.\n\nAs a result, Firebase services like Firebase Cloud Messaging will malfunction\nfor end users who installed your app after it was released with the updated\nFirebase SDKs. Additionally, repeated failing requests to Firebase may slow down\nthe end-user experience of your app.\n\nWhat do I need to do?\n\nTo fix malfunctioning Firebase services for your applications:\n\n1. Update your application by initializing Firebase with a valid API key of your project, a valid Project ID, and a valid Application ID (`mobilesdk_app_id` or \"App Id\").\n - **Default initialization process using a Firebase config file** : [Download your google-services.json config file](https://support.google.com/firebase/answer/7015592) from the Firebase console, then replace the existing file in your app.\n - **Programmatic initialization using a `FirebaseOptions` object** : [Download your google-services.json config file](https://support.google.com/firebase/answer/7015592) from the Firebase console to find your API key, Project ID, and Application ID, then update these values in the `FirebaseOptions` object in your app.\n2. Release a new version of your app to the Play Store.\n\nTroubleshoot Apple apps\n\nTo improve security, Firebase SDK updates [on January 14](/support/release-notes/ios#version_6150_-_january_14_2020)\nand afterwards replaced the Firebase Instance ID service with a dependency on\nthe [Firebase Installations API](https://console.cloud.google.com/apis/library/firebaseinstallations.googleapis.com).\n\nFirebase installations enforces the existence and validity of mandatory Firebase\noptions API key, Project ID, and Application ID in order to associate client\ndata with your Firebase project. See [`FIROptions`](/support/guides/docs/reference/ios/firebasecore/api/reference/Classes/FIROptions) for more\ninformation.\n\nFirebase Cloud Messaging (FCM) with Firebase Instance ID (IID)\n\nIf new users of your app are experiencing issues with FCM, it's\npossible that you are initializing Firebase without the required set of Firebase\noptions.\n\nYour application may be using an incomplete or invalid\n[`GoogleService-Info.plist`](/docs/reference/ios/firebasecore/api/refe%0Arence/Classes/FIRApp) configuration file; or your app is\n[programmatically initializing Firebase](/docs/projects/multiprojects)\nwithout the full set of required Firebase options.\n\nAs a result, Firebase services like Firebase Cloud Messaging will malfunction for\nend users who installed your app after it was released with the updated Firebase\nSDKs. Additionally, repeated failing requests to Firebase may slow down the end-\nuser experience of your app.\n\nWhat do I need to do?\n\nTo fix malfunctioning Firebase services for your applications:\n\n1. Update your application by initializing Firebase with a valid API key of your project, a valid Project ID, and a valid Application ID (`GOOGLE_APP_ID` or \"App Id\").\n 1. **Default initialization process using a Firebase config file** : [Download your GoogleService-Info.plist config file](https://support.google.com/firebase/answer/7015592) from the Firebase console, then replace the existing file in your app.\n 2. **Programmatic initialization using a `FIROptions` object** : [Download your GoogleService-Info.plist config file](https://support.google.com/firebase/answer/7015592) from the Firebase console to find your API key, Project ID, and Application ID, then update these values in the `FIROptions` object in your app.\n2. Release a new version of your app to the App Store.\n\nFCM Server keys\n\nIf your app is using an [FCM Server key](/docs/cloud-messaging/auth-server#authorize-legacy-protocol-send-requests)\nrather than a\nCloud API key, this could cause a security vulnerability in case you are using\nthe same FCM Server key to send push notifications via FCM.\nIn this case, we strongly recommend that you revise how your server\n[authenticates send requests to FCM](/docs/cloud-messaging/auth-server).\n\nNote that FCM Server Keys (which are not the same as the\nFirebase/Cloud API keys) must not be included in applications, as they can be\nabused to send push notifications in the name of your project."]]
