1238 results found
-
CLI deploy and link blocking functions
Function Deployment & Validation Flow:
When deploying cloud functions with recognized lifecycle hook names (e.g., beforeCreate, beforeSignin), the system should:
.
Detect Blocking Function Patterns
Check if the deployed function's name matches known blocking trigger conventions..
Assignment Validation
Verify whether the detected function is registered as a blocking trigger in the system configuration..
Interactive Guidance
If unassigned, display CLI prompt:
"Seems like you want to deploy a 'Blocking' function named <FUNCTION_NAME> but no blocking trigger is assigned. To configure this function visit: <CONSOLE URL>".
Key Function Patterns:beforeCreate | beforeSignin | afterSignout | customBeforeHookWhy This Matters:
…
1 vote -
CLI deploy and link blocking functions
Function Deployment & Validation Flow:
When deploying cloud functions with recognized lifecycle hook names (e.g., beforeCreate, beforeSignin), the system should:Detect Blocking Function Patterns
Check if the deployed function's name matches known blocking trigger conventions.Assignment Validation
Verify whether the detected function is registered as a blocking trigger in the system configuration.Interactive Guidance
If unassigned, display CLI prompt:
"Seems like you want to deploy a 'Blocking' function named <FUNCTION_NAME> but no blocking trigger is assigned. Would you like to configure this function now? (y/N)"Key Function Patterns:
```
beforeCreate | beforeSignin | afterSignout | customBeforeHook(Additional supported hooks)
…Why1 vote -
Request Query Parameters for Security Rules
Introduce a request.query.parameters object to store key-value pairs from the query payload, enabling conditional access control based on user authentication state.
Current workarounds, like nesting documents in sub-collections, restrict uniqueness to a single field. This proposal allows queries to be filtered dynamically based on multiple conditions.
For example, access can be restricted based on user authentication state or location.
if request.query.parameters.user == request.auth.uid if request.query.parameters.location == request.auth.token.region if request.query.parameters.email != null if request.query.parameters.email == request.auth.emailPrivileged searches can be enabled with conditions such as:
if request.query.parameters.key == request.auth.token.vipkeyRange queries can be implemented using a function object to validate if…
1 vote -
Beting
প্রথম ডিপোজিটে ১০%পার্সেন্ট বোনাস
1 vote -
multiplatform
full support for KMM android, web, ios and desktop.
What is the point of not supporting all of these?we build the best car but you can only use one wheel. Not a great theory for adoption.
1 vote -
Have a Realtime Database located in Australia ( Sydney or Melbourne )
As of this writing, our only option for Database location is US Central, Belgium and Southeast Asia. Having a new region under Australia would be great.
1 vote -
.net maui sdk for firebase data connect
support using Data Connect in c# and .NET Maui by having SDK for C# and generating C# types from the schema
1 vote -
1 vote
-
Allow Events with Reserved Names as A/B Test Goals
We have several events with the prefix "Firebase_" for irrelevant reasons. These events were successfully added to Google Analytics by sending them via mParticle.
We can view statistics for these events, but we cannot use them as goals for A/B tests. The UI displays the following error:
"Error: Error saving experiment: Can't validate experiment data."
The server response states:
"Cannot use reserved event name: '<event name>'."The suggested workaround is to create new events with non-reserved names based on these existing events. However, there are limits on the number of events you can create, and this adds unnecessary work.
Since…
1 vote -
Firebase authentication needs to support standard user profile attribute mapping
When leveraging firebase for OIDC based authentication, there is data loss in mapping of standard user profile attributes between IdP and app such as given name, family name and other attributes as specified in the standard specifications[1]. Firebase auth must implement the specification properly and ensure against data loss.
1 vote -
Option to clear remote config locally stored data
Remote config fetched values are not encrypted and it's kept as plain text. Is there any function that can be used to clear this data after a successful fetch? At least we can keep the data safe on our own if there's a way to clear the local file content. I know currently it keeps the last fetched time in the same file but a clear function can clear all values except values like last fetch time. Will be very useful for those who want to use remote config data securely
1 vote -
Firebase project config in env
Cloud functions do provide process. env.FIREBASE_CONFIG.
One can set it in the yaml, but it would be nice if app hosting would provide these automatically.
1 vote -
Support submodules
Support submodules for automated builds.
Currently, builds fail when checking out submodules.
1 vote -
Add Support for Firebase App Check Without Requiring Authentication for Android Storage Access
The issue I am encountering is quite unusual. It arises whenever we try to access storage, even though I am using App Check and Firebase authentication is not required. Our App Check setup appears to be functioning correctly, and we can fetch data without any problems. However, these errors still appear in the console. This issue is occurring only in the Android, while the iOS works fine.
Console error:
error getting token java.util.concurrent.ExecutionException: com.google.firebase.internal.api.FirebaseNoSignedInUserException: Please sign in before trying to get a token.1 vote -
assign server timestamp in epoch format
adding a function like FieldValue.serverTimestamp() that does the same thing but assigns time in epoch format rather than in normal date time format.
it may be a better choice in order to reduce the data transfer and document collection size.
1 vote -
Allow "App Nickname" to be an option in the link text generated for email link authentication
Currently there is no way to customize the email sent to users who authenticate via email (deep ?) link. I understand / accept the rational for this.
For Firebase projects with multiple Apps, this leads to all authentication emails having a single title (and link) based on the "public-facing name" set in "Project settings". It would be good to have an option to use the "app nickname" used for each of the Apps within the project to form the basis for the email title + link text. This would give users more confidence that they've received a valid login email…
1 vote -
Similar to __name__, allow ordering documents by internal createdAt / updatedAt sentinel value
A document always maintain createdAt / updatedAt timestamp value internally. But these fields can't be used for ordering documents.
For example :-
(This is possible)
await citiesRef.orderBy('name').limit(3).get();
(This is NOT possible)
await citiesRef.orderBy('created_at').limit(3).get();
Currently if we need order by timestamp, we need to maintain a separate timestamp field alongside internal createdAt / updatedAt fields. Then create index over that additional field to perform order by timestamp.
Similar to name sentinel, firestore should provide created_at and updated_at sentinel for ordering document. These sentinel should work without any new index, ascending or descending order.
1 vote -
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 -
Add Linux platform support
What feature would you like to see?
I would like to see Firebase add official support for the Linux platform. This enhancement would allow developers to build applications that leverage Firebase services natively on Linux, enabling broader platform compatibility and empowering Linux-based applications.Why would it be useful?
Adding Linux support would:Enable developers to integrate Firebase services directly into Linux-based applications.
Provide parity with other supported platforms (e.g., iOS, Android, Web).
Open up Firebase's powerful features (e.g., authentication, cloud storage, Firestore) to a growing user base on Linux desktop and server environments.2 votes -
1 vote
- Don't see your idea?