1222 results found

1. "Verify Email Address" page should be translated

   We notice an inconsistency where the initial Firebase email verification page displays in English (the one with the 'Complete verification' button), despite the URL containing the lang=fr parameter, while the final success message correctly appears in French.
   This appears as a bug.

   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

2. 3P model support

   Firebase should have support for non-Gemini Models (non-Google) as well.

   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 AI Logic  ·  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. Provide proper sorting for the firebase cloud functions table UI

   Provide proper sorting for the firebase functions table UI, ideally persisted on localStorage, it could allow us to sort by trigger, by name, by ..., just to make the table easily visually consumed and help users find their http triggers with ease (to copy paste, I find my self lost on my list many times)

   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

4. Data

   Assets

   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

5. Punycode domain support ✌🏻

   The hosting product support punycode domain but App Hosting doesn't which is kind of odd. Please bring App Hosting to the same domain support parity with the Hosting product. Thank you!

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

6. Configure to redirect system domains (...web.app) to primary domain.

   Problem
   Firebase Hosting currently serves content simultaneously across three URLs: a custom domain (e.g., site.example.org) and two system domains (project.web.app and project.firebaseapp.com). This creates duplicate content issues for SEO and fragmenting analytics.

   Proposed Solution
   Allow users to designate a Primary Domain within the Firebase Console. Once set, all requests to the default system domains should automatically trigger a 301 redirect to the primary custom domain.

   Key Requirements
   * Automatic Redirection: System domains (web.app / firebaseapp.com) should mirror the "Redirect" functionality already available for custom domains.
   * SEO Optimization: Consolidate page rank by ensuring only one canonical URL exists.
   * Configuration: A simple toggle or dropdown in the Hosting "Domains" tab to "Redirect system domains to [Custom Domain]."

   Problem
   Firebase Hosting currently serves content simultaneously across three URLs: a custom domain (e.g., site.example.org) and two system domains (project.web.app and project.firebaseapp.com). This creates duplicate content issues for SEO and fragmenting analytics.

   Proposed Solution
   Allow users to designate a Primary Domain within the Firebase Console. Once set, all requests to the default system domains should automatically trigger a 301 redirect to the primary custom domain.

   Key Requirements
   * Automatic Redirection: System domains (web.app / firebaseapp.com) should mirror the "Redirect" functionality already available for custom domains.
   * SEO Optimization: Consolidate page rank by ensuring only one… 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  ·  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

7. Firebase is currently awful... It doesn't even look like a Google service.

   Firebase TLDR:

   UI?
   Trash
   Pricing?
   Trash... Cloudfare can do it for free.
   User experience?
   One of the worst system interface I have ever used in my entire life. I tested a few apps and got charged for testing a Alpha game for 2 days with a few friends, what I would've paid for a VPS for a whole month with unlimited amount of bandwidth.

   This plataform does NOT feel like a Google service. And I am NEVER going to use this **** ever again. Feels that I just got scammed for real.

   Firebase = Trash company. I hope Google finds it out before this ruins Google Optimal reputation.

   All Google's services are Excelent, literally ALL... except Firebase.

   Firebase TLDR:

   UI?
   Trash
   Pricing?
   Trash... Cloudfare can do it for free.
   User experience?
   One of the worst system interface I have ever used in my entire life. I tested a few apps and got charged for testing a Alpha game for 2 days with a few friends, what I would've paid for a VPS for a whole month with unlimited amount of bandwidth.

   This plataform does NOT feel like a Google service. And I am NEVER going to use this **** ever again. Feels that I just got scammed for real.

   Firebase = Trash company. I hope Google finds… 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  ·  Other  ·  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. If This firebase..is for protecting my Google Ads by YouTube is.. good..but idont know what i do to get its shown.. i got YouTube Creati

   Iwant to used Google Ads.by YouTube channel and YouTube creations Apps and music studio channel us all in one YouTube page channel... I hope you're understand what I'm trying to say... that's all thank you for your.. understanding..

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

