1239 results found
-
تطوير اللعبة
اللعبة ممتعةولكن عندما تزداد المساحة تتوقف اللعبة عن العمل فجئة ، ولا استطيع الدخول اليها ابدا ، نريد حلا مستعجلة رجاء
1 vote -
Introduce of PHP Admin SDK
This SDK will help developer, who wants to develop web/portal/application with PHP.
PHP is secure language if used properly, PHP Is not dead7 votes -
Integrate with Play Integrity Standard API
Current Firebase App Check is using the classic play integrity API, which results in rate limit easily. As a result, the token decode will fail easily as the QPS limit by play integrity api. Why not migrate to the Standard Play Integrity API which suggested by Google Play?
10 votes -
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!
22 votes -
تطبيق حجز مواعيد الأطباء وطلب الادويه
قيام التطبيق بالحجز عند الأطباء ورفع روشته المريض لطلب الادويه من الصيدليات
6 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 -
Bring back draft experiments in A/B Testing
The ability to save draft A/B tests in Firebase has disappeared. Preparing experiment variants, targeting rules, and parameters requires review and planning before launching.
Without drafts, we are forced to store all experiment setups, JSON payloads, and conditions externally in separate docs just to not lose them. This creates unnecessary overhead and risk of errors. Please bring back draft status so teams can prepare and collaborate on experiments directly in Firebase.
2 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 -
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.
3 votes -
To my business and identification
from datetime import date, datetime
import os
import json
import math
from pathlib import Path
import ollama=== PATHS ===
BASEDIR = Path(file).parent.parent # Personal-AI root
SYSTEMDIR = BASEDIR / "00-System"
IDENTITYDIR = BASEDIR / "01-Identity-Vault"
BUSINESSDIR = BASEDIR / "02-Business"
KNOWLEDGEDIR = BASEDIR / "03-Knowledge"
TASKSDIR = BASEDIR / "04-Tasks"
LOGSDIR = BASEDIR / "05-Logs"
RULESFILE = SYSTEMDIR / "AI-Rules.md"
EMBEDCACHEFILE = SYSTEMDIR / "embed_cache.json"Embedding model
EMBEDMODEL = "nomic-embed-text"
CHATMODEL = "llama3.1"
MAXFILES = 5…2 votes -
Firestore Enterprise, array indexes failure
In Firestore Enterprise, array indexes can be created in the index management view without throwing any errors or warnings. However, when executing queries that rely on array operations (such as array-contains or array-contains-any), the query engine completely ignores the created array index and falls back to a full table scan.
This creates significant issues for setups migrating from Firestore Standard, where array indexes are commonly used to handle multi-document references and array-based lookups.2 votes -
Куни
Лизание писечки
2 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 -
Parallel Server-Client Execution & AI Audit Engine for Web Workspaces
Concept Overview:
A three-column AI-native IDE interface designed to separate full-stack development into visual parallel execution layers with real-time performance auditing.- Three-Column Workspace Architecture:
Server-Side Column: Backend logic, database queries, edge functions, and server rendering (SSR/RSC).
Client-Side Column: UI state, interactive DOM updates, event listeners, and browser JS execution.
AI Alternatives Column: As you code, Gemini continuously suggests alternative routes (e.g., shifting heavy data transformations from client state to server queries).
- Real-Time "Audit" Engine: Clicking the Audit button runs an instant sandbox trace evaluating all implementations across three core metrics:
Execution Latency & Network Roundtrips
Client JavaScript Bundle Size Impact
…
3 votes
- Don't see your idea?