762 results found
-
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…
25 votes -
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.…
6 votes -
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…
1 vote -
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 -
dynamic robots.txt and favicon
Add capability to dynamically change robots.txt and favicon. The current behavior returns 404.
3 votes -
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 -
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 -
Crashlytics Section should have User perceived ANR Filter
There are lot of ANR like https://github.com/firebase/firebase-android-sdk/issues/6147#issuecomment-2417385067
Which has no solution even Firebase team concluded that.
So, there should be a filter to segregate user perceived ANRs on crashlytics.1 vote -
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 -
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 -
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 -
I needed phone number for free
I need phone number for free
0 votes -
Allow vapid key generation through a REST API call
Currently, vapid key generation is only available from the console UI. This is an issue when you want to manage firebase setup in a CI pipeline. A REST API endpoint would resolve this.
2 votes -
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 -
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.2but the documentation states that above operators are only working with numeric values :
"...
For string values:
exactly matches,
contains,
does not contain,
contains regexFor 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…1 vote -
Working perfectly fine
Excellent
1 vote -
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 -
Support customized user properties to target audiences.
Support customized user properties combining with topics to send notifications through API. The default user properties are not enough to group users. Need to combine topics with customized user properties as conditions to target audiences through API. Real time and high volume notifications request automatically pushing instead of manually pushing using console.
2 votes -
Disable build script in `firebase deploy` OR enable env configurations
Right now there's not the ability to select a build configuration. I want that either firebase leaves to the developers the option to build the app, or that a developer can instruct firebase to use a specific build configuration.
1 vote -
rules map
In Firebase Firestore rules, we currently have various controls and functions, which are very handy. However, array management is not optimal. I propose introducing a map function for arrays in Firebase Firestore rules. This function would allow us to map arrays of objects, significantly simplifying the creation and management of rules.
1 vote
- Don't see your idea?