1244 results found
-
Data Connect Event Triggers on Emulator
Support Data Connect Event Triggers on emulator for local development. With the risk outlined in the event trigger documentation regarding infinite loops, we ought to be able to test our event triggers on emulator. Data Connect supports great local development except for the triggers, so this would be top notch!
21 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.
7 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…
5 votes -
photocraft.apk
photocraft.apk इस एपी को बनाना, एपीके को बनाना है और इसमें फोटो सेल करके पैसा कम करना चाहते हैं.
2 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…3 votes -
تطبيق حجز مواعيد الأطباء وطلب الادويه
قيام التطبيق بالحجز عند الأطباء ورفع روشته المريض لطلب الادويه من الصيدليات
5 votes -
Back up it
Interested
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”.
3 votes -
SQL Connect should support more postgreSQL constraints and indexes
Customers that have an existing schema with PostgreSQL or have product requirements that involve using more complex PostgreSQL features like CHECK constraints or partial indexes cannot use fdc because it tries to drop the schema and fails to start up.
There's partial support for this already via the brownfield setup guide but if constraints and indexes could be included this would unlock more use cases. https://firebase.google.com/docs/sql-connect/manage-services-and-databases#integrate-existing-databases
See the issue here https://github.com/firebase/firebase-tools/issues/10571
3 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.
3 votes -
Shadrack
import 'package:flutter/material.dart';
import 'package:firebasecore/firebasecore.dart';// Import the firebaseappcheck plugin
import 'package:firebaseappcheck/firebaseappcheck.dart';Future<void> main() async {
WidgetsFlutterBinding.ensureInitialized();
await Firebase.initializeApp();
await FirebaseAppCheck.instance.activate(
// You can also use aReCaptchaEnterpriseProviderprovider instance as an
// argument forwebProvider
webProvider: ReCaptchaV3Provider('recaptcha-v3-site-key'),
// Default provider for Android is the Play Integrity provider. You can use the "AndroidProvider" enum to choose
// your preferred provider. Choose from:
// 1. Debug provider
// 2. Safety Net provider
// 3. Play Integrity provider
androidProvider: AndroidProvider.debug,
// Default provider for iOS/macOS is the Device Check provider. You can use the "AppleProvider"…1 vote -
Rap drill
Des musiques social et spirituels pour motiver et faire réfléchir les gens
Vidéo alléchantes3 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
4 votes -
44
Edson
2 votes -
WEIRD LOOKING LONG VERIFICATION LINKS
This concerns the verification links. Since we cannot edit the HTML body directly, the long default Firebase links can look intimidating to users, making them hesitant to click. Would it be possible for Firebase to format these links as buttons by default across the platform? I believe this improvement would be highly beneficial for many developers and users.
1 vote -
Our Project has been suspended last two days
Our Project is suspended from last two days and has been restored yet..
2 votes -
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…
17 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...
3 votes -
I dislike your new UI for A/B testing; it's extremely difficult to use. Configurations aren't readily apparent; the page shrinks to the righ
I dislike your new UI for A/B testing; it's extremely difficult to use. Configurations aren't readily apparent; the page shrinks to the right sidebar, which is visually unpleasant. New configurations can't be created immediately, unlike in the previous mode. Starting a test requires creating a new condition; otherwise, the test won't be at the highest priority under the same configuration, and users will end up using other conditions within the same configuration. It's difficult to use, very difficult to use.
2 votes -
First-class Firebase SDK support for Kotlin/Wasm and Compose Multiplatform Web
Please add first-class Firebase SDK support for Kotlin/Wasm, especially for Compose Multiplatform Web apps.
Kotlin/Wasm is becoming an important target for sharing Kotlin and Compose UI across Android and Web. Today, Firebase works well on Android and through the JavaScript SDK on Web, but Kotlin/Wasm integration is still awkward and requires wrappers, JS interop, REST calls, or platform-specific abstractions.
It would be very useful to have official support for Auth, Remote Config, Realtime Database, Firestore, Analytics, and Storage from Kotlin/Wasm.
2 votes
- Don't see your idea?