1221 results found

1. 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

2. 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

3. 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

4. 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

5. firestore pipeline as rulev3/transformation

   Additional to just a condition for allow read/write. I think firestore rule should be replaced with transform function. It should utilize pipeline operation and return document to read/write. So that it could force add field or change logic to generate some field on every document without redeploy client

   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

6. 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

7. 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

8. 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

9. 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

10. Don't require Github integration for App Hosting Backends

    I'm using Cloud Build and deploying to App Hosting using the CLI. We don't have an option when running firebase apphosting:backends:create to not connect a github repo, even though with the CLI deploy option the integration is not necessary. We're able to script setup of Hosting backends, but the github connection requirement in App Hosting disables our ability to script setup of our App Hosting Backends.

    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

11. Create documentation for the Docker image requirements for an App Hosting app deployed using Terraform

    Add documentation listing the Docker image requirements for an App Hosting app deployed using Terraform. Include sample Dockerfiles for Next and Angular apps.

    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

12. Data Connect should be serverless through and through.

    One of the great things about firebase is that it didn't burden you of your design decisions and let you pay for resources when you needed it. Serverless is one of the main selling point of firebase, you can see its footprints on firestore, realtimedb, and firebase functions.

    Seeing the need to instantiate a DB instance when getting started with data connect was so disappointing for me because I thought it was a step in the wrong direction.

    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  ·  SQL Connect (Data Connect)  ·  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. AI agent

    The AI agent testing is very basic. It cannot access external urls . It does n ot let me upload files like (pdf,xml etc) to test my application. Hope it gets upgraded in the future

    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  ·  Test Lab  ·  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. reference Bazel label paths for dependencies, possibly from a BUILD file or workspace definition.

    UUID Group Name

    74fd13fa90f483537a1866505fae79762f121b96 Empty Group = NoOne
    c70777b3b2b15fd1baf444b2b6e968d75e3a405c chromeos-committers
    global:Anonymous-Users Anonymous Users
    global:Registered-Users Registered Users

    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

15. Here is a **strong, complete, production-ready prompt** you can paste into any advanced LLM (GPT/Claude/LLaMA) to generate a **full tokenisa
    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

16. Support for Proper 404 Status Codes and Multiple 404 Pages Based on URL Patterns on Firebase Hosting

    Currently, when using a custom 404 page (e.g., 404.html), Firebase Hosting always responds with a 200 status code, even when the page is served via a rewrite rule.
    This differs from behavior on traditional servers (e.g., Nginx with the internal directive), where the server can correctly return a 404 while still serving a custom error page.

    Why this matters:
    - Proper HTTP status codes are essential for SEO.
    - Search engines may incorrectly index 404 pages if they return 200.
    - Client applications and monitoring tools rely on correct status codes.

    Additionally, In many multilingual or multi-section sites, different parts of a website require different 404 pages.
    At the moment, the only workaround is to use rewrite rules, such as:

    {
      "rewrites": [
        { "source": "/es/**", "destination": "/es/404.html" }
      ]
    }
    

    However, this still returns 200 instead of 404, which causes the same issue as above.

    Requested enhancement:
    - Allow developers to define multiple 404 handlers depending on URL patterns (e.g. /es/** → /es/404.html, /fr/** → /fr/404.html)
    - Ensure each of these handlers can return a real 404 status code

    These two capabilities would significantly improve:
    - SEO accuracy
    - Error analytics
    - User experience for multilingual or multi-section websites
    - Parity with traditional server behavior

    Thank you for considering these enhancements!

    Currently, when using a custom 404 page (e.g., 404.html), Firebase Hosting always responds with a 200 status code, even when the page is served via a rewrite rule.
    This differs from behavior on traditional servers (e.g., Nginx with the internal directive), where the server can correctly return a 404 while still serving a custom error page.

    Why this matters:
    - Proper HTTP status codes are essential for SEO.
    - Search engines may incorrectly index 404 pages if they return 200.
    - Client applications and monitoring tools rely on correct status codes.

    Additionally, In many multilingual or multi-section sites, different parts… 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

17. meraestore

    Aap store Play store Google service Google product

    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  ·  Analytics  ·  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. BUILD

    LOVE

    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  ·  Authentication  ·  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. BUILDING

    LETS BUILD

    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

20. make a software that acts as library for books

    my idea is to create an android$ios software app that will be holding books for leading or which will act as a library

    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  ·  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