2315 results found

1. Firebase studio app
   5 votes

   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  ·  Firebase Studio  ·  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. Firebase Auth with IP address whitelist & blacklist

   Blacklist scenario: Let's say that a device is detected for fraud/scam activity. I want to blacklist the device for 1 year based on the previously logged-in IP address, so the scammer is no longer able to use their devices. Even though the scammer created a new Firebase account, they won't be able to do that because of the IP address blacklist.

   Whitelist scenario: Let's say that I have an internal app. I want this app to be used by my employees only, so only specific devices are allowed to login.

   3 votes

   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  ·  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. Let Gemini see your firebase screen

   Often it has given steps but have been out of date. Example: "My memory of the Google Cloud interface was incorrect.". i end up having to copy and paste my screen, so Gemini can see what i am looking at.

   5 votes

   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  ·  Firebase Studio  ·  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. Better Github integration

   Automatically pushes to GitHub when Gemini makes changes. Also make it where you don't have to re authenticate so often with GitHub.

   3 votes

   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  ·  Firebase Studio  ·  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. studio

   vamos con seguridad para ariba, gracias al creador

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

6. I suggest that Firebase improves error messages to be more clear and beginner-friendly, especially for new developers.

   As a beginner, I often feel confused when errors appear. Clearer and more descriptive error messages in the Firebase console would help users understand problems faster without searching elsewhere

   0 votes

   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  ·  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

7. ☆☆☆☆☆

   Excellent

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

8. I want to make my website but i don't have a money to pay now give me a free trial for month if i get money then i pay

   Free trial

   1 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  ·  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. Add topic subscription from PWA Javascript app

   Hi,
   It would be very helpful if a user could be automatically enrolled in an FCM topic when they log in to the PWA using a VAPID key.
   Currently, when I generate the token at login, it's saved in the Firebase Realtime database in the /fcmTokens path. The problem is that this process is very data-intensive: the ESP8266 must read all the tokens in /fcmTokens and send notifications individually, resulting in a significant increase in handshaking, SSL, and device heap memory traffic. This would not happen if Firebase added topic subscriptions/unsubscriptions from PWAs.

   3 votes

   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  ·  Cloud Messaging  ·  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. Add MQTT protocol for lightweight communication with IoT devices RealTime Database and Authentication

    Ciao,
    Attualmente sto inviando dati da dispositivi ESP8266 a Firebase Realtime Database utilizzando la libreria:
    https://github.com/mobizt/FirebaseClient

    Tuttavia, ho riscontrato un problema importante: ogni invio di dati consuma molto traffico Firebase a causa dell'handshake SSL (molto pesante per ESP8266) richiesto per ogni connessione. Questo rende l'integrazione con dispositivi IoT a basso consumo con connettività limitata molto inefficiente.

    Per questi motivi, sarebbe estremamente utile e vantaggioso avere il supporto nativo per un protocollo più leggero e ottimizzato per l'IoT, come MQTT, che ridurrebbe drasticamente l'overhead, il consumo di dati e la latenza, migliorando significativamente l'esperienza utente della piattaforma nell'ambiente IoT.

    Firebase è un'ottima soluzione, ma l'aggiunta di MQTT la renderebbe davvero completa, anche per i casi d'uso IoT più sensibili alla rete.

    Cordiali saluti,
    Sebastiano La Tona

    Ciao,
    Attualmente sto inviando dati da dispositivi ESP8266 a Firebase Realtime Database utilizzando la libreria:
    https://github.com/mobizt/FirebaseClient

    Tuttavia, ho riscontrato un problema importante: ogni invio di dati consuma molto traffico Firebase a causa dell'handshake SSL (molto pesante per ESP8266) richiesto per ogni connessione. Questo rende l'integrazione con dispositivi IoT a basso consumo con connettività limitata molto inefficiente.

    Per questi motivi, sarebbe estremamente utile e vantaggioso avere il supporto nativo per un protocollo più leggero e ottimizzato per l'IoT, come MQTT, che ridurrebbe drasticamente l'overhead, il consumo di dati e la latenza, migliorando significativamente l'esperienza utente della piattaforma nell'ambiente IoT.

    Firebase è… more

    4 votes

    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  ·  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

