1217 results found

1. remove recaptcha firebase phone auth flutter

   remove recaptcha firebase phone auth flutter

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

2. Fee/Pricing

   Functions is behind paywall, (it is still free for some limit in Blaze plan), but IF i upgrade to Blaze, then Cloud Storage, Hosting etc starts to charge right away, even in free plan they have free limits but once switched to Blaze it starts to charge. So to get free Functions, i have to pay cloud storage and hosting and more.

   For any playground project that is not gonna hit market or earn money, how i am supposed to try/learn functions? This forces me to move away from platform

   8 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

   2 comments  ·  Cloud Functions 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

3. Gemini Panel UI Improvements

   The Gemini side panel has an awkward UI design which takes up way too much screen space. When I click to open it shouldn't stay open because then I have to click the X to close and click again to reopen which I find annoying. There should be an option button to allow for auto open when the mouse moves to the edge of window and auto close when the mouse exits the Gemini panel.

   Also if you choose to dock to right there's so much wasted space with duplicate menu buttons. (Alerts, Chat, Help) appears on both the left and right side of the panel. Only one of them is necessary the other should be removed to allow for a wider panel.

   Additionally anchoring the panel to top or bottom is essentially the same thing as maximize because it takes up 95% of the screen. Those options should resize the Gemini panel to be something like 25% of the screen instead.

   The Gemini side panel has an awkward UI design which takes up way too much screen space. When I click to open it shouldn't stay open because then I have to click the X to close and click again to reopen which I find annoying. There should be an option button to allow for auto open when the mouse moves to the edge of window and auto close when the mouse exits the Gemini panel.

   Also if you choose to dock to right there's so much wasted space with duplicate menu buttons. (Alerts, Chat, Help) appears on both the left… 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  ·  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

4. Using Genkit embedders (including from e.g. genkitx-openai-plugin)

   Instead of only being able to select embedding models from Vertex AI (e.g. Gecko), it'd be great to be able to pass in any embedder imported from Genkit plugins like genkitx-openai-plugin or genkitx-cohere

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

5. Include User Online Feature

   Just like we have user logged in etc, can we have isUserOnline?

   5 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

6. Manual reloading of firebase functions in emulator

   I'm suggesting this feature of nodemon:

   https://github.com/remy/nodemon?tab=readme-ov-file#manual-restarting

   Sometimes when inner dependencies changes, firebase emulator don't detect changes. So whenever I make a change in my large project, I have to always shutdown firebase emulator and restart it.

   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

   0 comments  ·  Emulators  ·  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. Sort screen rendering traces by impact

   Currently, the screen rendering trace tool displays a list of issues, but with many items, it becomes overwhelming to sift through and identify the most significant problems.

   Specific Challenges

   • Volume of Data: With many items in the trace list, manually identifying high-impact issues is impractical.
   • Lack of Prioritization: The current list does not prioritize issues based on their impact, making it difficult to focus on what matters most.
   • Efficiency: Developers need a way to quickly pinpoint and address the most significant rendering issues to improve application performance.

   Proposed Solution

   Introduce an "Impact Sort" option in the screen rendering trace tool. This sorting method will prioritize issues based on the formula: frozen frames * number of samples. By calculating the total frozen frames a given issue causes across the installed base, this option will provide a clear insight into which issues are most detrimental to performance.

   Currently, the screen rendering trace tool displays a list of issues, but with many items, it becomes overwhelming to sift through and identify the most significant problems.

   Specific Challenges

   • Volume of Data: With many items in the trace list, manually identifying high-impact issues is impractical.
   • Lack of Prioritization: The current list does not prioritize issues based on their impact, making it difficult to focus on what matters most.
   • Efficiency: Developers need a way to quickly pinpoint and address the most significant rendering issues to improve application performance.

   Proposed Solution

   Introduce an "Impact Sort" option in the screen rendering trace tool.… more

   5 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  ·  Performance Monitoring  ·  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 .guru domain extension

   I have a domain with the extension: .guru,
   but when I enter the domain to firebase for authentication, it doesn;t accept it as a valid domain name! HELP PLEASE!

   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

   1 comment  ·  Authentication  ·  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

9. useEmulator should return False if emulator is not running

   I am currently using firebase/firestore from react native. Currently

   import { firebase } from "@react-native-firebase/firestore";

   const rc = firebase.firestore().useEmulator("192.168.1.130", 8080);

   Ideally I would like rc=False if the emulator is not up.

   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  ·  Emulators  ·  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. Cloud Spanner Datasource

    Support Cloud Spanner as a datasource for Data Connect in addition to Cloud SQL via Cloud Spanner's PostgreSQL compatibility layer.

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

11. Allow a function to set the headers of a hosting endpoint dynamically

    Right now there does not seem to be a way to dynamically set the headers of a hosting response using a function.

    Among other things, this makes it impossible to use a nonce.

    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  ·  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. Robo de mis billetera google

    Robo de datos personales

    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 Check  ·  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. Allow cross-project restoring of Firestore databases

    When working with Firestore databases, you may want to restore an entire database for testing in your stage project.

    However, currently, you can only restore in the same project

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

