1243 results found

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

   3 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

2. Add copy source code to Firestore Query Builder

   It'd be great if Query Builder had a way to translate whatever query you're running into a code snippet. Something like Firestore's docs where you can select a language and then copy the code.

   3 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

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

   3 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

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

   3 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

5. Make App Hosting available in Doha and Dammam region (me-central)

   Deployment of apps in the firebase project has limited region options and middle east regions are not among them.

   Allowing the deployment of backend in these region will enable us to lower latency and use the cool firebase dashboards to manage the backend without having to go to GCP console often.

   3 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

6. Access user agent of the client

   App hosting replaces user agent header of the client, with "Google"
   I need to access user agent to modify responses according to user's operating system.

   3 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

7. Support Multiple Data Connect Services in Emulator Suite (or Allow Hybrid Cloud Fallback)

   Currently, the Firebase Emulator Suite allows running only a single Data Connect service instance locally. For projects utilizing a microservices architecture with multiple isolated Data Connect services, this creates a significant blocking issue during development.

   Primary Feature Request: Multi-Service Emulation - Please update the Emulator Suite to support running multiple Data Connect services simultaneously.

   Alternative / Interim Solution: Hybrid Cloud Fallback - If full multi-service emulation is technically complex to implement immediately, please introduce a "Hybrid" mode as an alternative.

   Current Behavior: When the emulator is running, all calls to Data Connect are forced to look locally. If a specific service isn't emulated, the call fails, even if a live version exists.

   Proposed Behavior: Allow an opt-in flag (e.g., --allow-cloud-fallback) that permits the SDK to connect to live/deployed Cloud instances for any Data Connect service not currently running in the emulator.

   Why this is critical: Support has confirmed the current "walled garden" approach is intended to prevent accidental costs. However, without multi-service support, this leaves developers in a deadlock: we cannot emulate our full stack locally, and we cannot mix local emulation with cloud resources. We are effectively forced to test entirely in production.

   Currently, the Firebase Emulator Suite allows running only a single Data Connect service instance locally. For projects utilizing a microservices architecture with multiple isolated Data Connect services, this creates a significant blocking issue during development.

   Primary Feature Request: Multi-Service Emulation - Please update the Emulator Suite to support running multiple Data Connect services simultaneously.

   Alternative / Interim Solution: Hybrid Cloud Fallback - If full multi-service emulation is technically complex to implement immediately, please introduce a "Hybrid" mode as an alternative.

   Current Behavior: When the emulator is running, all calls to Data Connect are forced to look locally. If a specific… more

   3 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

8. Multiple Roles

   As of now, firebase only supports single role. We want multiple role support. Example, Employer, Employee, Admin etc.

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

9. firebase MCP and gemini-cli integrated

   I am using the gemini-cli + firebase MCP and my build fails. Gemini-cli asks me to copy-paste the logs from firebase console. Could all the troubleshooting be integrated please? thanks

   3 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 & MCP Server  ·  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. Query filter for Nested Arrays

    Adding a query method to filter the nested arrays in the firestore collection would be more scalable to get data faster. This would avoid the unnecessary looping of the data for finding a particular field, which are already stored in an array.

    This feature would make the firestore to perform extraordinarily in retreiving the data.

    3 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

11. Voice over

    I can give my voice over to control

    3 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  ·  Other  ·  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. غایربیس
    3 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  ·  Cloud Storage for 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

13. Request to Enable Firebase Phone Authentication in Somalia.

    I am writing to request that Firebase Phone Authentication be enabled for Somalia. Over the past two years, there has been significant growth in the use of Flutter and Firebase to develop mobile apps in Somalia. However, the lack of phone authentication support in this region has created a barrier for developers.

    Phone authentication is essential for securing user accounts and is widely used in regions like ours. Enabling this feature in Somalia would greatly benefit both developers and users by improving accessibility and security.

    I kindly ask you to consider this request and enable Firebase Phone Authentication for Somalia.

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

14. Add support to document Why change was published

    There should be an optional note field when publishing changes to explain why these changes to the config were published. Moreover, it would be great to have a simple history view of what changes were published with notes.

    Right now, we can only see WHEN and WHO published the latest changes, but we don't know WHY

    3 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  ·  Remote Config  ·  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. Fallback to Gemma when browser based models are not available in the Hybrid SDK

    When using Firebase AI Logic for hybrid inference, I want to be able to support users that are using non-Chrome browsers to still be able to run inference. In this case, give me an option to download Gemma and run inference for my users running a non-Chrome browser. This preserves the PREFERONDEVICE or ONLYONDEVICE flags I have set and allows my users to continue to benefit the rewards of my app without needing to download a new browser.

    3 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

16. parametre

    je veut ma cle api

    3 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 console  ·  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. Clear Gemini History Not Working

    Sorry, I hit a snag. Please try again shortly or modify your prompt.
    [GoogleGenerativeAI Error]: Error fetching from https://monospace-pa.googleapis.com/v1/models/gemini-2.5-pro:streamGenerateContent?alt=sse: [400 Bad Request] The input token count (9521395) exceeds the maximum number of tokens allowed (1048576).

    When you try to clear the history on Gemini, this doesn't work. This needs to be fixed, otherwise it prevents vibe coding, etc.

    3 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. A M-pesa app but cheaper on transactions

    Cheapest app on transactions

    3 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

19. Links

    Reliable

    3 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  ·  Extensions  ·  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. Phone Authentication

    Estimado equipo de Firebase,

    Estoy desarrollando una aplicación móvil en Flutter que utiliza Firebase Authentication con verificación por teléfono. El proyecto está orientado a usuarios en Nicaragua (+505), pero al intentar enviar el código SMS, recibo el siguiente mensaje de error:

    "SMS unable to be sent until this region enabled by the app developer."

    Ya he habilitado la autenticación por teléfono en la consola de Firebase, configurado números de prueba, y activado la autenticación multifactor por SMS. Sin embargo, el envío de SMS reales sigue bloqueado para esta región.

    Solicito amablemente que se habilite el soporte para envío de SMS en Nicaragua para mi proyecto.

    Nombre del proyecto: PEDIDOS_GASEOSAS
    
    ID del proyecto: pedidos-gaseosas
    
    Correo del desarrollador: fernandojoserojas0@gmail.com

    Agradezco mucho su atención y quedo atento a cualquier información adicional que necesiten para procesar esta solicitud.

    Saludos cordiales,
    
    Fernando Rojas

    Estimado equipo de Firebase,

    Estoy desarrollando una aplicación móvil en Flutter que utiliza Firebase Authentication con verificación por teléfono. El proyecto está orientado a usuarios en Nicaragua (+505), pero al intentar enviar el código SMS, recibo el siguiente mensaje de error:

    "SMS unable to be sent until this region enabled by the app developer."

    Ya he habilitado la autenticación por teléfono en la consola de Firebase, configurado números de prueba, y activado la autenticación multifactor por SMS. Sin embargo, el envío de SMS reales sigue bloqueado para esta región.

    Solicito amablemente que se habilite el soporte para envío de SMS… more

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