Firebase Studio Prototype: Automatic Gemini API error

General
1

I removed some spaces due to the limit, but when creating a new project it is not generating the key automatically, it is looping and giving an error. I tried to create it manually and it says that I do not have permissions. Does anyone know if there is a limit or how I can solve it? Or is there a bug? Thanks

2 Likes
2

Hello

–Build helpers sometimes insert a default API key or test packages during setup.
These placeholder entries can persist and later cause authentication or deployment loops.

To keep your environment clean, add a small pre-deploy validation script that halts deployment whenever it detects placeholder keys or unidentified configuration lines.

npm run verify-config


// verify-config.js
import fs from "fs";

const config = fs.readFileSync(".firebaserc", "utf8");
if (/pk_test_|gemini_test/i.test(config)) {
  console.error("⚠️  Placeholder or test key detected — clean before deploy.");
  process.exit(1);
}

console.log("âś…  Configuration verified. Proceed.");

After adding this check, review your project documentation and ensure that your configuration fully matches Firebase and Gemini setup guidelines.
Give yourself a full 72 hours to read through the docs and confirm your project’s alignment. Then try:

Project Status Notifier

A small Node utility that posts status updates to Slack during build or deployment.

Features

  • Works with any Slack incoming webhook.
  • Configurable message text and project name.
  • Zero external dependencies beyond axios and dotenv.
  • Perfect for Firebase or Node-based workflows.

Example

./index.js "Configuration verified âś…" "MyFirebaseApp"