Skip to content

General

General

Categories

JUMP TO ANOTHER FORUM

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

2292 results found

  1. Hi all,

    We send Firebase app invitations only to our company domain emails, but the invitation email can be forwarded and accepted by a personal Gmail account, which creates a security concern.

    Is there a way to:

    Restrict invitation acceptance to only the Google account that received the email

    Or limit access to company-domain Google accounts only

    Prevent forwarded invitations from granting access to unauthorized users

    Any best practices or Firebase-supported solutions would be appreciated. Thanks!

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Improve firestore rules debug info:
    2 features will really improve the debugging of firestore rules:
    - Add a "label" parameter to the debug() function to identify the result in the debug log file of the emulator. Right now, only the value is printed, it is very confusing when you have several debug calls...
    - Improve the error message returned to the client so we can understand the permission denied. Right now the message contains very little information and it is not helpful a all..,

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. There is a very annoying limitation in the Firestore rules: you cannot convert a Set() to a List().

    This prevents a lot of possibility especially when using Map().diff().affectedKeys(): there is no way to access the first element for example.

    My use case is the following:
    On my client side, I am incrementing the value of a map element, ie:
    MapFieldValue resources;
    resources["gold"] = FieldValue::Increment(-amount);

    And on the rules side, I want to ensure that the resulting value is always positive (ie you cannot spend more gold than you have, even concurrently!):

    let updatedKeys = (resource.data.diff(request.resource.data).affectedKeys());
    return (updatedKeys.size() == 1 &&…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. how to manage ?

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. When typing messages in Gemini within Firebase Studio with a Japanese IME enabled,
    the Enter key pressed during text composition is incorrectly handled as message submission,
    which frequently causes accidental sends.

    While composing text, the Enter key should be used only to confirm conversion
    and must not trigger message submission.
    Please align this behavior with that of other common services.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Dear Sir, If I would that my project storage getting over 1gb . then it would be better. now the condition id that i have lost my world that I I made in this project. I cannot upgrade because my all card is not taking cor paying to get the blaze plan

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Analytics  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Additional to just a condition for allow read/write. I think firestore rule should be replaced with transform function. It should utilize pipeline operation and return document to read/write. So that it could force add field or change logic to generate some field on every document without redeploy client

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Add support for Agent Skills (https://agentskills.io/home).

    Skills is being supported by almost all the Agentic IDEs. For instance, tools such as Gemini CLI and Google Antigravity support Skills now.

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Deployment of apps in the firebase project has limited region options and middle east regions are not among them.

    Allowing the deployment of backend in these region will enable us to lower latency and use the cool firebase dashboards to manage the backend without having to go to GCP console often.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  App Hosting  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  App Check  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Now for iphone 16 and iphone 17, analytics only detect it as iphone, marketing name is null.
    It is hard to analyze user's device distribution.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Analytics  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Given apphosting supports multiple configured backends, it would greatly improve the emulator's utility to provide a mechanism to emulate all of them locally. With this feature in place firebase can support local emulation of apphosting and cloud run backends configured using hosting rewrite rules when deployed, which is a big win for supporting any number of microservices behind a single domain for integration testing and local dev. We'll still be responsible for implementing a local service discovery mechanism, but we'll have the convenience of just the emulator for spawning all our app processes.

    From the outside the feature looks like…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  App Hosting  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. An AI assistant designed to proactively guide users when they are stuck, offering contextual suggestions and actionable next steps in real time. Similar to Google AI Live or Google Gemini, it analyzes user intent and current state to surface relevant solutions, reduce friction, and help users move forward confidently without breaking their workflow.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Custom Dom should instantly hook on the app hosting

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  App Hosting  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. After deployment in firebase studio, app hosting require backend to rollout. However GitHub has to feed firebase console the code in repo. That request is now done manually and can miss critical steps that lead to frustration

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Firebase Studio right now offers basic code completion through its standard editor.

    Adding built-in AI-powered code completion could bring several new features:

    • Smart suggestions based on the code around it

    • Ability to generate multiple lines of code as you type

    • Understanding the purpose behind your code, like GitHub Copilot does

    • Compatibility with popular Firebase Studio languages such as TypeScript, JavaScript, Dart, and JSON

    Now developers have to depend on external extensions to access AI-based code completion. This disrupts their workflow when they work in Firebase Studio.

    Having built-in AI code completion would boost efficiency and turn Firebase Studio into a…

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?