Firebase Functions API激活等待：环境变量配置失效问题求助

Hey Jesper, sorry to hear you're stuck with this—since your setup worked perfectly just two weeks ago, this is likely a configuration drift or minor service hiccup we can fix with a few checks. Let's walk through the most common fixes step by step:

• Check your firebase-tools version first
  Sometimes recent CLI updates can introduce unexpected issues. Run firebase --version to see what you're on. If you updated since things worked, try rolling back to a stable version you know worked before. For example:
  npm install -g firebase-tools@12.8.1 (replace with the specific version you were using two weeks ago)

• Verify environment variable deployment
  It’s easy to forget that setting env vars with firebase functions:config:set doesn’t automatically push them to production. Make sure you’ve deployed the config changes with:
  firebase deploy --only functions:config
  If testing locally, you also need to export the config to a local file for the emulator to pick up:
  firebase functions:config:get > functions/.runtimeconfig.json
  Double-check that this file exists in your functions directory and isn’t being ignored by .gitignore.

• Confirm dependent APIs are enabled
  The "waiting for APIs to activate" message often points to a required Google Cloud API being disabled. Head to the Google Cloud Console for your project, navigate to APIs & Services > Enabled APIs & Services, and make sure these are turned on:

  • Cloud Functions API
  • Cloud Build API
  • Cloud Storage API (if your functions interact with storage)
    If any are disabled, enable them, wait 5-10 minutes for activation to complete, then redeploy your functions.

• Restart the Functions Emulator (local testing only)
  Emulators don’t pick up config changes on the fly. Kill any running emulator processes and restart them with:
  firebase emulators:start --only functions

• Double-check config reading in your code
  Make sure you’re accessing env vars correctly. For example, if you set firebase functions:config:set api.key="abc123", your code should use functions.config().api.key—watch for typos in variable names or nesting structure.

• Dig into logs for hidden errors
  The generic "waiting for APIs" message might mask a specific issue. Run firebase functions:log to fetch recent logs, or check the Functions tab in the Firebase Console for detailed error messages (like permission failures or config parsing errors).

• Re-authenticate your Firebase CLI
  Rarely, auth tokens can expire or get corrupted. Run firebase login --reauth to re-authenticate your account, then try deploying again.

If none of these fix the issue, sharing your firebase-tools version, a snippet of how you’re reading env vars in code, and any specific error logs would help narrow things down further.

内容的提问来源于stack exchange，提问作者Jesper