776 results found

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

   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

2. Sub Collection View

   I feel the window to view sub collection on the firebase firestore console could be expandable.

   2 votes

   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

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

   25 votes

   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

4. Automatic SMS OTP read with English templates

   For automatic SMS retrieval to work, SMS length has to be under 64 bytes. This means currently that for English SMS template, the app name has to be 11-14 characters. Play Console allows max 30 characters. Firebase doesn't allow customers to modify the SMS template contents themselves. Now I'm working around by utilizing some other languages, that will fit below 64 bytes with current app name.

   Two options I suggest to achieve this:
   1) Modify the English SMS template: remove unnecessary filler words and make it shorter, so that it will fit to 64bytes with max 30 char app names.

   or

   2) Add support to Firebase SMS Templates for English variants, so those could be used solely for sending out OTP SMS with shorter app names set in the Store listing.

   For automatic SMS retrieval to work, SMS length has to be under 64 bytes. This means currently that for English SMS template, the app name has to be 11-14 characters. Play Console allows max 30 characters. Firebase doesn't allow customers to modify the SMS template contents themselves. Now I'm working around by utilizing some other languages, that will fit below 64 bytes with current app name.

   Two options I suggest to achieve this:
   1) Modify the English SMS template: remove unnecessary filler words and make it shorter, so that it will fit to 64bytes with max 30 char app names.

   … more

   6 votes

   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

5. Crashlytics support for react JS based application.

   Crashlytics support for react JS based application.

   2 votes

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

6. Replace collection with new set of documents as an atomic operation

   Many time, we have a collection that is created using data received from an API call and the collection needs to be reset to the new data received in the next API call. For e.g., I have a collaborative app. Each user can see who else in their address-book using the app, such that they can collaborate with them. I send the phone contacts to the backend and we check which contacts and using the app and initialize the contacts collection. The phone contacts are synched every day. The next day, when we get the phone contacts, I want simply find out who is using the app and replace the contacts collection with that data without finding out who was already present in the contacts collection, which contact data has changed and which contacts is no longer there. Currently, if I delete the collection and then recreate with new set of documents, the realtime update listener is triggered with empty collection causing unwanted behavior in the app.

   Many time, we have a collection that is created using data received from an API call and the collection needs to be reset to the new data received in the next API call. For e.g., I have a collaborative app. Each user can see who else in their address-book using the app, such that they can collaborate with them. I send the phone contacts to the backend and we check which contacts and using the app and initialize the contacts collection. The phone contacts are synched every day. The next day, when we get the phone contacts, I want simply… more

   1 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

7. Remote Config Emulator

   Provide a native emulator for Remote Config with A/B tests will be great, but is not critical.

   5 votes

   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

8. Add real time support to the Firebase Javascipt SDK for Remote Config

   Real time fetches are currently supported for all platforms except the Javascript SDK. I'd like to be able to fetch in real time across all of my apps: iOS, Android, and Web.

   33 votes

   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

   5 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

9. dynamic robots.txt and favicon

   Add capability to dynamically change robots.txt and favicon. The current behavior returns 404.

   3 votes

   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. Explain the format of the Firestore rules (and indexes) in firebase.json

    At https://firebase.google.com/docs/cli?authuser=0#the_firebasejson_file, the firebase.json examples mention the Firestore rules like this:

    "rules": "firestore.rules",
    "rules": "firestore.default.rules",
    "indexes": "firestore.default.indexes.json"

    What exactly is "firestore.rules"? A reserved string? An ID (pointing to what)? A filename (in what format)?

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

11. Unique password option for password policy

    Add an option for the password policy to require users to create a new, unique password that has never been used for their accounts.

    1 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  ·  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. Native Swift implementation of the Real-time database client

    The current Swift client for the Real-time database is written in Objective-C with a Swift overlay.
    In order to allow using Firebase from Swift across different platforms like Windows and Linux, it would be awesome with a native Swift version. Alternatively a Swift version bridged directly from the firebase-cpp-sdk using the new Swift C++ interoperability.

    I did a port of the Objective-C code to Swift as an experiment, and I have it running on Linux just fine - together with the Auth-rewrite in Swift.

    The (very experimental) PR is here: https://github.com/firebase/firebase-ios-sdk/pull/8670

    3 votes

    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

