1212 results found
-
A/B Testing is limited to 24 simultaneous experiments.
A/B Testing is limited to 24 simultaneous experiments. I want to run more experiment. How to increase the limit for concurrent experiment. Also I want to target all the users in same experiment (App= Android & iOS)
5 votes -
Manage minInstances setting of pinned functions of previous releases
Pinned functions of previous releases keep their minInstances setting. E.g. after deploying 10 times with a minInstances setting of 1, there will be 10 idling instances but only the newest revision handles all the traffic. Yet the remaining 9 instances' idle time is billed as well because the function is still addressable through the revision tag.
This also affects the maxInstances setting: With a maxInstances setting of 10, the newest Cloud Run revision which handles 100% of the traffic won't be able to scale anymore.
As far as I know, the only way to handle this right now is to…
5 votes -
I am not able get server key
Why it is Disabled?
5 votes -
List of all error codes in auth (Not the admin SDK)
Currently there is only a list of error codes the Admin SDK can receive, not for the web sdk.
5 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 -
Support "Continuing Uploads Across Process Restarts" on iOS
I work for a company that enable people to record sports using video and the storage footprint are often very huge (10GB+). While building an app for iOS, I notice that Firebase don't support continuing uploads across process restarts on iOS which is a major deal-breaker for continuing using Cloud Storage for Firebase.
I see support for this on Android and I will encourage you to add this to iOS in the future. Ref: https://firebase.google.com/docs/storage/android/upload-files#continuing_uploads_across_process_restarts5 votes -
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?
5 votes -
Login with WhatsApp
Just like phone auth, WhatsApp auth would be greatly beneficial for Asian markets. Users don't need to verify with OTP and us developers get access to their WhatsApp directly for promotion purposes.
5 votes -
Add Android Beta devices in TestLab
Before each new Production version, it would be nice to have available in Testlab the Beta version of each Android release.
For instance, as of now when this message is being written, I would like to run all the test suite against the new Android 14 beta using Testlab, but I can't.
5 votes -
Real-time updates for Cloud functions
With Firebase, you can have real time listeners on Firestore documents, which allow to have your UI in sync with your data.
But when you ship logic in an app, you lose control over it.
If you want to be able to update that logic after shipping, you place it in the backend (Cloud Functions), but then you lose real time updates.
It would be amazing to have functions that can fire real-time events based on Firestore updates.So the flow would be:
- There is an update in a Firestore document (or potentially other triggers like pub/sub, analitycs, etc.)…5 votes -
Configure logs save location
Configure where the log files for the emulator are saved, instead of poluting the root of the project
5 votes -
Support for WebAssembly in Cloud Functions
Many languages requested in other posts—Swift, Rust, Kotlin, etc.—can be implemented all at once by adding WebAssembly (WASM) and WebAssembly System Interface (WASI) to the list of Cloud Functions’s supported runtimes (and—importantly—supplying high-quality documentation).
5 votes -
App Check for Java Admin SDK
Verifying requests with Java Admin SDK would be very helpful for many servers using this language.
5 votes -
Allow input of analytics label on in-app messages like push notifications
Push notifications allow for an analytics label which makes sense for marketers who are running multi channel campaigns and want to aggregate results.
There is currently no way to add these to in app messages. Goal would be they are treated the same way as push notifications with simple reporting and pull through on the analytics for custom report building. Thanks
5 votes -
X-User-Country header when proxying to Google Cloud Run
App Engine and Cloud Functions send X-AppEngine-Country to app servers, which is useful for serving regional content to users.
Google Cloud Run doesn't receive the same headers. GCR can receive this header through load balancer custom headers (https://cloud.google.com/load-balancing/docs/https/custom-headers), but it'd be great if it were supported through Firebase Hosting directly without any extra configurations.
5 votes -
Option to enable MFA by provider
There should be an option to turn on MFA for a user for specific provider (e.g., password). Since user's Google signin might have MFA already, it's sort of inconvenient to have extra MFA barrier for Firebase Auth tenant.
5 votes -
MFA option to "remember device"
User shouldn't have to enter MFA every time logging in on same device. There should be a boolean option remember device for some period of time (somewhere between 2 weeks and forever)
5 votes -
Trusted headers for client IP address via Firebase Hosting
Context: from a backend running on Cloud Run/Cloud Functions, how to determine client IP address, when you need to TRUST it for IP-address based access restrictions.
You can normally find the real client IP as the first entry in the X-Forwarded-For header, but you cannot trust it.
If you are using Cloud Run (or Cloud Functions gen 2), then as far as I can tell the Cloud Run orchestrator always sits as a proxy in front of your container. This means you can trust the last entry in X-Forwarded-For as this is the client IP seen by Cloud Run itself.…
5 votes -
5 votes
-
5 votes
- Don't see your idea?