14. Transactions should allow exponential backoff retries like pub sub

    Transactions allow passing an options object with maxRetries, but all retries are immediate. If there are many other functions writing the same document, transactions will fail after all retries (lock will time out). Maybe a better strategy would be to delay with exponential backoff like pub sub does.

    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

    2 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. Tell people that mixing V1 and V2 config files in the same project will create a port and container error.

    Tell people that mixing V1 and V2 config files in the same project (note: even outside the gen2 function) will create a port and container error. Right now you don't mention in the docs or anywhere that having ANY function.config files in a project with a gen 2 function will cause a deploy error that says a container is broken and the port is unreachable. This error is misleading. It will also show the gen 2 function in the console as "unknown trigger" which also is misleading.

    In all your documentation you say you can have gen1 and gen2 functions in the same project, but you don't warn people that using function.config configs OUTSIDE of the gen2 functions will still kill the deploy. This makes mixing gen 1 and gen2 functions essentially impossible for anyone who uses gen1 config variables, which is probably most people.

    A quick google search will show that many people have this problem so the error should either be fixed or it should be noted in the upgrade documentation.

    Tell people that mixing V1 and V2 config files in the same project (note: even outside the gen2 function) will create a port and container error. Right now you don't mention in the docs or anywhere that having ANY function.config files in a project with a gen 2 function will cause a deploy error that says a container is broken and the port is unreachable. This error is misleading. It will also show the gen 2 function in the console as "unknown trigger" which also is misleading.

    In all your documentation you say you can have gen1 and gen2 functions… 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  ·  Cloud Functions 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

16. Security Rules: unique() operator

    I am submitting a feature request to introduce a 'unique()' operator in Firestore's security rules, offering a streamlined method to enforce data uniqueness within collections. This operator would not only simplify validation and potentially reduce reads by leveraging Firestore's hidden index table, but also eliminate the need for a separate cloud function, similar to the 'get()' and 'exists()' operations.

    Background:

    At present, ensuring data uniqueness in Firestore often requires workarounds that are less than optimal and can impact scalability.

    Feature Proposal:

    The proposed 'unique()' operator would operate much like the 'exists()' operation, but with a focus on reading Firestore's concealed index table. This efficient approach would verify the uniqueness of specified fields within collections.

    Comparison to Existing Operations:

    Similar to the 'get()' and 'exists()' operations, the 'unique()' operator would provide developers a straightforward means to validate crucial data points such as usernames, email addresses, and more, all without the need for complex cloud functions.

    Example Usage:

    For instance, to ascertain unique usernames:

    Firestore Security Rules:

    function isUniqueUsername(username) {
      return unique(/databases/$(database)/documents/users, ['username', '==', username]);
    }
    

    Benefits:

    Introducing the 'unique()' operator not only simplifies the validation process and leverages the hidden index table but also eliminates the requirement for an additional cloud function. This comprehensive approach enhances Firestore's performance while maintaining developer-friendly functionalities.

    Conclusion:

    By implementing the 'unique()' operator, Firestore could effectively address the challenge of maintaining data uniqueness while offering a holistic solution that eliminates the need for cloud functions.

    Thank you for considering this feature request. I'm optimistic about the significant value it could add to Firestore and our development workflows.

    I am submitting a feature request to introduce a 'unique()' operator in Firestore's security rules, offering a streamlined method to enforce data uniqueness within collections. This operator would not only simplify validation and potentially reduce reads by leveraging Firestore's hidden index table, but also eliminate the need for a separate cloud function, similar to the 'get()' and 'exists()' operations.

    Background:

    At present, ensuring data uniqueness in Firestore often requires workarounds that are less than optimal and can impact scalability.

    Feature Proposal:

    The proposed 'unique()' operator would operate much like the 'exists()' operation, but with a focus on reading Firestore's concealed… more

    26 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  ·  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. provide feedback on database restore progress

    During a restore, there's no way to know how long it will take or where the progress is. It would be great to have some visibility into the process.

    I initiated a restore from a backup created by the automated schedules

    gcloud alpha firestore databases restore \
    --source-backup=projects/PROJECTID/locations/LOCATION/backups/BACKUPID \
    --destination-database='DATABASE_ID'

    I have seen this take between 20 minutes to over a day.

    The documentation for this feature is here:

    https://cloud.google.com/firestore/docs/backups

    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

18. Jendo

    Menarik

    0 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

    2 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

19. Support reCAPTCHA Enterprice Multi-factor authentication

    AppCheck fail of low score reCaptcha

    user can't access based on AppCheck fail of low score reCaptcha

    reCAPTCHA Enterprice support Multi-factor authentication (Conditionally enforce email multi-factor authentication for users who score below a threshold.) but AppCheck does not.

    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 Check  ·  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. Should add basic REDIS/ Memcache Like Capability

    Why I Want This?

    Firebase splits functions to individual Docker Container. This works great for scaling, but with that it is not easy to share global values, for example, user's access key to external services and session specific values.

    While we can use REDIS and such hosted on GCP, it would be more "batteries included" platform if this feature is offered as a built-in functionality for the functions without resorting to Firestore or RTDB.

    What I look for is to globally share key values and also auto-expire them.

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