2365 results found

1. First of all, Firebase Studio is really good. But after spending some time using it, I found several issues. 1. The browser page often stop

   First of all, Firebase Studio is really good. But after spending some time using it, I found several issues.

   1. The browser page often stops responding while making changes or refreshing pages. (THE MOST ANNOYING ISSUE)
   2. It takes a very long time to load pages.
   3. The AI sometimes changes things it was not prompted to change, or follows instructions from messages that were sent after a reverted version of the webpage.
   4. The AI occasionally ignores messages and takes no action.
   5. Sometimes when you write a prompt and press Enter, nothing happens and you have to retype it. This usually happens during long sessions when Firebase Studio has been open for several minutes without actions. It is safer to copy your prompt before pressing Enter.
   6. The AI works very well at first, but once the web app grows with many pages and large amounts of data, it loses control and starts doing what it thinks is best. It may rename things on its own, change metadata, or completely redesign pages when you only asked it to replace an image.
   7. The code editor does not provide any feedback that changes have been saved.
   8. You cannot manually create restore points to revert to like the AI does.
   9. When a project is archived and later unarchived for edits, there is no restore point. For example, if I unarchive my project and ask the AI to do something complex and it breaks the project, there is no way to revert to the previous version. A workaround is to ask it to do something simple, like adding a random word in a paragraph and then removing it, just to create a restore point.
   10. The builder overall is very slow. It would be better if there were a local application that could perform the same tasks without the heavy browser lag.

   These are some of the issues I encountered.

   Here are some ideas that could improve it:

   1. Instead of taking actions automatically based on what it thinks is best, the AI should first suggest changes and let the user decide whether to apply them.
   2. Easier image uploading and optimization. For example, I could upload an image to the AI, ask it to optimize it, and then use it. The AI would store it in the database and convert it to WebP or another optimized format.
   3. A prompt queue or real time handling system. While the AI is working on a prompt, I should be able to send another prompt for a different task or add missing information. The system would queue it and handle it automatically once the previous task finishes, or process them in parallel if possible.
   4. An AI action mode. This would allow you to talk with the AI without it taking any actions until that mode is enabled.
   5. AI web search and research mode, allowing it to gather real world data before building something.
   6. AI analyzers and helpers. For example, a dedicated AI that helps specifically with SEO, or one that helps design pages for a specific purpose. If you have a shop page, it could help structure it to maximize sales.
   7. Better brand consistency across pages. Sometimes the AI designs elements completely differently between pages. For example, if you ask it to add a paragraph with three images on one product page and then ask for the same thing on another product page, the layout may look completely different, like it belongs to another website.
   8. A full backup system.

   First of all, Firebase Studio is really good. But after spending some time using it, I found several issues.

   1. The browser page often stops responding while making changes or refreshing pages. (THE MOST ANNOYING ISSUE)
   2. It takes a very long time to load pages.
   3. The AI sometimes changes things it was not prompted to change, or follows instructions from messages that were sent after a reverted version of the webpage.
   4. The AI occasionally ignores messages and takes no action.
   5. Sometimes when you write a prompt and press Enter, nothing happens and you have to retype it. This usually happens during… more
   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Perform automatic rollouts only for changes to configured app directory

   I have a Next.js app within a monorepo for my Firebase project, which also includes an iOS and Android app, each in their own directories. My App Hosting backend is configured for the Next.js app directory, but it appears that the automatic rollouts feature does not take this setting into account when changes are pushed to the repo. I don't want to perform a rollout when making changes only the iOS app, for example.

   Automatic rollouts should only perform the rollout (or be able to be configured to) only when the specified app directory contains changes. Path matching is a common feature in CI/CD and I'm surprised to find that this isn't the default behavior. We should be able to specify which path(s) App Hosting monitors for changes, so that it doesn't needlessly roll out every time I make a change in the monorepo that doesn't affect the app.

   I have a Next.js app within a monorepo for my Firebase project, which also includes an iOS and Android app, each in their own directories. My App Hosting backend is configured for the Next.js app directory, but it appears that the automatic rollouts feature does not take this setting into account when changes are pushed to the repo. I don't want to perform a rollout when making changes only the iOS app, for example.

   Automatic rollouts should only perform the rollout (or be able to be configured to) only when the specified app directory contains changes. Path matching is a… more

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  App Hosting  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Persistent Memory & "Do Not Modify" Toggles to Protect Existing Code

   As a project becomes more developed, I've noticed that the Gemini assistant in Firebase Studio sometimes starts modifying templates, forms, and functions that were already working perfectly.

   To prevent this, I currently have to prepend a strict warning to every single prompt: "Proceed with extreme caution. Do not change the visual design, menus, structure, or any logic unrelated to this specific query: [my actual prompt]". While this workaround is effective and usually results in better code, it is tedious to write every time.

   My Suggestion: It would be incredibly helpful to implement a "Context Memory" feature with a checklist or on/off toggles. This would allow developers to explicitly mark certain functions, files, or UI layouts as "Locked/Remember" (Gemini must preserve them) and others as "Modifiable". This way, we wouldn't have to constantly use defensive prompting to protect the code that is already finished and working.

   As a project becomes more developed, I've noticed that the Gemini assistant in Firebase Studio sometimes starts modifying templates, forms, and functions that were already working perfectly.

   To prevent this, I currently have to prepend a strict warning to every single prompt: "Proceed with extreme caution. Do not change the visual design, menus, structure, or any logic unrelated to this specific query: [my actual prompt]". While this workaround is effective and usually results in better code, it is tedious to write every time.

   My Suggestion: It would be incredibly helpful to implement a "Context Memory" feature with a checklist or… more

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Agent Skills  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Firebase Protype Needs to be more trained on Firebase products like firestore Rules and Genkit

   I have built approx 3-4 apps and each time I had to switch from firebase products to third party providers because google App protype itself faces issues Integrating its own products but works great with third party products.

   Genkit most of the times fails if asked a complecated integration
   Simply imposible to work with Firestore
   Firaebase AUTHentication using Firebase Prototype is like work with AI for a weeek to solve, easier to switch next AUTH or other platforms

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Add command to check Firebase CLI authentication status without triggering reauth

   Currently, the Firebase CLI does not provide a way to proactively check whether the user’s authentication state is still valid. Authentication validity is only discovered when running a command that requires auth, at which point the CLI may fail and instruct the user to run firebase login --reauth.

   This makes it difficult to:
   • Detect impending or current auth expiration ahead of time
   • Build scripts or tooling that can validate environment readiness
   • Provide a better UX in local development workflows
   • Perform lightweight “health checks” without risking mid-command failure

   Problem
   There is no supported command such as:
   • firebase login:status
   • firebase auth:check
   • or similar

   The only way to determine auth validity today is to run a real command (e.g. firebase projects:list) and handle a failure, which is reactive and indirect.

   Proposed Solution
   Introduce a command that checks CLI authentication status without performing a project operation, for example:

   firebase login:status

   Possible behaviors:
   • Exit code 0 if credentials are present and refreshable
   • Exit code 1 if credentials are missing, expired, or require reauthentication
   • Optional human-readable output, e.g.:
   • “Authenticated (user@example.com)”
   • “Authentication expired — run firebase login --reauth”

   Optional enhancements:
   • --json output for scripting
   • Indicate auth method (user OAuth vs service account)
   • Indicate whether silent refresh succeeded

   Why this would be useful
   • Improves developer experience
   • Enables deterministic preflight checks in scripts
   • Reduces surprise failures during deploys
   • Aligns with similar tooling (gcloud auth list, aws sts get-caller-identity, etc.)

   Scope clarification
   This request is specifically about Firebase CLI authentication, not Firebase Auth sessions or Admin SDK behavior.

   Alternative workaround (current)
   Running a harmless command like firebase projects:list is currently the only way to infer auth state, but this is indirect and not ideal.

   Currently, the Firebase CLI does not provide a way to proactively check whether the user’s authentication state is still valid. Authentication validity is only discovered when running a command that requires auth, at which point the CLI may fail and instruct the user to run firebase login --reauth.

   This makes it difficult to:
   • Detect impending or current auth expiration ahead of time
   • Build scripts or tooling that can validate environment readiness
   • Provide a better UX in local development workflows
   • Perform lightweight “health checks” without risking mid-command failure

   Problem
   There is no supported command such as:
   •… more

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firebase CLI  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Update privacy policy part of PNV SDK

   About the new post on the Google Groups of PNV SDK:
   https://groups.google.com/g/firebase-pnv-announce/c/44tx7z_Pc8w/m/99O0BfW4AAAJ?utm_medium=email&utm_source=footer
   https://firebase.google.com/docs/phone-number-verification/android/get-started

   "You must have a publicly accessible privacy policy to complete OAuth brand verification. You can use Firebase Hosting to create a basic web app to host your test privacy policy."

   It mentions to have privacy policy related to this, but doesn't mention what to put there.
   I tried to contact Firebase support, and they said to me to request it here, with these details:

   "
   It should clearly say, in simple words:
   that your app reads the user’s phone number,
   why it does this,
   whether the number leaves the device or is sent to any server,
   and how users can contact you.
   "

   About the new post on the Google Groups of PNV SDK:
   https://groups.google.com/g/firebase-pnv-announce/c/44tx7z_Pc8w/m/99O0BfW4AAAJ?utm_medium=email&utm_source=footer
   https://firebase.google.com/docs/phone-number-verification/android/get-started

   "You must have a publicly accessible privacy policy to complete OAuth brand verification. You can use Firebase Hosting to create a basic web app to host your test privacy policy."

   It mentions to have privacy policy related to this, but doesn't mention what to put there.
   I tried to contact Firebase support, and they said to me to request it here, with these details:

   "
   It should clearly say, in simple words:
   that your app reads the user’s phone number,
   why it does this,
   whether the number… more

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Phone Number Verification  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Support to configure non-blocking tool use in Firebase AI Logic?

   Async function call (https://ai.google.dev/gemini-api/docs/live-tools#async-function-calling) is helpful in many scenario, but Firebase AI Logic doesn't allow to configure it. Please support

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firebase AI Logic  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Restrict Firebase App Invitations to Only the Intended Google Account (Prevent Forwarded Email Access)

   Hi all,

   We send Firebase app invitations only to our company domain emails, but the invitation email can be forwarded and accepted by a personal Gmail account, which creates a security concern.

   Is there a way to:

   Restrict invitation acceptance to only the Google account that received the email

   Or limit access to company-domain Google accounts only

   Prevent forwarded invitations from granting access to unauthorized users

   Any best practices or Firebase-supported solutions would be appreciated. Thanks!

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  App Distribution  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Improve firestore rules debug info

   Improve firestore rules debug info:
   2 features will really improve the debugging of firestore rules:
   - Add a "label" parameter to the debug() function to identify the result in the debug log file of the emulator. Right now, only the value is printed, it is very confusing when you have several debug calls...
   - Improve the error message returned to the client so we can understand the permission denied. Right now the message contains very little information and it is not helpful a all..,

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firestore  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. مميزات
    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Firebase Studio  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. unsefe content ?

    how to manage ?

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Github auto feed to firebase conle backend

    After deployment in firebase studio, app hosting require backend to rollout. However GitHub has to feed firebase console the code in repo. That request is now done manually and can miss critical steps that lead to frustration

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Une fonction pour directement télécharger
    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. I would like to import the source code of an existing GitHub repository from Firebase Studio Prototyper Gemini so that I can modify it. This

    I would like to import the source code of an existing GitHub repository from Firebase Studio Prototyper Gemini so that I can modify it. This feature is very useful, so please consider it.

    As a specific example, I would like to import the source code of the following GitHub repository so that I can modify it from Firebase Studio Prototyper Gemini.
    https://github.com/okamoto53515606/homepage

    PS)
    Until the above feature is available, I plan to proceed as follows:
    1. Instruct Firebase Studio Prototyper to create a dummy app (with minimal functionality).
    2. Press the "Publish" button to create app hosting for the dummy app (with minimal functionality).
    3. Open a terminal in Firebase Studio.
    4. In the Firebase Studio terminal, download and unzip the tar.gz file from GitHub.
    5. Run npm install again in the Firebase Studio terminal.
    6. Run "Restart" from Firebase Studio to rebuild your Firebase Studio development environment.
    7. Have prototyper gemini review the contents of the new docs folder and understand the structure of your app.
    8. Ask prototyper gemini to make any corrections.

    I would like to import the source code of an existing GitHub repository from Firebase Studio Prototyper Gemini so that I can modify it. This feature is very useful, so please consider it.

    As a specific example, I would like to import the source code of the following GitHub repository so that I can modify it from Firebase Studio Prototyper Gemini.
    https://github.com/okamoto53515606/homepage

    PS)
    Until the above feature is available, I plan to proceed as follows:
    1. Instruct Firebase Studio Prototyper to create a dummy app (with minimal functionality).
    2. Press the "Publish" button to create app hosting for the dummy… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Please communicate the following information to Gemini, the prototyper, in advance. Please also provide Gemini with a development preview UR

    Please communicate the following information to the prototyper, Gemini, in advance. Please also provide the development preview URL to the prototyper, Gemini, in advance.

    Firebase Studio Development Environment Workflow and Knowledge

    This document summarizes the knowledge required for AI development partners (App Prototypers) to understand the characteristics of this development environment and work smoothly with users.

    1. Terminal and Command Execution

    Available Command Line Tools

    The following main commands are available in the terminal of this environment.

    • git: Version control
    • gcloud: Google Cloud resource operations
    • firebase: Firebase project operations

    How to Execute Commands

    In dialogue with the user, the AI ​​presents commands to be executed.

    • `bash Markdown: When commands are presented in this format, an execute button (▶) appears in the user interface. The user can execute the command simply by pressing this button.
    • AI Cannot Execute Directly: The AI ​​itself does not have the permission to execute commands directly. The basic workflow is a collaborative one: the user executes a command, communicates the results to the AI, and then proceeds to the next step.

    2. Deployment and URL

    Deployment Flow

    • Pushing to Production: By pressing the "Publish" button in the upper right corner of the UI, the developed application is deployed to Firebase App Hosting and pushed to the production environment.

    Environment URL

    • AI Doesn't Know URLs: By default, the AI ​​does not know the development preview URL or the production URL.
    • User-Provided Information: The user can run a command such as firebase apphosting:backends:list and provide the AI ​​with the URL identified from the command. The AI ​​can then remember that information as context and use it for future development (such as CORS configuration).
    • Example of URL confirmed:
    • Preview URL: https://9000-firebase-studio-*.cloudworkstations.dev/
    • Production URL: URL confirmed using the firebase apphosting:backends:list command

    3. Infrastructure Configuration Workflow Example

    In addition to code, Firebase and Google Cloud infrastructure configuration can also be performed in conjunction with AI.

    1. User specifies the goal: (Example: "I want to securely set the service account's private key as an environment variable.")
    2. AI plans and suggests commands:
    3. Check the account with gcloud iam service-accounts list.
    4. Use gcloud iam service-accounts keys create - ... to output the key to standard output without saving it to a file.
    5. User executes command: Executes the suggested command and optionally provides feedback to the AI ​​with the results.
    6. Continuous Operation Through Collaboration: The AI ​​suggests the next step based on feedback.

    This workflow allows users unfamiliar with commands to safely and accurately configure infrastructure with the assistance of the AI.

    4. Version Control (Git) Workflow Example

    How Auto-Commit Works

    The AI ​​suggests file changes, and once they're applied, the changes are automatically committed to Git. The commit message contains the AI's instructions (user prompts).

    Reverting to a Specific Commit

    You can also revert a project to a specific past state through interaction with the AI.

    1. AI suggests a history check command: The AI ​​suggests a command such as git log --oneline.
    2. User executes a command and shares the results: The user executes a command and shares the displayed commit history with the AI.
    3. User specifies the commit to revert to: The user identifies the commit in the history to which they want to revert.
    4. AI suggests a rollback command: The AI ​​suggests a command to return to a specified state, such as git reset --hard <commit ID>.
    5. User executes a command: The user executes the command, reverting the project's files to a previous version.

    I would like to see the prototyper gemini be able to execute terminal commands directly.
    I would appreciate your consideration.

    Please communicate the following information to the prototyper, Gemini, in advance. Please also provide the development preview URL to the prototyper, Gemini, in advance.

    Firebase Studio Development Environment Workflow and Knowledge

    This document summarizes the knowledge required for AI development partners (App Prototypers) to understand the characteristics of this development environment and work smoothly with users.

    1. Terminal and Command Execution

    Available Command Line Tools

    The following main commands are available in the terminal of this environment.

    • git: Version control
    • gcloud: Google Cloud resource operations
    • firebase: Firebase project operations

    How to Execute Commands

    In dialogue with the… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Put the collection name in the beginning of the page title of the Firebase web console

    Right now it goes "Project Name - Database - Data - Firebase console" which can get confusing when i have multiple tabs open.

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firestore  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Project

    تحويل جيمني الي اداة امر سيادي . لقد نجحت في دمجها مع موقع حكومي فرنسي و جعلها فتح شركة و مراجعة الأخطاء خلال ساعة واحدة .... لا أعرف كيف احصل علي مكافئة و لمن ينبغي ان اقدم المشروع
    
    Converting Gemini into a sovereign command tool. I successfully integrated it with a French government website, enabling company setup and error review within one hour. I don't know how to get a reward or who to submit the project to.

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Gemini in Firebase  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Support Request – Firebase Studio Preview & Environment Variables Subject: Firebase Studio Preview does not allow setting custom environmen

    Support Request – Firebase Studio Preview & Environment Variables

    Subject: Firebase Studio Preview does not allow setting custom environment variables (Admin SDK / Service Account issue)

    Hello Firebase Studio Support Team,

    I’m using Firebase Studio (Cloud Workstations) with a Next.js (App Router, Server Actions) project that uses Firebase Admin SDK to write to Firestore.

    I’m encountering a blocking issue with environment variable management in Firebase Studio Preview.

    🔍 Problem Description

    My application requires a service account to initialize Firebase Admin SDK.
    Normally this is done via an environment variable such as:

    FIREBASESERVICEACCOUNT_KEY=<base64-encoded service account JSON>

    However, in Firebase Studio Preview:

    There is no UI or documented way to define custom environment variables or secrets

    Preview automatically injects GOOGLEAPPLICATIONCREDENTIALS

    This causes Admin SDK to fall back to Application Default Credentials (ADC)

    ADC fails in Preview with errors like:

    Getting metadata from plugin failed
    Could not refresh access token (HTTP 500)

    Even when using dotenv or runtime logic, this cannot be overridden because the env is injected before the Node process starts.

    📜 What I Tried

    Removing GOOGLEAPPLICATIONCREDENTIALS from .env

    Forcing credentials in code (cert(serviceAccount))

    Using dotenv

    Using Firebase CLI (functions:config:set)

    Restarting / rebuilding Preview

    Searching for Preview env / secrets configuration

    None of these allow injecting a custom env variable into the Preview runtime.

    ❓ Questions

    Is it currently supported to define custom environment variables or secrets for Firebase Studio Preview?

    If yes, where is this documented or configured?

    If not, is there a recommended workflow for projects using:

    Next.js Server Actions

    Firebase Admin SDK

    Firestore writes

    Is Preview intended only as a frontend-only viewer, not a backend runtime?

    🎯 Impact

    This limitation prevents:

    Testing Admin SDK logic

    Firestore write operations

    Any backend logic that depends on secure credentials

    At the moment, the only working solution is local development or Cloud Run/App Hosting, which defeats the purpose of Preview for full-stack apps.

    Thank you for your help.
    Clarification or documentation on this would be very valuable.

    Best regards,
    Murat

    Support Request – Firebase Studio Preview & Environment Variables

    Subject: Firebase Studio Preview does not allow setting custom environment variables (Admin SDK / Service Account issue)

    Hello Firebase Studio Support Team,

    I’m using Firebase Studio (Cloud Workstations) with a Next.js (App Router, Server Actions) project that uses Firebase Admin SDK to write to Firestore.

    I’m encountering a blocking issue with environment variable management in Firebase Studio Preview.

    🔍 Problem Description

    My application requires a service account to initialize Firebase Admin SDK.
    Normally this is done via an environment variable such as:

    FIREBASESERVICEACCOUNT_KEY=<base64-encoded service account JSON>

    However, in Firebase… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Firebase CLI  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. NEW ALL-ROUNDER AI CREATION self by FIREBASE,Android,Replit etc . ALL cooperated

    by FIREBASE,Android,Replit etc . and then make that AI Go its Developments on its own and on and so on ....make fire studio do everything to make an AI that independent and strong enough tdo everything for their own developments?

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Add a CLI flag for hosting project previous release count option

    I have an ecommerce SAAS company where each client/tenant website is hosted on Firebase Hosting. We have over 80 websites hosted across six Firebase projects.

    We create each new site using the Firebase CLI:

    firebase hosting:sites:create [options] <siteId>

    The only options for this command are:

    --app <appId> specify an existing Firebase Web App ID
    -h, --help display help for command

    I'd like to request an additional option to set the "previous releases to keep", aka "previous release count".

    After I create a new site, I have to deploy the new website to Firebase hosting before I can set the previous release count on the Firebase Hosting website. The website won't let me set the release count before deploying my first release.

    If I can set this previous release count when creating the site, then I don't have to wait until after I complete these two required steps (plus remember to do it).

    If I forget to set the previous release count, then I'll end up with too many previous releases that I'm paying for that I'll never use.

    Basically, this would eliminate one of the many little annoying steps I need to do manually when launching a new tenant website.

    I have an ecommerce SAAS company where each client/tenant website is hosted on Firebase Hosting. We have over 80 websites hosted across six Firebase projects.

    We create each new site using the Firebase CLI:

    firebase hosting:sites:create [options] <siteId>

    The only options for this command are:

    --app <appId> specify an existing Firebase Web App ID
    -h, --help display help for command

    I'd like to request an additional option to set the "previous releases to keep", aka "previous release count".

    After I create a new site, I have to deploy the new website to Firebase hosting before I can set the previous… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Hosting  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating