1217 results found
-
Green/Blue deployment pattern
Allow for deployments to be either a green or blue deployment to be able to have multiple instances of the same functions deployed within a single Firebase project.
This would help cover the gap of time between releases of client apps and Cloud Functions, which if not handled correctly cause production issues.
3 votes -
Jira Cloud Integration for Post production issue type:
Currently, Crashlytics only supports Bug issue type with Jira Integration. It would be helpful if it allowed other issue types, such as post-production issues.
This solution allows users to integrate with their organization's Jira issue-type standards, including Pre-production, Post-production, and Defects, instead of relying solely on the issuetype "bug".
2 votes -
12 votes
-
10 votes
-
Add Bulk User Update to SDK
Add a bulk update user method to avoid handling the user configuration update limit of 10/s in code. Specifically, my use case is to bulk disable/enable users in a single call.
1 vote -
1 vote
-
Zero Config Image CDN - With Transformation Support
Similar to ImgIx or Supabase Images, the feature to create a storage bucket with image transformation and CDK enabled, can be used to provide images for the front-end, in different formats, sizes, and optimized for the browser.
11 votes -
HTTPS Proxy with Authentication
Firebase currently does not have a clear way of supporting HTTPS proxy. If the network is limited by OEM's restrictions, or firewalls then Firebase Crashlytics won't operate. Probably no Firebase service will be able to work.
We can set the domain and the port for HTTP proxy, but then it is not authenticated.
3 votes -
Rules between Firestore and Realtime Database
We've rules to limit access to data in both firestore and realtime database, but there are requirements where I need to specify a rule of realtime database based on a value in Firestore.
Games are classical examples, I want to store the realtime game data in realtime DB but apply rules to read and write there based on my user and app data in firestore.
Lack of this is either making me use either of the DB or write hard rules in client side (which is not really secure).
10 votes -
Disable Passwordless Sign-In for E-mail
As Firebase is retiring Dynamic Links, it is no longer possible to set up the Dynamic Link required for Passwordless Sign-In via e-mail. I recommend that either Firebase disable Passwordless Sign-In, or that they update their documentation outlining the new method to do Passwordless Sign-In without their Dynamic Link.
3 votes -
Expose subcollections as json fields
Currently, subcollections are treated separately from fields in the UI. This seems like an arbitrary distinction - a subcollection is simply a json object under a document. You could do the same thing with a string field.
The API could support retrieving subcollections as string fields in json format for a document. This would prevent the need to iterate over every document in a collection, then get a list of the subcollections, then retrieve the documents from those subcollections, etc. If worried about time required, since Firestore supports 100 nesting levels, perhaps the API call could include the nesting level…
1 vote -
Allow security rules to validate custom bearer tokens
Currently, Firestore and Cloud Storage security rules
req.authproperty will only validate and accept Google-signed ID tokens from Firebase Auth/Identity Platform.This means that "user authentication rules" CANNOT be used if we rely on our own (or 3rd-party) authentication/token server.
Proposal:
Allow security rules to configure the token verification rules so that they can verify the token claims of a configured token authority. For example, tokens signed by a service account private key, or 3rd party auth server (aside from Firebase Auth/Identity Platform).1 vote -
2 votes
-
1 vote
-
GODOT implementation
would be great if I could use the GODOT game engine with Firebase.
because I saw many other game engines use Firebase, like Unity I think will be great to have this feature.3 votes -
Add ability to view performance monitoring metrics per request method per url
Currently, we can view metrics for specific URL patterns; however, we cannot set up separate monitoring for different request methods (GET, PUT, POST, etc.) for the same URL pattern.
Either the ability to set up monitoring for a given request method + URL pattern combo, the ability to filter down into specific request methods for a given URL pattern, or both would be wonderful.
5 votes -
Query language (like SQL) but for firestore to enable developers to share queries across the whole stack
let's say that you have a Kotlin android app, Swift iOS app, a Dart Flutter app and cloud functions written in typescript.
there should be a way to re-use shared queries across the whole stack.
having a query language like SQL and pass those redundant queries across all apps that would be really efficient and could save developers a lot of time and it could produce less bugs.I'm not suggesting SQL, I'm suggesting to have a query language that's all.
1 vote -
Support yarn and/or pnpm for frameworks
Currently frameworks only used npm
This can cause issues if using yarn or pnpm, and npm does not read the lockfile and you can end up with different versions of dependencies in production
Deployments with frameworks should detect the package manager used
3 votes -
Shorten email verification link
I am building a web application using Firebase authentication. I require email verification to have users access our platform. Currently, the link is quite long, but I was wondering if there was any way to shorten the URL to make it more user friendly, and to make it look less spam-like
3 votes -
10 votes
- Don't see your idea?