1241 results found
-
Restrict Firebase App Invitations to Only the Intended Google Account (Prevent Forwarded Email Access)
Hi all,
We send Firebase app invitations only to our company domain emails, but the invitation email can be forwarded and accepted by a personal Gmail account, which creates a security concern.
Is there a way to:
Restrict invitation acceptance to only the Google account that received the email
Or limit access to company-domain Google accounts only
Prevent forwarded invitations from granting access to unauthorized users
Any best practices or Firebase-supported solutions would be appreciated. Thanks!
2 votes -
Improve firestore rules debug info
Improve firestore rules debug info:
2 features will really improve the debugging of firestore rules:
- Add a "label" parameter to the debug() function to identify the result in the debug log file of the emulator. Right now, only the value is printed, it is very confusing when you have several debug calls...
- Improve the error message returned to the client so we can understand the permission denied. Right now the message contains very little information and it is not helpful a all..,3 votes -
Allow to convert a Set() to a List() in the Firestore rules
There is a very annoying limitation in the Firestore rules: you cannot convert a Set() to a List().
This prevents a lot of possibility especially when using Map().diff().affectedKeys(): there is no way to access the first element for example.
My use case is the following:
On my client side, I am incrementing the value of a map element, ie:
MapFieldValue resources;
resources["gold"] = FieldValue::Increment(-amount);And on the rules side, I want to ensure that the resulting value is always positive (ie you cannot spend more gold than you have, even concurrently!):
let updatedKeys = (resource.data.diff(request.resource.data).affectedKeys());
return (updatedKeys.size() == 1 &&…1 vote -
Seems list everything
Dear Sir, If I would that my project storage getting over 1gb . then it would be better. now the condition id that i have lost my world that I I made in this project. I cannot upgrade because my all card is not taking cor paying to get the blaze plan
1 vote -
firestore pipeline as rulev3/transformation
Additional to just a condition for allow read/write. I think firestore rule should be replaced with transform function. It should utilize pipeline operation and return document to read/write. So that it could force add field or change logic to generate some field on every document without redeploy client
2 votes -
Make App Hosting available in Doha and Dammam region (me-central)
Deployment of apps in the firebase project has limited region options and middle east regions are not among them.
Allowing the deployment of backend in these region will enable us to lower latency and use the cool firebase dashboards to manage the backend without having to go to GCP console often.
3 votes -
Look into Gemini Ai as well as Google Ai concentrate on permissions and time ie. Min, hour etc etc
Look into Gemini Ai as well as Google Ai
8 votes -
Update iphone 16 and iphone 17 mapping for device information
Now for iphone 16 and iphone 17, analytics only detect it as iphone, marketing name is null.
It is hard to analyze user's device distribution.4 votes -
Support an array/object in firebase.json "emulators"."apphosting" to run multiple apphosting backends at once
Given apphosting supports multiple configured backends, it would greatly improve the emulator's utility to provide a mechanism to emulate all of them locally. With this feature in place firebase can support local emulation of apphosting and cloud run backends configured using hosting
rewriterules when deployed, which is a big win for supporting any number of microservices behind a single domain for integration testing and local dev. We'll still be responsible for implementing a local service discovery mechanism, but we'll have the convenience of just the emulator for spawning all our app processes.From the outside the feature looks like…
1 vote -
Custom domain
Custom Dom should instantly hook on the app hosting
4 votes -
Change "apphosting"."ignore" behavior in firebase.json to apply the configured paths from the directory holding firebase.json
I always run my firebase projects as monorepos since they typically incorporate several distinct apps with shared deps. I use my own CI/CD pipeline because the apphosting default is not flexible enough.
When deploying apphosting using the CLI, there is a size limit on the zipped bundle. If the "ignore" behavior would allow me to ignore directories from the project root I wouldn't have problems, but since it's relative to the apphosting "rootDir" I don't have a way to use my entire monorepo for integration testing, etc and then ship my apphosting project using
firebase deploybecause the entire monorepo…1 vote -
1 vote
-
Firebase Auth with IP address whitelist & blacklist
Blacklist scenario: Let's say that a device is detected for fraud/scam activity. I want to blacklist the device for 1 year based on the previously logged-in IP address, so the scammer is no longer able to use their devices. Even though the scammer created a new Firebase account, they won't be able to do that because of the IP address blacklist.
Whitelist scenario: Let's say that I have an internal app. I want this app to be used by my employees only, so only specific devices are allowed to login.
6 votes -
Add Native Invitation Email Flow for Firebase Authentication (Multi-Tenant Apps)
In many multi-tenant applications, an invitation is a time-limited, one-time handshake between two parties inside an app context (e.g. organization, workspace, team, or document).
After the invitation email is accepted, the link should bring the recipient into the app at a specific contextual entry point (for example, a workspace, organization, or document reference). From that point:
Existing users continue through the regular sign-in flow (if not already signed in)
New users continue through the standard sign-up flow
At that point, the application takes full control of the user experience and logic.
From Firebase’s perspective, the responsibility would primarily be to…
1 vote -
Cannot create event on edge
Cannot create event on edge
1 vote -
Elidiannys
Ffffff
1 vote -
Save phone
Idea save
1 vote -
Figure out a way to make menus/options User Friendly - I tried setting up Email Trigger in an APP - maybe I will get it figured out a year f
Fix the menu process flow for set-up - think like a user instead of a Nerd Progrmmer or enable Gemini to do some work for users
1 vote -
Türkçe dil destegi istiyoruz
Türkçe dil desteği istiyoruz ugulamayı daha iyi kullanmak için yoksa silmeniz gerekecek
1 vote -
Session Management & Device Visibility for Firebase Authentication
Add optional session management to Firebase Authentication that creates and tracks individual login sessions per user, allowing developers/users to view active sessions with device and operating system information (derived from the User-Agent), approximate location (city/country), session creation time, and last active timestamp. The feature would enable per-device logout and selective session revocation via the Firebase Admin SDK, with optional read-only access for clients to build “logged-in devices” security UIs, while remaining privacy-safe, opt-in, and configurable without exposing raw IP addresses or User-Agent strings.
View Complete Proposal/Request here: https://gist.github.com/12fahed/42e802890b5b887b93c66d94ceadeb2d
42 votes
- Don't see your idea?