Skip to content

General

General

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

692 results found

  1. Checking app

    1 vote
    How important is this to you?
  2. I'd like to have an option to install an extension for certain project in my code base.

    For example, I want to use algolia search extension on a collection that will only only exists in dev project, but I ended up deploying this extension in prod as well.

    I can't seem to find a way not to deploy extensions that are meant to be in dev only to prod.

    1 vote
    0 comments  ·  Extensions  ·  Admin →
    How important is this to you?
  3. DynamicLink Analytics Data don't have number of app install,

    but another data such as number of click, number of execution exists,

    I don't know why i cannot watch number of app install

    2 votes
    How important is this to you?
  4. Simple API to revoke the token/refresh token from a backend without using the SDK.

    19 votes
    How important is this to you?
  5. In Analytics Conversions
    Why can’t I find the unity ads network in the advertising network settings?

    1 vote
    0 comments  ·  Analytics  ·  Admin →
    How important is this to you?
  6. In Firebase's Firestore, a user with write access to a project can simply delete any document and even a whole collection with multiple documents with a single click. This is a major security problem as any of my team member may end up deleting a whole collection with millions of documents in under a minute, through the Firebase console.

    I would like to request for a feature to disable this.

    To be clear - The possibility to grant write access without delete access. Currently, if I am not mistaken, through the User and Permissions panel it's kind of "all or…

    11 votes
    1 comment  ·  Firestore  ·  Admin →
    How important is this to you?
  7. Would be great to have the option to integrate crashlytics alerts with google chat

    8 votes
    1 comment  ·  Crashlytics  ·  Admin →
    How important is this to you?
  8. Authentication is a difficult part of getting healthcare apps out there, and rightfully so, patient data security is hugely important. If Firebase offered this natively, not only would development be faster, but fewer mistakes/vulnerabilities would be present in healthcare apps that integrate with EHR.

    1 vote
    0 comments  ·  Authentication  ·  Admin →
    How important is this to you?
  9. 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

    4 votes
    How important is this to you?
  10. 2 votes
    How important is this to you?
  11. Just a UI issue on the website. I have multiple accounts on my phone and firebase automatically signs into what ever account that my mobile chrome is on. There is no option to sign out but my firebase is managed with a different amount. I switched the account on chrome but it's still logged into the other account. A simple sign out option would make life a lot easier when auto sign ins don't work.

    1 vote
    1 comment  ·  Other  ·  Admin →
    How important is this to you?
  12. Problem

    When filling out the form to add a Slack webhook URL for a Crashlytics project the form only allows URLs that begin with https://hooks.slack.com/..., however, some companies have their own proxy URLs to manage the Slack webhooks for their enterprise Slack instance (e.g. https://hooks.mycompanydomain.com/...).

    Feature request

    Please relax the client-side only form validation to allow other hostnames besides "hooks.slack.com".

    9 votes
    1 comment  ·  Crashlytics  ·  Admin →
    How important is this to you?
  13. You cannot delete a Firestore database with the API; you must use the CLI if you want to do this programmatically. This is problematic as it means you essentially need to create a shell in your application, ensure the CLI is available, authenticate, and then make the required CLI call.

    2 votes
    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?
  14. Currently you can only delete collections programmatically via the CLI. Otherwise, you have to list and delete every single document in the collection. If those documents have nested collections, you have to (recursively) retrieve and delete every document in the nested collection (As deleting a document does not delete any nested collections the document has). If there are additional levels of nested collections... You get the idea.

    I wasn't sure what this other request was referring to so I made this one: https://firebase.uservoice.com/forums/948424-general/suggestions/46562317-api-support-for-deleting-directories

    7 votes
    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?
  15. Add a bulk update user method to avoid handling the user configuration update limit of 10/s in code. Specifically, my use case is to bulk disable/enable users in a single call.

    1 vote
    0 comments  ·  Authentication  ·  Admin →
    How important is this to you?
  16. 1 vote
    0 comments  ·  Authentication  ·  Admin →
    How important is this to you?
  17. Currently, subcollections are treated separately from fields in the UI. This seems like an arbitrary distinction - a subcollection is simply a json object under a document. You could do the same thing with a string field.

    The API could support retrieving subcollections as string fields in json format for a document. This would prevent the need to iterate over every document in a collection, then get a list of the subcollections, then retrieve the documents from those subcollections, etc. If worried about time required, since Firestore supports 100 nesting levels, perhaps the API call could include the nesting level…

    1 vote
    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?
  18. If Firebase cannot support some kind of changestream implementation, it should include metadata on each document that includes a "last updated" timestamp. Then clients can query against this field to only retrieve "new" changes (Inserts, Updates). It lacks support for delete capture but is the next best thing after a changestream.

    18 votes
    1 comment  ·  Firestore  ·  Admin →
    How important is this to you?
  19. Firestore does not support any actual CDC (Change Data Capture). A changestream similar to other NoSQL implementations (Mongo, DocumentDB, Azure Cosmos DB) would make the database a lot more usable and grant feature parity with other popular NoSQL databases. This changestream would expose operations like updates, inserts, and deletes for a client to come and retrieve from either a timestamp or a resume token.

    8 votes
    1 comment  ·  Firestore  ·  Admin →
    How important is this to you?
  20. Currently, Firestore and Cloud Storage security rules req.auth property will only validate and accept Google-signed ID tokens from Firebase Auth/Identity Platform.

    This means that "user authentication rules" CANNOT be used if we rely on our own (or 3rd-party) authentication/token server.

    Proposal:
    Allow security rules to configure the token verification rules so that they can verify the token claims of a configured token authority. For example, tokens signed by a service account private key, or 3rd party auth server (aside from Firebase Auth/Identity Platform).

    1 vote
    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?
  • Don't see your idea?