9. The login to develop console only display the WeChat

   When I press the login button on https://firebase.google.cn/docs/crashlytics/android/get-started-ndk?authuser=9&hl=en
   It displays the QR code to login with Wechat. But I'm not in China and I don't have wechat account.

   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  ·  Other  ·  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. Yourtelent studio-8891325219•Accessed 1 hour ago

    Mujhe ek YouTube se Milta julta Ek app banana hai uski link Maine Upar Dal Di Haiuski link Maine Upar Dal Di Hai

    0 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

    0 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

11. Native support for RBAC (Role-Based Access Control)

    Native RBAC (Role-Based Access Control) management
    Currently, to manage roles (admin, editor, client), you have to use Custom Claims via the Admin SDK (Node.js) or store the roles in Firestore. This is cumbersome for a beginner.

    The improvement: Being able to define roles directly from the Firebase console and have them automatically appear in the request.auth object of Security Rules without additional code.

    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

12. let developer enforce schema if wanted on the serverside

    provide an option for the developer enforce a schema in the firebase console. At least on the firestore enterprise edition. Mongo Atlas had this offering. rightnow, we are having to manage schema at the app level and then again at the cloudfunctions level. Making it hard to manage.

    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

13. Improve Firebase Auth integration with Server side rendering (Next.js)

    Hey, hi, I’m a Next.js developer, and the only problem I’m having with Firebase is with the Firebase Auth integration. I’d like to see improvements to the documentation for Next.js and its integration with server-side rendering. The problem I’ve encountered is that we need to save the token generated on the frontend to pass it to the backend. And the Next.js documentation recommends creating the token on the backend as “HttpOnly” for better security, but Firebase Auth doesn’t follow this pattern, and there isn’t much documentation about it or how Firebase handles cookie security.

    I hope Firebase will consider my feedback.

    Hey, hi, I’m a Next.js developer, and the only problem I’m having with Firebase is with the Firebase Auth integration. I’d like to see improvements to the documentation for Next.js and its integration with server-side rendering. The problem I’ve encountered is that we need to save the token generated on the frontend to pass it to the backend. And the Next.js documentation recommends creating the token on the backend as “HttpOnly” for better security, but Firebase Auth doesn’t follow this pattern, and there isn’t much documentation about it or how Firebase handles cookie security.

    I hope Firebase will consider my… 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  ·  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

14. Narottam
    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  ·  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

