1232 results found

1. Firebase Data Connect lacks ON DELETE RESTRICT support and causes brownfield schema mismatch

   Hi Firebase Data Connect team,
   I’m currently using Firebase Data Connect with Cloud SQL (PostgreSQL) and facing a limitation related to foreign key delete constraints.
   PostgreSQL natively supports ON DELETE RESTRICT, and when I manually apply this constraint directly in Cloud SQL, everything works perfectly and the application behaves exactly as intended.
   However, Data Connect does not provide any way to define or preserve ON DELETE RESTRICT in its schema. While Data Connect does expose an explicit directive (the ! notation) to define ON DELETE CASCADE, there is no equivalent option for RESTRICT or other delete behaviors.
   Because of this, when the database contains a valid ON DELETE RESTRICT constraint, Data Connect reports a brownfield schema mismatch error, stating that the SQL schema does not match the Data Connect schema and asking to make the SQL schema identical to Data Connect’s definition.
   This creates a serious problem for production systems:
   ON DELETE RESTRICT is a core relational integrity feature
   Data Connect recognizes CASCADE but provides no mechanism to define RESTRICT
   Manually applied constraints are rejected or flagged during deployment
   Questions / Requests:
   Is there an official way to define ON DELETE RESTRICT in Data Connect?
   If not, what is the recommended workaround that avoids schema drift and deployment failures?
   Are there plans to support explicit delete behaviors (RESTRICT / CASCADE / SET NULL) in the Data Connect schema?
   This capability is essential for production-grade relational database design, and first-class support would greatly improve Data Connect’s suitability for real-world systems.
   Thanks for your time, and I’d appreciate any guidance or roadmap clarity on this.

   Hi Firebase Data Connect team,
   I’m currently using Firebase Data Connect with Cloud SQL (PostgreSQL) and facing a limitation related to foreign key delete constraints.
   PostgreSQL natively supports ON DELETE RESTRICT, and when I manually apply this constraint directly in Cloud SQL, everything works perfectly and the application behaves exactly as intended.
   However, Data Connect does not provide any way to define or preserve ON DELETE RESTRICT in its schema. While Data Connect does expose an explicit directive (the ! notation) to define ON DELETE CASCADE, there is no equivalent option for RESTRICT or other delete behaviors.
   Because of this,… 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  ·  SQL Connect (Data Connect)  ·  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 needs to make blaze plan have a better built in cap for pay as you go.

   The cap just alerts you when you reach your cap. If you have a major issue, for example, something that spam read and writes indefinetly, you will end up paying thousands over your "limit". PLEASE. PLEASE make it so YOUR customers do not have to write a script that should be built in.

   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

3. Here is a **strong, complete, production-ready prompt** you can paste into any advanced LLM (GPT/Claude/LLaMA) to generate a **full tokenisa
   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

   0 comments  ·  App Distribution  ·  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. Add support to document Why change was published

   There should be an optional note field when publishing changes to explain why these changes to the config were published. Moreover, it would be great to have a simple history view of what changes were published with notes.

   Right now, we can only see WHEN and WHO published the latest changes, but we don't know WHY

   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

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

