1230 results found

1. 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.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  SDKs  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Allow Firebase project root to be configured independently of firebase.json location

   The Firebase CLI currently appears to treat the directory containing "firebase.json" as the effective root directory for the Firebase project.

   While "--config" allows "firebase.json" itself to be moved, moving the config file also changes how relative paths inside that configuration are resolved.

   This creates an awkward limitation for monorepos, where configuration files may naturally live in an infrastructure/configuration directory while build artifacts remain at the workspace root.

   It would be useful if the Firebase CLI allowed the configuration file location and the project root to be specified independently.

   Example

   Consider an Nx monorepo structured like this:

   repo/
   ├── apps/
   ├── libs/
   ├── dist/
   │ └── apps/
   │ └── web/
   ├── infrastructure/
   │ └── firebase/
   │ ├── firebase.json
   │ ├── firestore.rules
   │ ├── firestore.indexes.json
   │ └── storage.rules
   ├── nx.json
   └── package.json

   From an organizational standpoint, keeping Firebase-specific infrastructure under:

   infrastructure/firebase/

   is desirable.

   The CLI supports selecting that file:

   firebase deploy --config infrastructure/firebase/firebase.json

   However, if the Hosting configuration contains:

   {
   "hosting": {
   "public": "dist/apps/web"
   }
   }

   the path is effectively resolved relative to:

   infrastructure/firebase/

   rather than the actual workspace root.

   The build output produced by Nx is located at:

   repo/dist/apps/web

   so moving "firebase.json" also unintentionally changes the filesystem context of the Firebase project.

   Current workaround

   The practical workaround is to leave "firebase.json" at the workspace root:

   repo/
   ├── firebase.json
   ├── apps/
   ├── libs/
   ├── dist/
   └── infrastructure/
   └── firebase/
   ├── firestore.rules
   ├── firestore.indexes.json
   └── storage.rules

   and then reference Firebase-specific files from the root configuration.

   This works, but it means "firebase.json" becomes a special root-level file purely because its location controls the CLI's filesystem context.

   In larger monorepos, that makes Firebase configuration harder to organize consistently with other infrastructure.

   Proposed behavior

   It would be useful to provide a way to explicitly specify the Firebase project root separately from the config file.

   For example, a CLI option:

   firebase deploy \
   --config infrastructure/firebase/firebase.json \
   --project-root .

   or perhaps a configuration property:

   {
   "root": "../../",
   "hosting": {
   "public": "dist/apps/web"
   }
   }

   The exact API is less important than allowing these two concepts to be independent:

   1. Location of "firebase.json"
   2. Root directory used for resolving project-relative paths

   Why this matters

   This becomes particularly useful in monorepos using tools such as Nx, where:

   • application source lives under "apps/"
   • shared code lives under "libs/" or "packages/"
   • build artifacts are emitted to a workspace-level "dist/"
   • deployment/infrastructure configuration may live under "infrastructure/"

   In that structure, the location of a Firebase configuration file is an organizational concern and doesn't necessarily represent the root of the application workspace.

   Separating the config location from the project root would make Firebase CLI behavior more flexible without changing the existing default behavior.

   Backwards compatibility

   Existing behavior could remain unchanged when no explicit project root is supplied.

   For example:

   firebase deploy

   would continue using the directory containing "firebase.json" as it does today.

   Only users who explicitly provide a root would get the new behavior.

   Additional context

   I initially expected "--config" to control only which Firebase configuration file was loaded.

   The surprising part was discovering that relocating the configuration also effectively relocates the filesystem context used by Firebase.

   A separate root option would make "--config" much more useful for monorepo and infrastructure-oriented repository layouts.

   The Firebase CLI currently appears to treat the directory containing "firebase.json" as the effective root directory for the Firebase project.

   While "--config" allows "firebase.json" itself to be moved, moving the config file also changes how relative paths inside that configuration are resolved.

   This creates an awkward limitation for monorepos, where configuration files may naturally live in an infrastructure/configuration directory while build artifacts remain at the workspace root.

   It would be useful if the Firebase CLI allowed the configuration file location and the project root to be specified independently.

   Example

   Consider an Nx monorepo structured like this:

   repo/
   ├── apps/
   ├──… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firebase CLI  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Samuel

   Markus

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Agent Skills  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. photocraft.apk

   photocraft.apk इस एपी को बनाना, एपीके को बनाना है और इसमें फोटो सेल करके पैसा कम करना चाहते हैं.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  App Check  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Good App put on teachers and the liners

   This app is very very intelligent is good from teachers underlying all the student the healthy us from exam or question you can solve it

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Documentation  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. 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

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  SQL Connect (Data Connect)  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Realistic Car Simulators 2026

   Realistic Vehicles..
   Ai Stuff..
   Offline..
   Chat/Message..
   A Vehicle that you could touch the inside buttons..
   Remote control & all different kinds of Vehicles with a Key app/Startup/Starter..
   Actually Email & App Store Supporters..
   Worldwides- USA & others kinds of Cities & States & Towns & Countrysides..
   Rp- Role Play…
   Phone texts/call & others Stuff..
   Real life Simulators/Realistic one.. Similar to GTA five version..
   Players as npc & talking players & chat with..
   A Map/Gps on a Side we could see where to go while driving..
   Traffic jams..
   One More thing it’s should have
   iOS & others Version of all kinds of Phones-
   Old ones & new ones also a Laptop/Computers too..

   Realistic Vehicles..
   Ai Stuff..
   Offline..
   Chat/Message..
   A Vehicle that you could touch the inside buttons..
   Remote control & all different kinds of Vehicles with a Key app/Startup/Starter..
   Actually Email & App Store Supporters..
   Worldwides- USA & others kinds of Cities & States & Towns & Countrysides..
   Rp- Role Play…
   Phone texts/call & others Stuff..
   Real life Simulators/Realistic one.. Similar to GTA five version..
   Players as npc & talking players & chat with..
   A Map/Gps on a Side we could see where to go while driving..
   Traffic jams..
   One More thing it’s should have
   iOS & others Version of all kinds… more

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. 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.

   1. 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).

   1. 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

   Security & Scope (flagging sensitive keys or data exposed client-side)

   The engine ranks candidate implementations from Fastest / Most Efficient to Least Efficient, allowing developers to accept the optimal architecture with a single click.

   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.

   1. 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).

   1. 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

   … more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Agent Skills  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. car racing game

   Online Gaming Platform – Project Requirements Document

   1. Platform Name

   ---

   2. Project Objective

   The platform will provide a secure online gaming experience where users can create accounts, verify their identity, manage a digital wallet, and participate in games. The system will include secure payment processing, user verification, and fair gameplay mechanisms.

   3. User Registration

   • Full Name
   • Mobile Number
   • Email Address
   • Password
   • OTP Verification
   • Age Verification (where legally required)

   4. Identity Verification (KYC)

   • Government ID Upload
   • Selfie Verification
   • Mobile Number Verification
   • Email Verification
   • KYC Approval Status

   5. Digital Wallet System

   The platform will include a secure wallet that allows users to:

   • View Balance
   • View Transaction History
   • Deposit Funds
   • Withdraw Funds
   • Monitor Account Activity

   6. Payment System

   Supported payment methods may include:

   • Digital Banks
   • Mobile Wallets
   • Bank Transfers
   • Debit/Credit Cards

   All payment transactions will be processed through secure, encrypted channels.

   7. Gaming Features

   • Multiplayer Game Modes
   • Leaderboards
   • Ranking System
   • Match History
   • Fair Play System
   • Anti-Cheat Protection

   8. User Dashboard

   • User Profile
   • Wallet Balance
   • Game History
   • Achievements
   • Notifications
   • Account Settings

   9. Admin Panel

   • User Management
   • KYC Approval Management
   • Transaction Monitoring
   • Reports and Analytics
   • Security Monitoring
   • Customer Support Tools

   10. Security Features

   • Two-Factor Authentication (2FA)
   • Data Encryption
   • Secure Login System
   • Fraud Detection
   • Suspicious Activity Monitoring

   11. Legal & Compliance Requirements

   • Compliance with Local Laws
   • Privacy Policy
   • Terms and Conditions
   • Age Verification Requirements
   • Financial Compliance Standards

   12. Future Enhancements

   • Android Application
   • iOS Application
   • Live Chat Support
   • Referral Program
   • Tournament System
   • Multi-Language Support
   • AI-Based Security Monitoring

   Project Summary

   This project aims to build a modern, secure, and scalable online gaming platform with user registration, identity verification, digital wallet management, secure payment integration, fair gameplay systems, and a professional administration panel.

   Online Gaming Platform – Project Requirements Document

   1. Platform Name

   ---

   2. Project Objective

   The platform will provide a secure online gaming experience where users can create accounts, verify their identity, manage a digital wallet, and participate in games. The system will include secure payment processing, user verification, and fair gameplay mechanisms.

   3. User Registration

   • Full Name
   • Mobile Number
   • Email Address
   • Password
   • OTP Verification
   • Age Verification (where legally required)

   4. Identity Verification (KYC)

   • Government ID Upload
   • Selfie Verification
   • Mobile Number Verification
   • Email Verification
   • KYC Approval Status

   5. Digital Wallet System

   The platform will include a secure wallet that allows users to:

   • … more
   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firebase Studio  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Cancel Extensions Deprecation

    Continue offering the Extensions service, do not shut it down.

    Extensions are a core feature of Firebase, and the work required for customers to replace them is unacceptable.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Extensions  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. 44

    Edson

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  App Distribution  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Improve SEO Support for Content-Driven Websites

    I suggest that Firebase improve its support for content-driven websites by adding better SEO tools, enhanced static site optimization, and easier integration with search engines.

    I manage a gaming website called TomodachiLifeROM, where I publish game guides, tutorials, and gaming resources. Features such as built-in sitemap generation, improved metadata management, better structured data support, and more detailed performance recommendations would make Firebase Hosting even more useful for publishers.

    https://support.google.com/sites/thread/451587408?hl=en&sjid=16379941293809233418-EU

    It would also be helpful to have clearer documentation and examples for deploying SEO-friendly websites while maintaining excellent performance.

    Thank you for considering this suggestion.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Hosting  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. 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 Cloud Console, linked to the correct package name (com.washgo.mobile) and SHA-1
    - Play Integrity API enabled in Google Cloud Console
    - App Check status confirmed as "Monitoring" (not enforced, so not blocking requests)
    - SMS region policy set to "Allow" for Morocco
    - Google Play Internal Testing release published (versionCode 5), app installed via Play Store (not a development build)
    - Waited several hours between attempts to rule out temporary rate limiting

    Despite all of the above, real phone numbers (e.g. Moroccan numbers, +212...) still fail with error code 39 on every attempt, while test numbers configured in Firebase Console work without issue.

    This appears similar to reported issues:
    - https://github.com/firebase/firebase-js-sdk/issues/8955
    - https://github.com/firebase/flutterfire/issues/11565

    Could you please help us identify whether this is related to an anti-abuse mechanism blocking our project specifically, or another server-side configuration issue? We would appreciate any guidance on how to resolve this for production use.

    Thank you for your help.

    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… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Authentication  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. firebase init hosting:github environment secret

    The firebase init hosting:github command should support creating secrets for a GitHub environment for better security posture.

    https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/use-secrets#creating-secrets-for-an-environment

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase CLI  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. منصة تداول العملات الرقمية

    تطبيق لتداول الذهب والفضة والعملات المشفرة

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Cloud Functions for Firebase  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. usage is not acurate,

    just shows totals and i cannot see exactly at what time a read of documents was made, starting a scalable app is very frustrating when I can see 1K reads when my app it was even open, from where?, i just have one app and is in my phone, when I se monitoring I just can see group data, even worse the date is pacific time, even more confusing although I know to convert the timeline, I don't think is hard to show the local time right?

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firestore  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. We should be able to add more then 5 goals in a AB Test. Thats crucial for optimizers, i am sure you miss lots of customers because of it.
    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Test Lab  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. 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

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Remote Config  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. should add .bd domain.

    Firebase should add .bd domain extenstion. already info.bd is added. why not .bd?

    6 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Hosting  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Update new prefix MSISDN

    Dear Google,

    I contact from Movitel in Mozambique,
    Currently we deploy new Prefix +25888xxxxx for MSISDN , but it not yet update by google, to ensure services for customer when receive otp from google applicaition.
    I want to contact to need your help

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Authentication  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating