1234 results found

1. Support 2nd generation (v2) Firebase Functions in Firebase Extensions

   2nd generation Functions are better in every way and are recommended for almost all new Functions, but can't be used in Extensions (for most trigger types).

   https://firebase.google.com/docs/extensions/publishers/functions

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

2. API support for insertMany and updateMany

   Currently Data Connect insertMany and updateMany mutations do not support being passed multiple records via the SDK. Figure out a way to enable this so we can insert multiple rows in the same “@transaction” via the API.

   42 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

3. Punycode domain support ✌🏻

   The hosting product support punycode domain but App Hosting doesn't which is kind of odd. Please bring App Hosting to the same domain support parity with the Hosting product. Thank you!

   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

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

5. Firebase logIn with Phone Number

   Comprobar que Firebase Authentication with phone funcione con todas las operadoras del país junto con recaptcha y appcheck

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

6. Fastlane - Get automatically app key from google-services.json

   All Android application that included Firebase have mandatory this file : google-services.json

   When we want automatize delivery with fastlane on Firebase, we need to provide many informations on the lane such like "app", "servicecredentialsfile",...

   In fact, many Android projects has one or more build flavors and the delivery can be harder with the configuration on which target we want to deploy.

   We need to store many sensitive informations like key on the env file.
   We not push this file on the repository and it's not a good practice to have them has CI variables.

   The purpose of this feature request is to automatize the retrieve of app key from google-services.json.
   For this, we just need few informations on env / CI file :
   - location of google-services.json (that can be split in an other feature) *1;
   - package name declared on env / CI file.

   Only with your package name, you can retrieve (or not) your app key from google-services.json.
   This is a snippet of code for make this one :

   Parse the JSON content

   jsondata = JSON.parse(filecontent)

   Search for the appid corresponding to the packagename

   appid = ""
   jsondata["client"].each do |client|
   if client["clientinfo"]["androidclientinfo"]["package_name"] == targetpackagename
   appid = client["clientinfo"]["mobilesdkapp_id"]
   break
   end
   end

   All Android application that included Firebase have mandatory this file : google-services.json

   When we want automatize delivery with fastlane on Firebase, we need to provide many informations on the lane such like "app", "servicecredentialsfile",...

   In fact, many Android projects has one or more build flavors and the delivery can be harder with the configuration on which target we want to deploy.

   We need to store many sensitive informations like key on the env file.
   We not push this file on the repository and it's not a good practice to have them has CI variables.

   The purpose of this… more

   16 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

7. More regions app hosting

   Please do more regions like Australia for app hosting as some businesses have strict region requirements

   18 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

   4 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

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

9. Enable Firebase services for Syrians

   Syrian developers deserve greater support from leading global companies. I kindly ask you to enable Firebase services for people in Syria, so we can create meaningful applications and contribute to rebuilding our country.

   This request aligns with recent U.S. actions to ease restrictions and remove Syria from certain sanctions lists.

   Thank you for your understanding and for recognizing our hopes for a better future.

   7 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

10. Integrate Firebase product and developer notifications with Google Cloud Essential Contacts

    Larger customers often use Google Cloud Essential Contacts for ensuring critical notifications get to the right people. Currently Firebase product and developer communications seem to go out via email to named user accounts where the customer has no control who this goes to and it may miss its intended audience.

    It would be great if FIrebase notifications could be integrated with Google Cloud Essential Contacts to give customers more control over where critical notifications go to and to make this consistent with other Google Cloud services.

    https://docs.cloud.google.com/resource-manager/docs/managing-notification-contacts

    Thank you!

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

11. 122004
    1 vote

    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  ·  Edit…  ·  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. Update iphone 16 and iphone 17 mapping for device information

    Now for iphone 16 and iphone 17, analytics only detect it as iphone, marketing name is null.
    It is hard to analyze user's device distribution.

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

13. Custom domain

    Custom Dom should instantly hook on the app hosting

    4 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

14. Crashlytics alerts do not work if Firebase permissions have been granted from Google Cloud IAM roles

    Make Crashlytics alerts work with permissions granted from Google Cloud IAM roles rather than from the Firebase console's own permissions

    12 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

    3 comments  ·  Crashlytics  ·  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. Cloud Firestore Datasource

    Support Cloud Firestore as a datasource for Data Connect in addition to Cloud SQL. Support data model mapping (e.g. @collection) and querying via GraphQL

    191 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

    11 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

16. Option to plan first, approve/deny plan, before executing

    An option for Gemini to offer a plan. An approve/deny plan option for the user first before executing. Right now, it just does it without your consent. We know AI is better than us, but we need it to show us the plan if it makes sense for the overall business.

    14 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

    3 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

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

18. Update the knowledgebase of Gemini to stop using 1.5 versions

    Every time It uses or create a google cloud function it uses 1.5 versions. Even if I tell it specifically not to use and use a 2.5 version it keep using it. Please update the knowledge of the tool to avoid connecting to outdated apis.

    7 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

19. I need a breakthrough

    Do something better in future before that I need to learn something about this 😞

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

20. Offline Support

    Allow data to be cached and accessible offline. Offline data may have limited query and write capabilities compared to online data

    180 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

    10 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