13. Firestore: Use C++ implementation directly from Swift

    Swift has recently gained direct interoperability with C++.
    
    This would allow the current bridging layer written in Objective-C++ to be removed, which would in turn make it possible to use Firestore from Swift cross platform.

    The Browser Company have created patches for firebase-cpp-sdk to allow this:

    https://github.com/thebrowsercompany/swift-firebase

    It could also decrease the maintenance burden by removing the bridging layer code.

    3 votes

    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

14. no se registra mi dominio lleva casi 1 semana, y no tengo menor idea del por que

    no se registro mi dominio y no se por que o que esta mal

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

15. I needed phone number for free

    I need phone number for free

    0 votes

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

16. Phishing on Firebase - API Abuse channel for trusted vetted security partners

    I would like to explore the opportunity to become a partner to GCP / Firebase.

    How can security companies who deal with phishing and enforcement of AuP ToS breaches submit data to Google Firebase for quicker enforcement when there is abuse?

    Google is a very big company, but finding an actual human who works for Google is seemingly a very hard task - always automated reporting systems, which is understandable.
    
    But it feels like dealing with a faceless behemoth,
    Thus I want to explore the options to becoming a known vetted partner to Google Cloud platform, so GCP and Firebase pays attention to the valid abuse reports i have to share and acts on them accordingly in a timely manner.

    Right now abuse reports dispatched to Google Firebase feel like screaming in a void, due to the giant behemoth Google is.

    My problem is concretely with GCP and FIREBASE.

    I represent government entities, fin tech companies, telcos, banks, automotive sector, insurance companies and many others who are often targeted by phishers and the turnaround times are sadly not very good, which opens a window of opportunity to threat actors and phishers.

    I would like to explore the opportunity to become a partner to GCP / Firebase.

    How can security companies who deal with phishing and enforcement of AuP ToS breaches submit data to Google Firebase for quicker enforcement when there is abuse?

    Google is a very big company, but finding an actual human who works for Google is seemingly a very hard task - always automated reporting systems, which is understandable.
    
    But it feels like dealing with a faceless behemoth,
    Thus I want to explore the options to becoming a known vetted partner to Google Cloud platform, so GCP and Firebase… more

    2 votes

    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

17. Changestream

    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

    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  ·  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. Improve RemoteConfig conditions documentation

    Documentation about conditions for iOS and Android is lacking proper description for semver logic on parameter 'AppVersion'

    It seems that the condition properly evaluate operators
    >
>=
<
<=
    when the app version is a semver string i.e. 1.18.10 > 1.18.2

    but the documentation states that above operators are only working with numeric values :

    "...
    For string values:
    exactly matches,
    contains,
    does not contain,
    contains regex

    For numeric values:
    <, <=, =, !=, >, >=
    ..."

    The logic behind semver is very important and specific.
    To use it safetly we really need to be sure that the comparison is implemented as intended and documentation should describe it properly the implementation details.

    We really need semver comparison, otherwise simple matching on string is not useful to provide conditions based on AppVersion.
    At the same time we don't want to use because it works now with the risk it may change in the future because is not described in the docs.

    Please describe if the semver is implemented as intended to clear doubts.

    🙏

    Documentation about conditions for iOS and Android is lacking proper description for semver logic on parameter 'AppVersion'

    It seems that the condition properly evaluate operators
    >
>=
<
<=
    when the app version is a semver string i.e. 1.18.10 > 1.18.2

    but the documentation states that above operators are only working with numeric values :

    "...
    For string values:
    exactly matches,
    contains,
    does not contain,
    contains regex

    For numeric values:
    <, <=, =, !=, >, >=
    ..."

    The logic behind semver is very important and specific.
    To use it safetly we really need to be sure that the comparison is… more

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

19. Working perfectly fine

    Excellent

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

20. Notes Section

    Bro, I really think Firebase lacks a "notes section", I mean, sometimes you come up with something while working there, would be so great. Such as something floating.. or simply easy to access...

    2 votes

    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