5. Firebase App Distribution Permissions Change

   Currently, the automated testing feature within Firebase App Distribution mandates that the user executing the test possess either the Project Owner or Project Editor IAM role. This requirement is overly broad and presents a significant operational barrier for organizations managing a large number of projects (e.g., 1,000+) where granting such high-level permissions is often restricted due to security policies and standard practices. Attempts confirmed that even users with high-privilege roles like Organization Admin and Firebase Admin were unable to run these tests, indicating the check is strictly limited to Owner/Editor.

   This limitation prevents teams from effectively utilizing the automated testing feature. We request the ability to run Firebase App Distribution automated tests using more granular permissions. Ideally, this would involve either identifying a specific set of minimum required permissions that can be bundled into a custom role or providing a new, less privileged predefined IAM role specifically for this purpose. Enabling finer-grained access control is crucial for the adoption and practical use of this feature in enterprise environments. Google Support acknowledged this limitation is known, on the product roadmap without a specific ETA, and filed an internal bug/request.

   Currently, the automated testing feature within Firebase App Distribution mandates that the user executing the test possess either the Project Owner or Project Editor IAM role. This requirement is overly broad and presents a significant operational barrier for organizations managing a large number of projects (e.g., 1,000+) where granting such high-level permissions is often restricted due to security policies and standard practices. Attempts confirmed that even users with high-privilege roles like Organization Admin and Firebase Admin were unable to run these tests, indicating the check is strictly limited to Owner/Editor.

   This limitation prevents teams from effectively utilizing the automated testing… more

   10 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 Distribution  ·  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. Support for Proper 404 Status Codes and Multiple 404 Pages Based on URL Patterns on Firebase Hosting

   Currently, when using a custom 404 page (e.g., 404.html), Firebase Hosting always responds with a 200 status code, even when the page is served via a rewrite rule.
   This differs from behavior on traditional servers (e.g., Nginx with the internal directive), where the server can correctly return a 404 while still serving a custom error page.

   Why this matters:
   - Proper HTTP status codes are essential for SEO.
   - Search engines may incorrectly index 404 pages if they return 200.
   - Client applications and monitoring tools rely on correct status codes.

   Additionally, In many multilingual or multi-section sites, different parts of a website require different 404 pages.
   At the moment, the only workaround is to use rewrite rules, such as:

   {
     "rewrites": [
       { "source": "/es/**", "destination": "/es/404.html" }
     ]
   }
   

   However, this still returns 200 instead of 404, which causes the same issue as above.

   Requested enhancement:
   - Allow developers to define multiple 404 handlers depending on URL patterns (e.g. /es/** → /es/404.html, /fr/** → /fr/404.html)
   - Ensure each of these handlers can return a real 404 status code

   These two capabilities would significantly improve:
   - SEO accuracy
   - Error analytics
   - User experience for multilingual or multi-section websites
   - Parity with traditional server behavior

   Thank you for considering these enhancements!

   Currently, when using a custom 404 page (e.g., 404.html), Firebase Hosting always responds with a 200 status code, even when the page is served via a rewrite rule.
   This differs from behavior on traditional servers (e.g., Nginx with the internal directive), where the server can correctly return a 404 while still serving a custom error page.

   Why this matters:
   - Proper HTTP status codes are essential for SEO.
   - Search engines may incorrectly index 404 pages if they return 200.
   - Client applications and monitoring tools rely on correct status codes.

   Additionally, In many multilingual or multi-section sites, different parts… 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

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

7. Fallback to Gemma when browser based models are not available in the Hybrid SDK

   When using Firebase AI Logic for hybrid inference, I want to be able to support users that are using non-Chrome browsers to still be able to run inference. In this case, give me an option to download Gemma and run inference for my users running a non-Chrome browser. This preserves the PREFERONDEVICE or ONLYONDEVICE flags I have set and allows my users to continue to benefit the rewards of my app without needing to download a new browser.

   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

   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

8. parametre

   je veut ma cle api

   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

   0 comments  ·  Firebase console  ·  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. Map Firebase Data Connect (FDC) schema to custom postgres schema (not PUBLIC)

   Currently, any gql files placed in schema folder generate one FDC schema in FDC console, which generates associated tables in postgres PUBLIC schema. Putting tables there is not ideal.

   It would be nice if creating additional subfolders within schema source folder (or some other mechanism) could allow mapping to developer defined postgres schemas other than PUBLIC. For example, the following folder structure:

   schema/appname/*.gql

   would map to APPNAME schema in Postgres and tables would be created there.

   4 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  ·  SQL Connect (Data Connect)  ·  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. I want to know about android app work

    Page not found

    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

11. Add support for country-based user targeting in Firebase SDK

    It would be very helpful if the Firebase SDK included built-in support for targeting users based on their country. Currently, we have to handle this manually using workarounds or backend logic. Native support in the SDK for accessing the user’s country (based on IP or locale) and using it for feature targeting, in-app messaging, or remote config conditions would streamline country-specific personalization and improve the user experience.

    This feature would allow us to:

    Show different content or messages to users based on their country.

    Better segment users for A/B testing or campaigns.

    Reduce backend dependency for basic geographic targeting.

    Please consider adding this functionality directly in the Firebase SDK

    It would be very helpful if the Firebase SDK included built-in support for targeting users based on their country. Currently, we have to handle this manually using workarounds or backend logic. Native support in the SDK for accessing the user’s country (based on IP or locale) and using it for feature targeting, in-app messaging, or remote config conditions would streamline country-specific personalization and improve the user experience.

    This feature would allow us to:

    Show different content or messages to users based on their country.

    Better segment users for A/B testing or campaigns.

    Reduce backend dependency for basic geographic targeting.

    Please… more

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

12. saltar al contenido Google, LLC - Firebase Tombomvouz Tombomnouz Mantener la sesión iniciada · Configuración · Salir Support Kotlin Multipl

    saltar al contenido
    Google, LLC - Firebase

    Tombomvouz Tombomnouz
    Mantener la sesión iniciada · Configuración · Salir
    Support Kotlin Multiplatform (KMP) in the SDKs
    KMP is now stable and more libraries are being added to KMP ecosystem. There is a big opportunity for Firebase to be in Multiplatform and support developers adopting this tech.

    1,248
    vota
    Carlos Monzon
    compartió esta sugerencia
    · 27 de abril de 2023 · Reporte…
    Cuan importante es esto Para ti?
    Not at all
    Important
    Critical
    Añadir un comentario…
    Enviar un comentario
    Jeff Avery
    comentado
    · 17 de marzo de 2024 12:06 · Reporte
    I teach a Kotlin full-stack course, where we build desktop+Android apps. I'd prefer to use Firebase or GCP for hosting, but cannot due to lack of Kotlin multiplatform support. I'm surprised that Google hasn't done this already. This is critical for us to be able to use Firebase in the classroom. Without KMP support, I have to choose a different platform.

    MaasboDev
    comentado
    · 11 de marzo de 2024 02:22 · Reporte
    I'm doing an app using kmp and wanted to use firebas., Now is possible to add it for android and iOS, but the desktop part is not supported yet.

    Benoit Delville
    comentado
    · 03 de marzo de 2024 17:34 · Reporte
    KMP support will be the key decision to which analytic and crash report platform we will use soon. We would like Firebase to be in the list!

    Carlos
    comentado
    · 03 de marzo de 2024 07:35 · Reporte
    This sdks are a must for mobile dev!

    Analytics, remote config and crashlytics at least should be prioritized

    Krzysztof Borowy
    comentado
    · 03 de marzo de 2024 05:39 · Reporte
    I think this would allow for better adoptation of KMP in smaller teams, to get product out of the door faster

    Jep RM
    comentado
    · 01 de marzo de 2024 01:53 · Reporte
    Analytics at least should be in KMP to create libs

    Angel Rodriguez
    comentado
    · 29 de febrero de 2024 20:31 · Reporte
    This would make a great use case to use with KMP with smaller teams who would want native but don’t have the resources to build a service as well.

    Himanshu Mistri
    comentado
    · 28 de febrero de 2024 01:29 · Reporte
    We have pipeline software in which we want to use common code for accessing firebase backend

    Jordon de Hoog
    comentado
    · 27 de febrero de 2024 16:06 · Reporte
    I unfortunately (like many others it seems) had to go with a different service due to there being no KMP support for Crashlytics, and RemoteConfig.

    Jep
    comentado
    · 27 de febrero de 2024 16:01 · Reporte
    I don't think there is something for analytics. And it would be very helpful

    Alexey Egin
    comentado
    · 27 de febrero de 2024 11:22 · Reporte
    I’m running several kmp apps and it’s sometimes difficult to handle crash reports, because I need to use 3-rd party solutions

    Messias Junior
    comentado
    · 27 de febrero de 2024 10:58 · Reporte
    I started using Supabase because of the lack of KMP support from Firebase. Thats sad

    mohamed rejeb
    comentado
    · 27 de febrero de 2024 01:35 · Reporte
    I start using sentry instead of firebase Crashlytics because of the lack of support for KMP.

    Vincent Guillebaud
    comentado
    · 26 de febrero de 2024 15:16 · Reporte
    I had to use Supabase for my project because Firebase is not compatible for now...

    We need Firebase for KMP!

    Sami Deliceli
    comentado
    · 26 de febrero de 2024 15:16 · Reporte
    In this ecosystem, Firebase is a technology that will primarily be lacked. Therefore, full support for KMP will definitely be an indispensable need for many projects.

    Divyansh Kushwaha
    comentado
    · 26 de febrero de 2024 14:55 · Reporte
    Currently, there exists an implementation in community
    https://firebaseopensource.com/projects/gitliveapp/firebase-kotlin-sdk/
    But would definitely love to have official support.

    Tyler Wilson
    comentado
    · 26 de febrero de 2024 12:05 · Reporte
    This would be great to see. Would save some work in my projects. Though I hope to one support wasm/js. Seems like that would be an additional bit of work.

    Rich Woollcott
    comentado
    · 26 de febrero de 2024 11:38 · Reporte
    Would love to see KMP support for web and iOS & Android!

    Anton Spaans
    comentado
    · 26 de febrero de 2024 11:36 · Reporte
    Firebase support would greatly increase KMP'a adoption, since it's a question often asked when suggesting using KMP for mobile applications.

    I wouldn't say it's critical, you can create your own two (or more) native implementations, but it's near critical for the speed of adoption.

    Cédric Dupin
    comentado
    · 26 de febrero de 2024 11:31 · Reporte
    I need this to implement my app in iOS

    1 2 … 12 13 14 15 16 Siguiente →
    Google, LLC - Firebase
    Google, LLC - Firebase Terms of Service Content Policy

    saltar al contenido
    Google, LLC - Firebase

    Tombomvouz Tombomnouz
    Mantener la sesión iniciada · Configuración · Salir
    Support Kotlin Multiplatform (KMP) in the SDKs
    KMP is now stable and more libraries are being added to KMP ecosystem. There is a big opportunity for Firebase to be in Multiplatform and support developers adopting this tech.

    1,248
    vota
    Carlos Monzon
    compartió esta sugerencia
    · 27 de abril de 2023 · Reporte…
    Cuan importante es esto Para ti?
    Not at all
    Important
    Critical
    Añadir un comentario…
    Enviar un comentario
    Jeff Avery
    comentado
    · 17 de marzo de 2024 12:06 · Reporte
    I teach… 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  ·  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

13. Voices generate

    To generate voices

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

14. 🚀 Advanced Proposal: Hybrid Firebase Architecture for Optimized Performance, Offline Access & Cloud Resilience

    🧠 Core Strategy

    1. Deploy Firebase Studio locally (on-premise or VM)

    2. Integrate with Firebase Emulator Suite + Edge Cache

    3. Enable automatic sync with Firebase Cloud

    4. Allow direct access to local services (filesystem, DB, devices)

    5. Use secure reverse tunnels and proxy APIs for controlled cloud interactions

    ---

    ✅ Key Benefits Overview

    Feature Benefit

    ✅ Offline First Use Firebase Emulator Suite to run Firestore, Auth, Hosting, Functions entirely offline
    ✅ Faster Performance Local queries eliminate latency from cloud round-trips
    ✅ Access Local Resources Direct access to local files, OS services, SQLite, or PostgreSQL
    ✅ Data Control Comply with GDPR/PDPA by keeping sensitive data local
    ✅ Failsafe Operations Local Firebase runs even when internet is unavailable
    ✅ Auto Cloud Sync Sync local Firestore changes to Firebase Cloud when connected
    ✅ Edge Firebase Deploy Firebase Studio app via Cloudflare Workers/Fly.io for global low-latency access
    ✅ Multi-Environment Support Seamlessly test across local, edge, and cloud environments
    ✅ Security Tightened Use Firebase rules + local VPN + JWT-protected API proxy

    ---

    ⚙️ Recommended Components

    Component Purpose

    🔸 Firebase Emulator Suite Local Firestore, Functions, Hosting, and Auth
    🔸 Dockerized Firebase Studio Containerized deployment on any server or laptop
    🔸 Edge Caching (Cloudflare/Fly.io) For performance + reduced global latency
    🔸 Secure API Proxy (NGINX + JWT) Gatekeeper for accessing cloud endpoints
    🔸 Local DB (e.g. SQLite, PostgreSQL) Optional secondary storage/mirror
    🔸 Sync Engine (Node.js/Cloud Functions) Automated bidirectional sync to Firebase Cloud
    🔸 Local Admin Panel (Optional) UI to manage users, data, and deployments offline

    ---

    💡 Real-World Use Cases & Advantages

    🛍️ Point-of-Sale (POS) App

    Works offline in restaurants or kiosks

    Syncs sales data to Firebase Cloud when online

    Supports local printers and receipt scanners directly

    🛡️ Security or IoT System

    Sensors log data to local Firestore (offline)

    No internet needed for core functionality

    Syncs logs or events to Firebase Cloud daily

    🏫 Education System / LMS

    Operates in classrooms without stable WiFi

    Tracks student progress locally

    Syncs to cloud at home or when reconnected

    ---

    🔧 Bonus Features (Optional Add-ons)

    Add-on Description

    🔁 Realtime Sync Layer Use tools like Replicache or PouchDB for smooth 2-way sync
    🔐 Local Audit Logging Keep full trace of all data and user actions offline
    🧠 Offline AI Integration Use ONNX or local ML models without cloud inference

    ---

    🔥 Summary

    This goes beyond just deploying Firebase Studio locally. We're talking about building a resilient, high-performance Firebase hybrid ecosystem — one that operates seamlessly offline, scales globally via edge servers, and syncs intelligently to the cloud.

    🧠 Core Strategy

    1. Deploy Firebase Studio locally (on-premise or VM)

    2. Integrate with Firebase Emulator Suite + Edge Cache

    3. Enable automatic sync with Firebase Cloud

    4. Allow direct access to local services (filesystem, DB, devices)

    5. Use secure reverse tunnels and proxy APIs for controlled cloud interactions

    ---

    ✅ Key Benefits Overview

    Feature Benefit

    ✅ Offline First Use Firebase Emulator Suite to run Firestore, Auth, Hosting, Functions entirely offline
    ✅ Faster Performance Local queries eliminate latency from cloud round-trips
    ✅ Access Local Resources Direct access to local files, OS services, SQLite, or PostgreSQL
    ✅ Data Control Comply with GDPR/PDPA by keeping sensitive data local… more

    5 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  ·  Cloud Functions for Firebase  ·  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. Allow to convert a Set() to a List() in the Firestore rules

    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 && request.resource.data[updatedKeys.toList()[0]] >= 0);

    But without the "toList()" function, I cannot get the value of the updated key in the Map. There is no way to access a Set() element other than by knowing the key.

    My actual workaround is to set a "temporary" String field in the request with the value of the updated key, but this is more a "hack"...

    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 &&… 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. Firebase Should Work With Kotlin Multiplatform

    KMP is now getting stable and the Firebase should be able to be used in these projects

    5 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  ·  SDKs  ·  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. BUILDING

    LETS BUILD

    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

    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

18. As new user or y

    When we work with Gemini as new user using mobile,we have to access database console,first of all the naming to front end developement and backend should be clear as firebase front end console and for data base as backend firebase to distanguish between the two,and while working on gemini sholud have access to backend to work on in Ai as a layman,

    4 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  ·  Firebase console  ·  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. Firebase Storage Setup API Issue

    I'm running the Web/APP builder platform using user's own Firebase. However, when user is creating platform through my service, Storage setup API is limited to existing users who have previously set up Cloud Storage. I have discovered that the existed Storage Setup API is available for both Spark and Blaze plans but not for new Firebase user who has never setup the Storage.
    Please provide the Storage Setup API also for new firebase user

    44 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  ·  Cloud Storage for Firebase  ·  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. Seems list everything

    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

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