11. Native Firebase Mobile App (Android & iOS)

    I suggest that Firebase creates an official native mobile app for Android and iOS to manage projects, view analytics, logs, Firestore data, and Auth users. The web UI and PWA experience on mobile is slow and difficult to use.

    3 votes

    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  ·  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. Add command to check Firebase CLI authentication status without triggering reauth

    Currently, the Firebase CLI does not provide a way to proactively check whether the user’s authentication state is still valid. Authentication validity is only discovered when running a command that requires auth, at which point the CLI may fail and instruct the user to run firebase login --reauth.

    This makes it difficult to:
    • Detect impending or current auth expiration ahead of time
    • Build scripts or tooling that can validate environment readiness
    • Provide a better UX in local development workflows
    • Perform lightweight “health checks” without risking mid-command failure

    Problem
    There is no supported command such as:
    • firebase login:status
    • firebase auth:check
    • or similar

    The only way to determine auth validity today is to run a real command (e.g. firebase projects:list) and handle a failure, which is reactive and indirect.

    Proposed Solution
    Introduce a command that checks CLI authentication status without performing a project operation, for example:

    firebase login:status

    Possible behaviors:
    • Exit code 0 if credentials are present and refreshable
    • Exit code 1 if credentials are missing, expired, or require reauthentication
    • Optional human-readable output, e.g.:
    • “Authenticated (user@example.com)”
    • “Authentication expired — run firebase login --reauth”

    Optional enhancements:
    • --json output for scripting
    • Indicate auth method (user OAuth vs service account)
    • Indicate whether silent refresh succeeded

    Why this would be useful
    • Improves developer experience
    • Enables deterministic preflight checks in scripts
    • Reduces surprise failures during deploys
    • Aligns with similar tooling (gcloud auth list, aws sts get-caller-identity, etc.)

    Scope clarification
    This request is specifically about Firebase CLI authentication, not Firebase Auth sessions or Admin SDK behavior.

    Alternative workaround (current)
    Running a harmless command like firebase projects:list is currently the only way to infer auth state, but this is indirect and not ideal.

    Currently, the Firebase CLI does not provide a way to proactively check whether the user’s authentication state is still valid. Authentication validity is only discovered when running a command that requires auth, at which point the CLI may fail and instruct the user to run firebase login --reauth.

    This makes it difficult to:
    • Detect impending or current auth expiration ahead of time
    • Build scripts or tooling that can validate environment readiness
    • Provide a better UX in local development workflows
    • Perform lightweight “health checks” without risking mid-command failure

    Problem
    There is no supported command such as:
    •… more

    2 votes

    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  ·  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. Update the knowledgebase of Gemini to stop using 1.5 versions

    Every time It uses or create a google cloud function it uses 1.5 versions. Even if I tell it specifically not to use and use a 2.5 version it keep using it. Please update the knowledge of the tool to avoid connecting to outdated apis.

    5 votes

    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 AI Logic  ·  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. Access user agent of the client

    App hosting replaces user agent header of the client, with "Google"
    I need to access user agent to modify responses according to user's operating system.

    3 votes

    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  ·  App 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

15. application based templates

    Provide more application based templates using modernized AI and Web frameworks for static web pages, chatbot, web information search and summarization tools, so designers can focus on concepts instead of debugging infrastructure code.

    5 votes

    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  ·  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. I need a breakthrough

    Do something better in future before that I need to learn something about this 😞

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

17. সাইন-আপ

    সাইন-আপ

    1 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  ·  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 Request – Firebase Studio Preview & Environment Variables Subject: Firebase Studio Preview does not allow setting custom environmen

    Support Request – Firebase Studio Preview & Environment Variables

    Subject: Firebase Studio Preview does not allow setting custom environment variables (Admin SDK / Service Account issue)

    Hello Firebase Studio Support Team,

    I’m using Firebase Studio (Cloud Workstations) with a Next.js (App Router, Server Actions) project that uses Firebase Admin SDK to write to Firestore.

    I’m encountering a blocking issue with environment variable management in Firebase Studio Preview.

    🔍 Problem Description

    My application requires a service account to initialize Firebase Admin SDK.
    Normally this is done via an environment variable such as:

    FIREBASESERVICEACCOUNT_KEY=<base64-encoded service account JSON>

    However, in Firebase Studio Preview:

    There is no UI or documented way to define custom environment variables or secrets

    Preview automatically injects GOOGLEAPPLICATIONCREDENTIALS

    This causes Admin SDK to fall back to Application Default Credentials (ADC)

    ADC fails in Preview with errors like:

    Getting metadata from plugin failed
    Could not refresh access token (HTTP 500)

    Even when using dotenv or runtime logic, this cannot be overridden because the env is injected before the Node process starts.

    📜 What I Tried

    Removing GOOGLEAPPLICATIONCREDENTIALS from .env

    Forcing credentials in code (cert(serviceAccount))

    Using dotenv

    Using Firebase CLI (functions:config:set)

    Restarting / rebuilding Preview

    Searching for Preview env / secrets configuration

    None of these allow injecting a custom env variable into the Preview runtime.

    ❓ Questions

    Is it currently supported to define custom environment variables or secrets for Firebase Studio Preview?

    If yes, where is this documented or configured?

    If not, is there a recommended workflow for projects using:

    Next.js Server Actions

    Firebase Admin SDK

    Firestore writes

    Is Preview intended only as a frontend-only viewer, not a backend runtime?

    🎯 Impact

    This limitation prevents:

    Testing Admin SDK logic

    Firestore write operations

    Any backend logic that depends on secure credentials

    At the moment, the only working solution is local development or Cloud Run/App Hosting, which defeats the purpose of Preview for full-stack apps.

    Thank you for your help.
    Clarification or documentation on this would be very valuable.

    Best regards,
    Murat

    Support Request – Firebase Studio Preview & Environment Variables

    Subject: Firebase Studio Preview does not allow setting custom environment variables (Admin SDK / Service Account issue)

    Hello Firebase Studio Support Team,

    I’m using Firebase Studio (Cloud Workstations) with a Next.js (App Router, Server Actions) project that uses Firebase Admin SDK to write to Firestore.

    I’m encountering a blocking issue with environment variable management in Firebase Studio Preview.

    🔍 Problem Description

    My application requires a service account to initialize Firebase Admin SDK.
    Normally this is done via an environment variable such as:

    FIREBASESERVICEACCOUNT_KEY=<base64-encoded service account JSON>

    However, in Firebase… more

    2 votes

    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  ·  Firebase CLI  ·  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. Add devices running iOS 17 and 18 in Test Lab

    The newest iPhone model and iOS version available to run in Test Lab is an iPhone 14 Pro running iOS 16.6. With iOS 18 recently released, it would be great to have support for newer devices (iPhone 15 and 16 models) running the newest iOS versions (17.x and 18.x).

    54 votes

    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

    8 comments  ·  Test Lab  ·  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. Wander

    All products and services are best, secure and safe to be used by users.

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