Why does getToken trigger a 403 PERMISSION_DENIED error in Firebase installations?

Below is a list of steps you can follow to troubleshoot the error message:

Understand the Error

The error

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 the client was not allowed to call the Firebase Installations API. This API is used internally by Firebase Messaging when obtaining your FCM token.

Common Causes & Solutions

1. API Key Restrictions
   If your API key is restricted (for example, to specific referrers or IPs), it might block requests to the Installations API.
   Solution:

   • Go to the Google Cloud Console.
   • Locate your API key in the Credentials page.
   • Remove or relax any restrictions (or add the necessary ones) so that requests to firebaseinstallations.googleapis.com are allowed.

2. Incorrect VAPID Key / Configuration
   Make sure you are using the correct VAPID key associated with your Firebase project and that your Firebase web configuration is correct.
   Solution:

   • Verify that your Firebase project settings (Web configuration) include the proper VAPID key.
   • Double-check that the configuration passed to Firebase is valid.

3. Firebase Project or Console Settings
   Occasionally, the Firebase project settings might prevent certain API calls if not properly set up.
   Solution:

   • Ensure that your Firebase project is fully configured.
   • Look for any pending alerts or setup steps in the Firebase console.

4. Outdated Dependencies or SDK Version
   Using an outdated Firebase SDK might sometimes lead to unexpected permissions issues.
   Solution:

   • Update your Firebase libraries to the latest version.
   • Rebuild and retest your app.

Example Code (for Context)

While the code you posted is already correct regarding how to call getToken, make sure the configuration (API keys, VAPID key, firebaseApp initialization) is done as recommended in the Firebase setup guide:

JAVASCRIPTCopied
import { initializeApp } from 'firebase/app';
import { getMessaging, getToken } from 'firebase/messaging';

const firebaseConfig = {
  // your config here: apiKey, authDomain, projectId, etc.
};

const firebaseApp = initializeApp(firebaseConfig);
const firebaseMessaging = getMessaging(firebaseApp);

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

Summary

The 403 error is not directly related to your code's syntax but rather a permission issue with your Firebase project’s settings or API key restrictions. Reviewing these settings and ensuring your keys and configuration are set up correctly should help resolve the issue.