666 results found
-
Linear integration
When a crashlytics issue occurs, it creates a new issue in linear with a link to the crashlytics dashboard.
When a crashlytics issue is closed, close the associated issue in linear.
When a linear issue is closed, close the associated issue in crashlytics.
When a crashlytics issue receives velocity alerts, it increases issue priority in linear.2 votes -
12 votes
-
12 votes
-
13 votes
-
13 votes
-
Full terraform support
As DevOps engineer i have a lot pain to setup Firebase project. We should have infrastructure as a code for provide right engineering experience.
10 votes -
Hosting CDN cache stale-while-revalidate
Time-to-first-byte from Firebase Functions is usually slow (more than 500ms) even without cold start, sometimes (with cold starts) TTFB becomes absolutely unacceptable for projects where performance is important. SSRed HTML is also not Brotli compressed as static files.
This is a really big problem to deploy SSR web apps to Firebase IMO, and cache SWR at the CDN layer (edge) would solve it perfectly.5 votes -
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 -
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 -
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 -
Streaming
To implement userfriendly generative AI applications it is import to stream data produced by LLMs back to the users browser. Firebase currently buffers all content and only returns when data is complete. Is the firebase team planning to implement this?
4 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 -
Add API to make it easy to build rate limiting in HTTPS functions
It would be awesome with some kind of helper built on memcache to allow rate limiting on user defined parameters.
E.g. if I build a webservice that can access an 'account' concept that I have modelled with some kind of access token I have modelled, then it would be nice to add rate limiting rules for either the specific access token or the entire account.
11 votes -
12 votes
-
12 votes
-
Download the uploaded .ipa and apk file from App Distribution
- In the Firebase CLI
- In the Firebase Console
12 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
-
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
- Don't see your idea?