702 results found
-
Firestore indexes in emulator
Currently, the Firestore emulator allows all queries without checking if the query requires an index. It would be great if the emulator checks the Firestore indexes file if the index exists.
118 votes -
IOS SDK should have initializer simple initializers
Right now the SDK generated only has init with decoder.
public init(from decoder: any Decoder)
This limits us in generating the Previews for the views. Please consider adding additional inits with all variables in the struct
1 vote -
Need to use same app integrity certificat
When using app distribution, it would be nice if the certificate wasn't replaced to maintain consistency with the app in production.
2 votes -
Cloud Functions versioning
It will be great to have an easy way to deploy different versions of our API and access them by adding a "v1" or "v2" to the URL.
Currently, we can do it manually by changing the name of the function, but the ideal is to have a new parameter in the deployment process (CLI) to "group" them in versions.
This idea is great to roll out and have different versions living side by side until the production version that uses the new API is released to all the users.3 votes -
Secure Transport Layer Implementation
The "Secure Transport Layer Implementation" idea centers around fortifying the application's transport layer to mitigate vulnerabilities, particularly the risk of insufficient protection against attacks like POODLE. This vulnerability exposes the application to potential exploits, compromising the confidentiality and integrity of data exchanged between the application and its users.
Insufficient transport layer protection opens the door to various security threats, including man-in-the-middle attacks, data interception, injection of malicious content, and communication redirection. These threats undermine the trustworthiness of the application and jeopardize user data security.
To address this vulnerability effectively, it's imperative to reinforce the application's transport layer security by implementing…
12 votes -
Postgres Functions exposed as an API
Similar services, like postgraphile, allow exposing queries / mutations as postgres functions. It's extremely powerful, and allow extremely custom queries / logic for exposing data to the clients.
10 votes -
support SvelteKit in app hosting
support SvelteKit apps in the new App Hosting
10 votes -
Analytics Admin Sdk
Create Api for Firebase Admin SDK to get analytics data.
1 vote -
Add ability to choose Test Lab's device location
Some applications are very dependent (in performance perspective) on resources from CDNs & backend location - it would be great if we can choose location of the Test Lab's device location (preferably Android real devices) to set it closer to CDN & backend.
3 votes -
doesn't deprecate Firebase Dynamic Links and separately charge for the feature as part of the Blaze plan.
Firebase Dynamic Links are slated to be fully removed by Aug, 2025 but it is such a wonderful feature and I am not sure why is it removed from Firebase suite. I am willing to pay for it and I am sure there are many other users willing to pay for it.
3 votes -
make it more easy
It's incredible how complex you made Firebase, because of the link with Google Cloud. Firebase used to be an easy solution, but it's all soo overly complex that I don't trust any of it.
Maybe I will suddenly get a large bill because I made a mistake, or the configuration is bad. It's really annoying. Your service has gone from an easy to use cloud solution to a complete mess of configuration annoyances, security angst, complex issues.
The documentation is overly complex. You loop around in al the options. And everything refers to Google Cloud again.
Nothing is easy with…
3 votes -
Remove git from functions folder
Using firebase init will create a git submodule in the functions folder, which is a giant hassle to remove. I just want init git in the root project.
1 vote -
Log thirdPartyPrincipal in storage audit logs, similar to firestore
It seems GCP audit logs can capture all the operations on the firebase storage bucket, but the actor that shows up in the logs is a service account, rather than the end user. Is there a way to capture the end user who is requesting storage objects?
When I look at audit logs for firestore, I see a thirdPartyPrincipal that includes the end user, but this doesn't show up in the storage audit logs.
3 votes -
App Distribution API includes information whether tester have installed the app
Currently the only way to know whether a tester have installed a version is through the Firebase Console. I wish we could get this information through the App Distribution API too. Currently we only have lastActivityTime which is not very useful: https://firebase.google.com/docs/reference/app-distribution/rest/v1/projects.testers#Tester
2 votes -
Adding Republic of Moldova to a preview list of Gemini
Could you please add Moldova to the list of countries who can preview Gemini? We cannot use it in Android Studio and have to use other AI.
6 votes -
Add service to Data Connect Triggers
Trigger a Cloud Function that will add the service and schema to Data Connect when the user signs up successfully.
2 votes -
notes
Add Crashlytics Issue Notes to the Crashlytics Schema [1] for BigQuery Export [2]
[1] https://firebase.google.com/docs/crashlytics/bigquery-export#schema-columns
[2] https://firebase.google.com/docs/crashlytics/bigquery-export2 votes -
Expose "last updated" metadata
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 -
Vector embedding search should include distance in results
The newly released capability is https://firebase.google.com/docs/firestore/vector-search is working very nicely! However, all similar products should return the distance metric in the query results (which the backend has no doubt already calculated) so that the client perform further analysis based on that distance
8 votes -
Enhanced Foreign Key Behavior
I am reaching out to share a suggestion regarding the current implementation of foreign key constraints in Firebase DataConnect.
Currently, it appears that the default behavior for foreign keys is automatically assigned during schema deployment, and there is no way to explicitly define ON DELETE and ON UPDATE rules (e.g., NO ACTION, CASCADE) in the GraphQL schema. This limitation has the following implications:
1. Deployment Overrides: Even if these rules are manually adjusted in the underlying PostgreSQL database, deploying an updated schema resets the rules to the platform’s defaults.
2. Lack of Customization in Schema: Adding support for directives like…2 votes
- Don't see your idea?