67 results found
-
Add a delete button to Cloud Functions...
- There's literally no button to delete cloud functions anymore, i have no ability to delete them besides typing in 3 lines of code into the command line.
- There's ellipsis buttons that do nothing when tapped.
- There's a blue block at the bottom right of the view that does nothing and is a UI eye sore.
- The webpage is in dark mode and hard to see ui elements despite my device not being in dark mode and other google services not in dark mode.
- There's no support unless i pay.
I must be in some unknown beta test because there's no…
1 vote -
saltar al contenido Google, LLC - Firebase Tombomvouz Tombomnouz Mantener la sesión iniciada · Configuración · Salir Support Kotlin Multipl
saltar al contenido
Google, LLC - FirebaseTombomvouz Tombomnouz
Mantener la sesión iniciada · Configuración · Salir
Support Kotlin Multiplatform (KMP) in the SDKs
KMP is now stable and more libraries are being added to KMP ecosystem. There is a big opportunity for Firebase to be in Multiplatform and support developers adopting this tech.1,248
vota
Carlos Monzon
compartió esta sugerencia
· 27 de abril de 2023 · Reporte…
Cuan importante es esto Para ti?
Not at all
Important
Critical
Añadir un comentario…
Enviar un comentario
Jeff Avery
comentado
· 17 de marzo de 2024 12:06 · Reporte
I teach…1 vote -
1 vote
-
Allow underscores in task handler function names
Underscores are not allowed in cloud tasks handler functions. In JS/TS hyphens are not an option (because they are not allowed in variable names) and so we are forced to use camel-cased names.
We use underscores for all of our other function names, so we can't be consistent when naming task handlers.
This seems like a silly constraint, even more so because it doesn't apply to other cloud function types. I've been waiting for years for this to be fixed, please make it happen.
Request to https://cloudtasks.googleapis.com/v2/projects/myproject/locations/us-central1/queues/some_function_name had HTTP Error: 400, Queue ID "somefunctionname" can contain only letters…
1 vote -
add a section to roll back to a specific build
Add a section to roll back to a specific build. Just one place to list all the builds and which were published, with the option to rename them! So I can roll back to a specific build, especially on production
1 vote -
Group function by category
I think it would be awesome if we could group functions by category on the screen.
Sometimes we have a lot of functions depending on the project, and it becomes a little hard to read the console — it gets kind of fuzzy.4 votes -
Infinite loop/recursion detection
It's possible to make a mistake that causes a function to trigger itself (for example, an onDocumentWritten Firestore trigger that writes to the same document). If Cloud Functions for Firebase could detect this and shut down the infinite loop, it could prevent runaway bills.
It could also be a feature in the emulator suite so that we could check for them before deploying to production.
3 votes -
Allow ordering functions when they are displayed in firebase console.
As a non-expert user, I am trying to avoid navigating the Google Cloud Console ("GCC") when possible (which should be understandable since that is largely the point of Firebase). So when an internal error in one of my functions occurs, I go to the firebase console, find the relevant function and then select "see logs" which takes me the to the precise place in GCC. The issue is that the function in the Firebase console seem to be displayed in random order with no way of ordering them... so it is always a pain to scan through them to find…
2 votes -
🚀 Advanced Proposal: Hybrid Firebase Architecture for Optimized Performance, Offline Access & Cloud Resilience
🧠 Core Strategy
Deploy Firebase Studio locally (on-premise or VM)
Integrate with Firebase Emulator Suite + Edge Cache
Enable automatic sync with Firebase Cloud
Allow direct access to local services (filesystem, DB, devices)
Use secure reverse tunnels and proxy APIs for controlled cloud interactions
✅ Key Benefits Overview
Feature Benefit
✅ Offline First Use Firebase Emulator Suite to run Firestore, Auth, Hosting, Functions entirely offline
✅ Faster Performance Local queries eliminate latency from cloud round-trips
✅ Access Local Resources Direct access to local files, OS services, SQLite, or PostgreSQL
✅ Data Control Comply with GDPR/PDPA by keeping sensitive data local…5 votes -
افكار ساخنه
كل انواع النشاط واحدث الميزات انفنكس اصدار الحدث
1 vote -
On Document Update Firebase Function on specfic field update
OnDocumentUpdate firebase function should allow a filter such that function gets triggered when particular field(s) of the document changes. Currently the functions are triggered for every change made to the document. This leads to unnecessary billing.
1 vote -
Support Direct VPC
A static IP is a must-have feature when dealing with certain services.
In the past, we could use Serverless VPC Access connectors, but this required renting a virtual machine (VM), which contradicts the principles of serverless architecture and significantly increases costs.
Recently, a new method called Direct VPC has emerged, which eliminates the need for connectors. This means it is truly serverless, even when using a static IP.
Currently, Direct VPC can be configured by revision in the Google Cloud Console. However, I would like to enable Direct VPC in Firebase Functions as an option, like so:
vpcConnector: 'test-connector',
vpcConnectorEgressSettings:5 votes -
Consistent and documented behavior for on*WithAuthContext
When Functions use e.g. onDocumentCreatedWithAuthContext to handle Firestore event triggers, the meaning of event.authType and event.authId are not documented and are inconsistent between the production and emulator environments.
The documentation [https://firebase.google.com/docs/functions/firestore-events?gen=2nd#auth-context](here) says "For information about the data available in the authentication context, see..." and links to a page that is not specific to Firebase. That page lists some possible values, but it's not clear what values would be used. The most sensible guess is that authType would be "appuser" or "user" if the document was created from the client-side web SDK, and "serviceaccount" if created from a…
4 votes -
Improve Billing Verification and Support for New Firebase Users
Many new Firebase users face serious issues when trying to activate the Blaze plan due to strict and non-transparent billing verification processes.
In my case:
• I attempted to verify my billing using a Revolut card (registered under my name);
• All payment confirmations were approved through the Revolut mobile app (4–5 times), yet the verification still failed;
• No clear error explanation was provided, and I had no way to resolve the issue;
• I tried adding a backup Korean card, but the verification message never arrived in the Korean mobile banking app (SMS also didn’t arrive because my…5 votes -
Fix error messages when deploying Functions
Several error messages often occur when deploying Firebase Cloud Functions that should not occur. My first time attempting to deploy functions in a new project, I got:
i extensions: ensuring required API firebaseextensions.googleapis.com is enabled...
⚠ extensions: missing required API firebaseextensions.googleapis.com. Enabling now...Error: Request to https://serviceusage.googleapis.com/v1/projects/********/services/firebaseextensions.googleapis.com had HTTP Error: 429, Quota exceeded for quota metric 'Default requests' and limit 'Default requests per minute' of service 'serviceusage.googleapis.com' for consumer 'project_number:********'.
I don't know if that happens every time. It appears to be just a failure to wait long enough after enabling the API.
The second time, it got further, but…
4 votes -
Support .NET (C#) in Firebase Functions.
Firebase has .NET SDKs for the client and admin SDKS. It would be nice if Firebase Functions supported .NET (C#) especially since GCP Cloud Run Functions already support .NET.
4 votes -
Add Support for Aggregation Functions and Regex Filtering in Firebase Realtime Database
Firebase Realtime Database currently lacks support for aggregation functions (like sum, count, average) and regex-based data filtering. These features would simplify querying, reduce client-side processing, and improve performance, especially with large datasets. While Firestore offers some of these capabilities, Realtime Database remains the preferred choice for real-time syncing. Native support for these functionalities would greatly enhance its potential and usability.
7 votes -
Add support for local npm packages
Change the behavior of dpeloy for functions so that if a local (file based) npm package is listed in the package dependencies, the package will be uploaded with the function.
It is a major pain for local packages to not be supported in uploading cloud functions.
6 votes -
Enable source map support
Since Node 12 it has built-in source map support. For cloud run deployments we can start the node server with the flag --enable-source-maps, but for cloud functions we don't have this control.
I don't understand why we still need to install and register the source-map-support NPM package in our code to get source maps to work.
I suggest to have a configuration option that enables the flag, preventing us from having to manually install a package that is considered obsolete for newer versions of Node.
4 votes -
Allow secrets on scheduled functions
It's not clear in the documentation nor by implementation that secrets work with scheduled cloud functions. This seems to me like a major missing feature in security and consistency with the v2 cloud functions. Is the only solution using the cloud config for api keys/secrets?
We need to have something like:
exports.someScheduledFunction = onSchedule(
{
schedule: "every 60 minutes",
timeoutSeconds: 100,
secrets: [someToken.name],
},
async () => {
logInfo("Running every 60 min");...
}
);3 votes
- Don't see your idea?