How can I fix the Firebase 403 PERMISSION_DENIED error when retrieving an FCM token?

Below is an explanation and some troubleshooting tips for the error you're encountering.

---

What Is Happening

The error message:

FirebaseError: Installations: Create Installation request failed with error "403 PERMISSION_DENIED: Requests to this API firebaseinstallations.googleapis.com method `google.firebase.installations.v1.FirebaseInstallationsService.CreateInstallation are blocked." (installations/request-failed)

indicates that your request to create a new Firebase installation is being blocked due to insufficient permissions.

---

Possible Causes

1. API Key Restrictions
   If your API key is restricted, it might not allow calls to the Firebase Installations API. Verify that your API key is either unrestricted or properly configured to permit Firebase Installations requests.

2. Misconfiguration in Firebase Setup
   Ensure that your Firebase project is correctly set up (i.e., the configuration object contains the required fields like apiKey, projectId, senderId, etc.) and that you are using credentials belonging to the same project.

3. Incorrect VAPID Key
   The provided VAPID key should match the one registered in your Firebase Cloud Messaging settings. Double-check that it's correct and associated with your project.

---

Troubleshooting Steps

1. Check API Key Restrictions

   • Go to the Google Cloud Console.
   • Locate your API key and review its restrictions.
   • If restrictions are enabled, ensure that the Firebase Installations API is allowed.

2. Verify Firebase Configuration

   • Make sure your Firebase initialization is correct.
   • Confirm that all credentials, especially the apiKey, are for the correct Firebase project.

3. Review Firebase Console Settings

   • Check your Firebase Project settings to see if there are any restrictions on messaging or installations.
   • Validate the VAPID key in your Firebase Cloud Messaging settings.

---

Example (Pseudocode) Review

Your code snippet appears correct for getting the token:

JAVASCRIPTCopied
getToken(firebaseMessaging, { 
  vapidKey: 'BFw3u4u17-GNyllfuz4DEyZmNou70YrK1mPQI5eGODChuj6qB3iEObAt3Z6O0b7eUTpyeJ4Ox2vaWittvDoKuTc' 
})
.then((currentToken) => {
    if (currentToken) {
        console.log('FCM Token:', currentToken);
        CurrentToken = currentToken;
        console.log(firebaseApp);
        console.log(firebaseMessaging);
        sendTokenToServer(currentToken);
        // You can send this token to your server as needed.
    } else {
        console.log('No registration token available. Request permission to generate one.');
    }
})
.catch((err) => {
    console.log('An error occurred while retrieving token. ', err);
});

Focus on ensuring the messaging configuration, API key, and VAPID key are set up as expected within the Firebase console and your Google Cloud Console.

---

Final Thoughts

If you’ve confirmed that your API key and Firebase project configuration are correct and the error still occurs, there might be an issue with how your Firebase project is set up in the console. In that case:

• Double-check the Firebase Cloud Messaging documentation for any updates or changes.
• Review your project’s API usage in the Google Cloud Console to see if the Firebase Installations API has any additional configuration or quotas.

Following these steps should help resolve the 403 PERMISSION_DENIED error when creating a Firebase Installation.