776 results found
-
Crashlytics will report different stacks as different crash
Currently exception events are gathered as one issue depending solely on the actual exception location and its type.
Moreover, every such event pops all previous ones as regressed.
This makes it hard to follow the different issues. It is specifically a big problem where a fallback is used, with non-fatal crash reports in it. All crashes that ended up with the fallback are reported as one.
My suggestion is that different call stack and/or message will be shown as different issues. (Possibly with an option to set the differing place in the stack)2 votes -
Allow URLs to be accessible fully, or by invitation, or by password protection, like Notion and Figma
Allow natively what we can do in Notion / Figma (sharing a prototype), by sharing a page with the followings options:
1/ allow a page to be fully accessible (that's already possible, so the default)
2/ allow a page to be viewed only if we provide another User a link.
3/ allow a page to be viewed if 2/ + password protected11 votes -
Does Native Support for Authentication for EHR Providers like Epic and Cerner
Authentication is a difficult part of getting healthcare apps out there, and rightfully so, patient data security is hugely important. If Firebase offered this natively, not only would development be faster, but fewer mistakes/vulnerabilities would be present in healthcare apps that integrate with EHR.
1 vote -
2 votes
-
Firebase AppCheck (something like ReCaptcha Enterprise) for Expo React Native Android web app projects
How can I install Firebase AppCheck in my Expo React Native Android web app project? This app is deployed on Google play console registered as webapp on firebase.
ReCaptcha Enterprise
1 vote -
Unit tests for Python Firebase Functions
There should be unit testing for python functions like we have unit testing for typescript here: https://firebase.google.com/docs/functions/unit-testing.
3 votes -
Restrict Unauthenticated PURGE requests
At the moment Hosting is using Varnish cache which developers do not have access so they can't configure it, this leaves a small window for people to continuously Purge the page and increase the developer's usage
10 votes -
Firestore Index Name
As a Firestore project grows, so do the number of Composite Indexes.
While the fields are visible, being able to name a composite index would allow us to define which specific feature(s) a composite index is tied to, allowing us to remove unused indexes if they're no longer relevant.
9 votes -
should be able to sort data and select data with criteria on different fields
should be able to sort data and select data with criteria on different fields (the limitation section on https://firebase.google.com/docs/firestore/query-data/order-limit-data?hl=en&authuser=0)
2 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.5 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 -
Support hierarchical google-services.json
When you define multiple build types for your application you need to create a google-services.json file for each build type, eg : app/src/flavor1, app/src/flavor2, app/src/flavor_3
This becomes cumbersome when using multiple build flavors. It would be great if
1. the flavor directories acted as optional overrides of a default
2. the hierarchy for google-services.json respected initWith, e.. if I create a buildType1 with "initWith debug" I should be able to use the debug/google-services.json unless I try to overwrite it.4 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 -
Put the button to run a query on bottom not top in the console's query builder
In the console, after building a query in the query builder, one has to scroll up again and again to run it, it's an inconvenience when the query is long and has to be changed multiple times.
Putting the button at the bottom can make it easier to change and test out queries2 votes -
TTL for Realtime DB
Realtime DB is very similar to Redis functionality. It would be very valuable to enable real caching behaviour by adding time to live to an entry.
11 votes
- Don't see your idea?