1222 results found
-
Targeting all users via App Package Name
FCM must support targeting all users in HTTP v1 API by App Package Name via 'to' parameter in addition to 'topic', 'condition' and 'device token' as like available in FCM console. More suitable targeting parameter may also be added.
5 votes -
Security key/WebAuthn 2FA
Currently, we only have the option to use TOTP 2fa or SMS. Security keys are quickly gaining popularity, as it is a more secure option. Please add this.
2 votes -
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…
3 votes -
Expose createTime & updateTime in scheduled Firebase LevelDB exports
I am using this procedure for regular backups: https://firebase.google.com/docs/firestore/solutions/schedule-export
and some tooling to locally analyze data in the resulting (downloaded) LevelDB backups.The Admin SDK exposes (internally, but still) createTime, readTime and updateTime properties on snapshots. I don’t see these properties included in the database exports; which makes them less complete as backups, and less useful for data analysis.
2 votes -
Allow connecting the web client to HTTPS-hosted emulators (for Web Push testing & more)
Allow connecting the web client to HTTPS-hosted emulators (for Web Push testing & more)
Browsers nowadays require HTTPS-hosted sites to use some privileged features, like Web Push. HTTPS-hosted sites also typically can not request HTTP content from APIs ("protocol downgrade" errors).
Most Firebase Emulators are not built to work with HTTPS, which puts up a big obstacle to test HTTPS-enabled features on external devices (e.g. test locally-hosted Web Push server code on an external Android phone).
Server-side: Firebase emulators don't offer ways to be served over HTTPS, but tools like ngrok or a local HTTPS proxy offer simple workarounds for…
52 votes -
Nice idea, thinking
Website structure is good, nice demo
1 vote -
not upgrading blaze plan
firebase is not updateing to blaze plan i already have an verified billing account you should have to give more information about how to setup properly
4 votes -
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:
3 votes -
3 votes
-
Support inline/embeded types stored as structured JSONB columns
Allow storing structured types in JSONB columns using an @inline (or @embed) directive on the field.
type Address {
street: String!
street2: String
city: String!
state: String!
zipcode: String!
}type User @table {
address: Address @inline # stores as JSONB
}21 votes -
Custom GraphQL Scalar Support
On top of common scalars such as Email, Phone, etc., custom scalars are defined by developers on the client-side application, with logic for marshaling and unmarshalling the data provided, which could be either a class with the two methods or a couple of functions.
8 votes -
the sms quota for this project has been exceedded exceeded quota
Those shiit gringos to everything they see him money
3 votes -
Full Example of FirebaseServerApp in Next.js 14 using middleware
Create a comprehensive solution for authentication that is both client and server using middleware to protect pages. Correctly passing the ID token of the user when needed to API endpoints.
24 votes -
dynamic robots.txt and favicon
Add capability to dynamically change robots.txt and favicon. The current behavior returns 404.
6 votes -
AI suggestions in FCM notifications
AI suggests the body for a notification that I'm writing in the Firebase console, based on a notification title that I provide or a text that I write in natural language.
3 votes -
Interfaces, Union types in GraphQL
Support for GraphQL Interfaces or Union Types through the built in GraphQL schema builder tool. This was extensively discussed in the Google Chat group.
15 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 -
Cloud Armor or WAF Support
Enhanced security features such as Cloud Armor or WAF is almost a must-have nowadays also the level of protection is unclear.
9 votes -
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
- Don't see your idea?