1232 results found
-
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.
6 votes -
Firebase CLI: allow overriding local Emulator ports via command-line flags
Emulator ports can currently only be configured statically in the "emulators" block of firebase.json (or interactively via "firebase init emulators"). There is no way to set or override a port at invocation time.
This is especially painful in CI and parallel test runs: running multiple emulator suites concurrently (e.g. sharded test jobs on one runner) requires generating a distinct firebase.json per shard just to change port numbers.
A good solution are optional, per-emulator port flags on emulators:start and emulators:exec that override the corresponding firebase.json values, for example:
firebase emulators:start --firestore-port 8081 --auth-port 9098 --functions-port 5002 --ui-port 4001Precedence: CLI flag…
4 votes -
photocraft.apk
photocraft.apk इस एपी को बनाना, एपीके को बनाना है और इसमें फोटो सेल करके पैसा कम करना चाहते हैं.
1 vote -
تطبيق حجز مواعيد الأطباء وطلب الادويه
قيام التطبيق بالحجز عند الأطباء ورفع روشته المريض لطلب الادويه من الصيدليات
4 votes -
39
Subject: Phone Auth - Real numbers failing with error code 39 despite correct configuration (Blaze plan)
Project ID: washgo-1582e
We are experiencing a persistent issue with Firebase Phone Authentication on Android (React Native / @react-native-firebase/auth). Test phone numbers work correctly, but real phone numbers consistently fail.
Error observed:
[auth/unknown] An internal error has occurred. [ Error code:39 ]Steps already taken:
- Firebase project upgraded to Blaze (Pay-as-you-go) plan
- App signing key SHA-1/SHA-256 (Play App Signing) added to Firebase Console
- Upload key SHA-1/SHA-256 also added to Firebase Console
- OAuth 2.0 Client ID (Android) manually created in Google…2 votes -
Support bulk deletion of completed Remote Config A/B Testing experiments
Firebase currently limits projects to 300 experiments. Teams that run frequent A/B tests eventually reach this limit. The Firebase Console only allows deleting completed experiments one by one, which becomes extremely time-consuming. Please add:
- multi-select with checkboxes;
- “Delete selected”;
- optionally “Delete all completed experiments”.
2 votes -
Allow the App Testing Agent to persist user state between test runs
It would be great if the App Testing Agent could persist a user session or saved app state between test runs. This would allow tests to start from a predefined state instead of always going through the onboarding or login flow, making it much easier and faster to test authenticated features and later stages of the app.
2 votes -
Rap drill
Des musiques social et spirituels pour motiver et faire réfléchir les gens
Vidéo alléchantes2 votes -
views on data
Firestore should support a simple language like the rule language that allows modifying the data before sending it to clients.
The primary use case is changing or hiding some fields depending on the auth uid
3 votes -
Production Multi-Provider Integration Scheme For production readiness, for the Google IO 2027 release
Production Multi-Provider Integration Scheme For production readiness, for the Google IO 2027 release a service that after staring into your devices camera for 20 seconds will log you into any account email platform or social media that's ever log your face and stored it in the cloud
3 votes -
44
Edson
1 vote -
Alert on live activity updates
Live Activity pushes are meant to be completely silent background updates, so Firebase’s requirement for an alert field is technically incorrect and creates unnecessary sound/vibration issues.
When sending APNs messages with "apns-push-type": "liveactivity" via Firebase Cloud Messaging (FCM), the service currently requires an "aps.alert" field to be present in the payload.
However, Live Activity updates are designed by Apple to be silent background updates, they should not display alerts, play sounds, or trigger any user-visible notification behavior.
Because FCM enforces the presence of "aps.alert", developers are forced to include dummy or empty alert values (e.g. "alert": {}), which can still…
15 votes -
App Distribution should have at least basic management of email notifications
There is no option to set email preferences for tester groups in Firebase App Distribution. It is unnecessary to pester everyone with emails when they can find the last app version in App Tester.
59 votes -
Table Event Triggers
In additional to the
onMutationExecuted, we would love to have events on table mutations.onRowUpdatedonRowCreatedonRowDeleted
onMutationExecutedis already launched in Nov 2026. https://firebase.blog/posts/2025/11/dataconnect-nov2511 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
6 votes -
publish a GCP / firebase documentation MCP server
Enable fetch and query tools in an MCP server for the whole GCP, or the firebase documentation.
11 votes -
restore old firestore browser behavior where only part of long entries where visible.
restore old firestore browser behavior where only part of long entries where visible. Now when browser show entire value of props usability dropds to ZERO for any recored with long texts of maps...
2 votes -
103605920
5.000$
2 votes -
Provide Native Document Counters and Metadata for Firestore Collections
Problem:Currently, finding the total number of documents inside a Firestore collection requires building custom client-side listeners or cloud functions to maintain manual counter fields. This adds boilerplate code, introduces latency, and risks running into write rate limitations unless complex distributed counters are built.Proposed Solution:Firebase should provide an out-of-the-box, native SDK method (e.g., a simple client-side function) that securely requests the exact document count from the server's index layer without needing to download, fetch, or bill for individual document data payloads.Why this matters:This feature is critical for building cheap, efficient pagination UI, analytics dashboards, and status trackers without incurring massive read…
2 votes -
More information in errors for native sql statements
Errors in native sql statements like in _execute always result in the same "Invalid SQL statement" error without any further information, which makes it really difficult to debug. More data - for example the part of the SQL statement that is invalid - would be really helpful! Especially as this error also seems to be thrown when the SQL is perfectly fine but a wrong _execute syntax is used, which should not throw an "Invalid SQL statement" error, as it is not about SQL!
2 votes
- Don't see your idea?