1208 results found
-
Customise device name for Events DebugView's device selector
The device selector mentioned here: https://firebase.google.com/docs/analytics/debugview#device_selector consist of only generic device names (e.g. x86 64 for iOS simulator). For our app we can see many sessions (e.g. 6/8 right now) and all of them show "x86 64". It always takes few minutes to find "my" session for debugging.
It would be nice to have a way e.g. to customize device name (e.g. via Firebase API Analytics.setDeviceName("Przemyslaw's simulator")) so a developer could find their session immediately.6 votes -
Phone number for testing in firebase emulator
It would be great to be able to configure static MFA validation codes / phone numbers for testing in the emulator, like in the normal firebase auth product.
This would make testing an application with automated tests a lot easier.
6 votes -
Lazy loading of items in firebase console for firestore
Console has become laggy and returns a wait for page to load alert if a document has to many fields
6 votes -
Execution ID in logs generated by Firebase Functions v2
Logs generated by Firebase Functions v1 have the property
labels.execution_idthat can be used to correlate logs that pertain to the same execution. However, that property doesn't exist in logs generated by Firebase Functions v2. It's very important for debugging.6 votes -
Wildcard index exemptions
Firestore automatically indexes all fields in all collections adding to storage size and slowing write performance.
We can add single-field exemptions but we need to list all fields separately and there is a database-wide limit of 200 field exemptions.
In a highly optimised use case we would want to index only specific fields that we know we query on, and just exclude all others.
It's almost like the current behaviour is a database for novices, but we can't optimise for serious production.
We need either a wildcard exclusion, or effectively just a switch/setting that says "only fields with explicit index…
6 votes -
6 votes
-
6 votes
-
6 votes
-
6 votes
-
6 votes
-
6 votes
-
Evaluate Mutation Results in Realtime Refresh Conditions & Support Mutation-Side Triggers
Currently, when configuring a refresh condition on a query, the condition can only evaluate the triggering mutation's variables and auth (uid/token). We cannot check the actual result (response) of the mutation.
This creates a significant friction point when mutations are executed from non-client environments, such as a Cloud Function triggered by another backend service (e.g., Firebase Storage). Because the Cloud Function executes without the end-user's auth context, the only way to accurately filter the query refresh is to pass the userId into the mutation's variables. This feels like an unnecessary workaround just to satisfy the refresh condition.
To make real-time…
5 votes -
business
Making business account anything help him
5 votes -
firebase test files
Our app is a file manager, and it would be great to be able to test its functionality in Firebase Test Lab by providing some simple test files and directories. Without any files, the tests are relatively useless.
5 votes -
Review the Ai Coding Output
Review the code output of the built in Ai and Gemini 3.0 flash preview , i have recently created multiple new projects and then instructed gemini to produce my ideas and 9x/10 the app is somewhat built and with many errors and mistakes in the firebase code the app will only make it to a certin point and then suddenely it is destoryed forcing the ai to try to recover the damage it has no idea what its trying to fix and then instead of working on your own project your ai is trying to rebuild the firebase app infrastructure…
5 votes -
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.
5 votes -
Support 2nd generation (v2) Firebase Functions in Firebase Extensions
2nd generation Functions are better in every way and are recommended for almost all new Functions, but can't be used in Extensions (for most trigger types).
https://firebase.google.com/docs/extensions/publishers/functions
5 votes -
Firebase logIn with Phone Number
Comprobar que Firebase Authentication with phone funcione con todas las operadoras del país junto con recaptcha y appcheck
5 votes -
Realtime database console, usage tooltip scroll
If you have many RTDB instances, it's practically impossible to use the Usage tab in the console and view the tooltips. I have to scroll out to 25% in my browser, to see our current full list, and we may have more in the future. You should add a way to scroll the tooltip. I'm thinking: click graph, so you know which tooltip to show, and then make the tooltip static and scrollable. But it could be implemented however makes sense to the developers, as long as I can scroll down the tooltip and not have to zoom way out…
5 votes -
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.5 votes
- Don't see your idea?