15. Missing Primitives: Transaction Awareness and Trusted Server Metadata in Security Rules

    Firestore Security Rules currently lack two capabilities that force developers to choose between security, performance, and maintainability.

    1. Lack of Transaction/Batch Awareness Rules cannot verify if a write is part of an atomic batch or transaction. This makes it impossible to enforce multi-document integrity constraints natively.

    The Fallout: Developers must either trust the client to perform all parts of an operation (unsafe) or move logic to Cloud Functions. This introduces latency and cold-starts, but more importantly, it fragments security logic. Concise, native rules bolster security because they are easier to audit and are implemented correctly more often than fragmented, multi-layered workarounds.

    1. No "Middle Ground" for Server-Side Operations Currently, a server must either use the Admin SDK (which results in a full administrative bypass of all rules) or Identity Platform to impersonate a user. There is no way for a server to provide "partial validation" for a request that must still remain failable if it violates standard Rule constraints.

    The Fallout: Current limitations incentivize the use of "shared secrets"—checking for specific plain text properties or "magic strings" within the document data to signal that a server has "blessed" the write. This pattern may be adopted because it is more efficient than the alternatives, but it is brittle and mimics security without the actual structural protection of the Rules engine.

    Use Case Examples
    Relational Integrity (The "Escrow" Logic): A Purchase document must be created if and only if the Product status is simultaneously updated to sold in the same atomic transaction.

    External Validation (The "Verified Invite"): A server validates a one-time invite code against a 3rd-party API and "stamps" the request as valid. The Rules then check this stamp alongside request.auth to ensure the user isn't on a blacklist. The server validates the code; the Rules validate the user.

    State Synchronization (The "Booking Lock"): A user booking a hotel room must create a Booking doc and update the Room availability timestamp in one batch. Without is_transaction, rules cannot prevent "orphaned" bookings.

    Requested Features
    request.is_transaction: A boolean allowing rules to reject non-atomic "partial" updates to sensitive multi-document states.

    request.auth.token.server_assertions: A way for the Admin SDK to attach non-forgeable, temporary metadata to a user-authed request. This allows the server to act as a co-validator without needing a full administrative bypass.

    Appendix: Proposed Rule Syntax Examples
    A. Multi-Document Invariants

    JavaScript
    // Ensure a product status isn't flipped without a corresponding purchase record
    match /products/{productId} {
    allow update: if request.resource.data.status == 'sold'
    && request.istransaction == true
    && existsAfter(/databases/$(database)/documents/purchases/$(request.auth.uid)$(productId));
    }
    B. Co-Validation (Failable Requests)

    JavaScript
    // Server verifies the invite, Rules verify the user identity and blacklist status
    match /workspaces/{workspaceId}/members/{memberId} {
    allow create: if request.auth.uid == memberId
    && request.auth.token.serverassertions.inviteverified == true
    && !get(/databases/$(database)/documents/blacklist/$(memberId)).exists();
    }
    Summary: Firestore needs a way to combine user auth with trusted server assertions and transaction visibility. Without these, secure patterns are significantly harder to implement than unsafe ones.

    Firestore Security Rules currently lack two capabilities that force developers to choose between security, performance, and maintainability.

    1. Lack of Transaction/Batch Awareness Rules cannot verify if a write is part of an atomic batch or transaction. This makes it impossible to enforce multi-document integrity constraints natively.

    The Fallout: Developers must either trust the client to perform all parts of an operation (unsafe) or move logic to Cloud Functions. This introduces latency and cold-starts, but more importantly, it fragments security logic. Concise, native rules bolster security because they are easier to audit and are implemented correctly more often than fragmented, multi-layered workarounds.

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

16. Allow users to easily leave or disconnect from Firebase projects they no longer belong to

    When developers change companies or stop collaborating on a project, they often remain listed as members of Firebase projects that they no longer use or have access to.

    Currently, the only way to be removed from a project is for a project owner or administrator to manually remove the user from the project permissions. This becomes problematic when:

    The developer no longer has contact with the project owner

    The company forgets to remove former collaborators

    The user wants to clean up their Firebase project list

    I suggest adding a “Leave Project” or “Disconnect from Project” option directly in the Firebase console for members.

    This feature could:

    Allow users to remove themselves from projects they no longer work on

    Improve security by reducing unnecessary access to company resources

    Help developers keep their Firebase console organized

    Reduce administrative overhead for project owners

    For example, developers who change jobs often still see old company projects in their Firebase dashboard, even though they no longer use them.

    A simple self-removal option would solve this problem in a secure and user-friendly way.

    When developers change companies or stop collaborating on a project, they often remain listed as members of Firebase projects that they no longer use or have access to.

    Currently, the only way to be removed from a project is for a project owner or administrator to manually remove the user from the project permissions. This becomes problematic when:

    The developer no longer has contact with the project owner

    The company forgets to remove former collaborators

    The user wants to clean up their Firebase project list

    I suggest adding a “Leave Project” or “Disconnect from Project” option directly in the Firebase… 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  ·  Other  ·  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. preview env links support

    currently its needed to deploy the app to firebase hosting AND firebase app hosting to get preview links working, thats making things more complex than needed...

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

18. I want to able to set Cloud Run Execution Environment in Cloud Functions

    https://docs.cloud.google.com/run/docs/configuring/execution-environments

    Since Cloud Functions v2 run on Cloud Run and Cloud Run supports two different execution environment, I want to be able to set them, e.g.

    const { onRequest } = require("firebase-functions/v2/https");

    // Set it for a specific function
    exports.myFunction = onRequest({
    executionEnvironment: 'gen1', // This tells Cloud Run to use its Gen1 environment
    memory: '256MiB',
    }, (req, res) => {
    res.send("Running on Cloud Run Gen1 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  ·  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

19. 1251 end

    VIP NUMBER

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

20. RobLO
    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