1546 results found

1. Feedback, inefficient user experience

   I selected app by react+expo I think (I tried many different things and all have similar issues) one of projects as example was expense tracker

   the prompt was 👇

   Build a mobile-friendly financial management app called Expense Tracker with the following features and technical specifications:

   ---

   Core Features:

   1. Net Worth Management

   Allow users to manually set exact values for three asset categories: cash, bank, and card.

   Support incremental updates (add/subtract) to individual asset categories.

   Automatically calculate and display total net worth in real time.

   Visualize asset breakdown by category using a card or chart.

   1. Expense Tracking

   Let users add expenses by entering:

   Amount

   Description

   Category (e.g., food, transport)

   Source (cash, bank, or card)

   Show a filterable transaction history of all recorded expenses.

   Automatically subtract expense amounts from the selected asset source and update net worth accordingly.

   1. Debtor Management

   Allow users to record loans given to others by entering:

   Amount

   Debtor name

   Description

   Source used for lending (cash, bank, or card)

   Track the status of each debt: paid or unpaid.

   When marking a debt as paid, return the money to the original asset source.

   Allow filtering of debt records based on payment status.

   ---

   Technical Implementation:

   Components Required:

   UpdateNetWorthForm: Dual-mode form for exact values or add/subtract updates per asset category.

   ExpenseForm: Inputs for amount, description, category, and asset source.

   DebtorForm: Inputs for loan details and repayment action.

   NetWorthCard: Displays total net worth and asset breakdown visually.

   TransactionHistory: Filterable list of all expenses.

   DebtorsSection: Display, filter, and manage all debtor records.

   Data Models:

   NetWorth: Holds values for cash, bank, and card, plus total calculation.

   Expense: Stores expense records with source and metadata.

   Debtor: Stores loans, repayment status, and source tracking.

   App Flow Summary:

   1. User sets initial asset values.

   2. When expenses are recorded, assets update based on the selected source.

   3. Loans reduce assets and are logged with details.

   4. When debts are marked repaid, the amount returns to the correct asset source.

   5. Dashboard continuously displays real-time data on assets, expenses, and debts.

   ---

   Additional Notes:

   Ensure forms are validated and handle user input errors gracefully.

   Preserve individual asset values when updating only one category.

   Ensure debtor repayments correctly credit the original asset category.
   ,,,

   That's it. None of my projects on idx made an app honestly all of them get bugs that ruin it .. and Gemini tells many times that she can't do some prompts. Like fixing the Android emulator. Which isn't working at all as shown in ss. I hope you fix it and make it better. And I hope you're aware that almost all users are upset because of bad performance wasn't expected.

   I selected app by react+expo I think (I tried many different things and all have similar issues) one of projects as example was expense tracker

   the prompt was 👇

   Build a mobile-friendly financial management app called Expense Tracker with the following features and technical specifications:

   ---

   Core Features:

   1. Net Worth Management

   Allow users to manually set exact values for three asset categories: cash, bank, and card.

   Support incremental updates (add/subtract) to individual asset categories.

   Automatically calculate and display total net worth in real time.

   Visualize asset breakdown by category using a card or chart.

   1. Expense Tracking

   Let users add expenses by… more

   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  ·  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. Support for Inter-App Linking Within a Project

   The ability to link two applications together based on user action is missing. An example is the connection between passenger and driver apps in ride-booking.

   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

   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. Clear LLM Selector

   Firebase Studio appears to predominantly rely on one of the Gemini Flash models, though there also seems to be the ability to utilize Gemini 2.5 Pro via a bring-your-own-API-key approach. That by itself is fine, though the current UI isn't very good at keeping the user informed about which model they are using at any given time and how to switch during a project. I propose a clear, easy to change selector (most simply as a drop down panel) that showcases all available models, as well as models that can be added by using ones own API key. If such a key hasn't been provided to Firebase Studio, I'd suggest directly linking to a settings page for adding ones API key upon selecting an API-key only model. This would not only make Firebase Studio more streamlined and usable, but also ease frustration by letting users try a different model when the one they started the project with isn't suitable for a given task.

   Firebase Studio appears to predominantly rely on one of the Gemini Flash models, though there also seems to be the ability to utilize Gemini 2.5 Pro via a bring-your-own-API-key approach. That by itself is fine, though the current UI isn't very good at keeping the user informed about which model they are using at any given time and how to switch during a project. I propose a clear, easy to change selector (most simply as a drop down panel) that showcases all available models, as well as models that can be added by using ones own API key. If such… more

   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

   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

4. Laravel Support

   There was Laravel option available in project IDX but since it have turned into Firebase Studio I cannot see Laravel anymore.

   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

   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

5. Consistent and documented behavior for on*WithAuthContext

   When Functions use e.g. onDocumentCreatedWithAuthContext to handle Firestore event triggers, the meaning of event.authType and event.authId are not documented and are inconsistent between the production and emulator environments.

   The documentation [https://firebase.google.com/docs/functions/firestore-events?gen=2nd#auth-context](here) says "For information about the data available in the authentication context, see..." and links to a page that is not specific to Firebase. That page lists some possible values, but it's not clear what values would be used. The most sensible guess is that authType would be "appuser" or "user" if the document was created from the client-side web SDK, and "serviceaccount" if created from a Cloud Function. But those are not the values used.

   In production, if the document is created from the client-side web SDK, authType is "api_key" and authId is the ID of the logged in user. If it's created from a Cloud Function, authType is "unknown" and authId is the ID of the default service account. Thus it is possible to tell the difference, although since the behavior is undocumented, we can't assume that the behavior won't change.

   In the emulator environment, authType is always "unknown" and authId is always "fake-auth-id@gmail.com". This is inconsistent with the production environment and makes it impossible to tell how the document was created.

   The behavior should be consistent and sensible and well documented.

   When Functions use e.g. onDocumentCreatedWithAuthContext to handle Firestore event triggers, the meaning of event.authType and event.authId are not documented and are inconsistent between the production and emulator environments.

   The documentation [https://firebase.google.com/docs/functions/firestore-events?gen=2nd#auth-context](here) says "For information about the data available in the authentication context, see..." and links to a page that is not specific to Firebase. That page lists some possible values, but it's not clear what values would be used. The most sensible guess is that authType would be "appuser" or "user" if the document was created from the client-side web SDK, and "serviceaccount" if created from a… more

   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

   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

6. i cant create the Storage shows An unknown error occurred.

   i cant create the Storage shows An unknown error occurred.

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

7. Configure Firebase Lambda and API endpoint exposure

   Automate the "subprocesses" to open up an endpoint to interact with Firebase Lambdas, which have the access permissions to make changes to the realtime database, storage, and auth core functionality. This encompasses many applications' backend use cases if interactive via REST API. So open these lambdas to access services via HTTP calls.

   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

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

8. نظام TRS

   نظام التفكير وحرية لنظام QI AI له نظام التصرف الفردي ودالك عبر مكتبة المعلومات الالكترونية وبدالك يمكنه توفير نظام الاختراق وحماية الويب وتوفير نسيج من الحلول المقترحة وغيرها من الاعمال الاخرة كاتنيم الصور وفيدوات وتنظيم الموسقى العشوئة مع توفير اللعاب وافلام ومحاكات الخوارزمات مبرجة وكل هدا عبر نصوص وافكار وسينروات لمحاكات الخيال الواقعي

   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  ·  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. Recomendaciones para Mejorar Firebase Studio

   Recomendaciones para Mejorar Firebase Studio:

   Mejora en la Interpretación de Solicitudes Complejas:

   Firebase Studio debe mejorar su capacidad para interpretar solicitudes complejas y multifacéticas.
   Se debe prestar especial atención a la identificación y el cumplimiento de las especificaciones tecnológicas (por ejemplo, lenguajes de programación, frameworks, bases de datos) proporcionadas por el usuario.
   Implementar un sistema de "confirmación" donde la herramienta, antes de generar el codigo, muestre las tecnologias que usara, y el usuario pueda aceptar, o rechazar.
   Generación de Código Más Precisa y Completa:

   La herramienta debe generar código que sea más preciso y completo, abarcando todas las funcionalidades solicitadas por el usuario.
   Se debe prestar especial atención a la generación de código para funcionalidades clave como la autenticación de usuarios, la gestión de bases de datos, la implementación de APIs y la integración de servicios externos.
   Se debe mejorar la capacidad de la IA para generar codigo, que siga la estructura de carpetas que se le indica.
   Incorporación de Comentarios y Explicaciones Detalladas:

   El código generado debe incluir comentarios claros y concisos que expliquen la lógica y el propósito de cada sección.
   Se deben proporcionar explicaciones detalladas de las decisiones de diseño y las implementaciones técnicas.
   Se debe implementar la internacionalización de los textos que se le muestran al usuario.
   Se debe generar la documentación del codigo generado.
   Mejora en la Documentación Generada:

   La documentación generada debe ser completa, clara y concisa, y debe incluir:
   Una descripción general de la aplicación.
   Detalles técnicos sobre la arquitectura, las tecnologías utilizadas y la implementación de las funcionalidades.
   Instrucciones para la instalación, configuración y uso de la aplicación.
   Traducción de la documentación a los idiomas del usuario.
   La documentación debe estar actualizada y ser accesible para todos los desarrolladores involucrados en el proyecto.
   Mayor Flexibilidad y Control para el Usuario:

   Firebase Studio debe proporcionar a los usuarios una mayor flexibilidad y control sobre el código generado.
   Se deben ofrecer opciones para personalizar la arquitectura, las tecnologías y las funcionalidades de la aplicación.
   Se debe implementar, la opcion para que el usuario pueda seleccionar las versiones de las librerias que desea usar.
   Retroalimentación Continua y Mejora Iterativa:

   Google debe establecer un proceso de retroalimentación continua para recopilar opiniones y sugerencias de los usuarios.
   Firebase Studio debe mejorar de forma iterativa, incorporando la retroalimentación de los usuarios y adaptándose a las nuevas necesidades del mercado.

   Recomendaciones para Mejorar Firebase Studio:

   Mejora en la Interpretación de Solicitudes Complejas:

   Firebase Studio debe mejorar su capacidad para interpretar solicitudes complejas y multifacéticas.
   Se debe prestar especial atención a la identificación y el cumplimiento de las especificaciones tecnológicas (por ejemplo, lenguajes de programación, frameworks, bases de datos) proporcionadas por el usuario.
   Implementar un sistema de "confirmación" donde la herramienta, antes de generar el codigo, muestre las tecnologias que usara, y el usuario pueda aceptar, o rechazar.
   Generación de Código Más Precisa y Completa:

   La herramienta debe generar código que sea más preciso y completo, abarcando todas las funcionalidades solicitadas… more

   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  ·  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. Support for Lua

    I suggest support for Lua, a lot of games and apps use Lua, It'd be nice to have support of it as it's also beginner-friendly making it relatively easy

    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

    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

11. Fix error messages when deploying Functions

    Several error messages often occur when deploying Firebase Cloud Functions that should not occur. My first time attempting to deploy functions in a new project, I got:

    i extensions: ensuring required API firebaseextensions.googleapis.com is enabled...
    ⚠ extensions: missing required API firebaseextensions.googleapis.com. Enabling now...

    Error: Request to https://serviceusage.googleapis.com/v1/projects/********/services/firebaseextensions.googleapis.com had HTTP Error: 429, Quota exceeded for quota metric 'Default requests' and limit 'Default requests per minute' of service 'serviceusage.googleapis.com' for consumer 'project_number:********'.

    I don't know if that happens every time. It appears to be just a failure to wait long enough after enabling the API.

    The second time, it got further, but errored again:

    ⚠ functions: missing required API eventarc.googleapis.com. Enabling now...
    ✔ functions: required API pubsub.googleapis.com is enabled
    ✔ functions: required API storage.googleapis.com is enabled
    ✔ functions: required API run.googleapis.com is enabled
    ✔ functions: required API eventarc.googleapis.com is enabled
    i functions: generating the service identity for pubsub.googleapis.com...
    i functions: generating the service identity for eventarc.googleapis.com...
    ✔ functions: functions folder uploaded successfully
    i functions: creating Node.js 22 (2nd Gen) function onMessageCreated(us-central1)...
    ⚠ functions: Request to https://cloudfunctions.googleapis.com/v2/projects/********/locations/us-central1/functions?functionId=onMessageCreated had HTTP Error: 400, Validation failed for trigger projects/*****/locations/us-central1/triggers/onmessagecreated-119882: Invalid resource state for "": Permission denied while using the Eventarc Service Agent. If you recently started to use Eventarc, it may take a few minutes before all necessary permissions are propagated to the Service Agent. Otherwise, verify that it has Eventarc Service Agent role.
    ⚠ functions: Since this is your first time using 2nd gen functions, we need a little bit longer to finish setting everything up. Retry the deployment in a few minutes.
    ⚠ functions: failed to create function projects/**/locations/us-central1/functions/onMessageCreated
    Failed to create function projects/*****/locations/us-central1/functions/onMessageCreated

    Functions deploy had errors with the following functions:
    onMessageCreated(us-central1)
    i functions: cleaning up build files...
    ⚠ functions: Unhandled error cleaning up build images. This could result in a small monthly bill if not corrected. You can attempt to delete these images by redeploying or you can delete them manually at https://console.cloud.google.com/gcr/images/********/us/gcf

    Error: There was an error deploying functions

    Again, it appears to be a timeout issue.

    Subsequent deploys have been successful, but I get this warning every time:

    ⚠ functions: Unhandled error cleaning up build images. This could result in a small monthly bill if not corrected. You can attempt to delete these images by redeploying or you can delete them manually at https://console.cloud.google.com/gcr/images/********/us/gcf

    That implies there may be a storage leak happening on every deploy.

    None of these errors should be happening, as far as I can tell.

    Several error messages often occur when deploying Firebase Cloud Functions that should not occur. My first time attempting to deploy functions in a new project, I got:

    i extensions: ensuring required API firebaseextensions.googleapis.com is enabled...
    ⚠ extensions: missing required API firebaseextensions.googleapis.com. Enabling now...

    Error: Request to https://serviceusage.googleapis.com/v1/projects/********/services/firebaseextensions.googleapis.com had HTTP Error: 429, Quota exceeded for quota metric 'Default requests' and limit 'Default requests per minute' of service 'serviceusage.googleapis.com' for consumer 'project_number:********'.

    I don't know if that happens every time. It appears to be just a failure to wait long enough after enabling the API.

    The second time, it got further, but… more

    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

    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

12. Missing App Check Integration Details for Vertex AI in Firebase (Flutter SDK)

    I would like to report a critical documentation gap regarding the integration of App Check with Vertex AI in Firebase, especially for Flutter developers.

    Currently, there is no mention in the official Firebase documentation that Flutter developers must initialize Vertex AI using:

    final model = FirebaseVertexAI.instanceFor(appCheck: FirebaseAppCheck.instance)
    .generativeModel(model: 'MODEL');

    Without this step, even when App Check is properly set up across the project, the Firebase dashboard continues to show 0% verified requests under "Vertex AI in Firebase."

    This not only leads to confusion but also prevents teams from safely enforcing App Check across all services, as doing so risks breaking features dependent on Vertex AI.

    I strongly recommend that this initialization requirement be explicitly included in both the Firebase Vertex AI and App Check documentation sections for Flutter.

    I would like to report a critical documentation gap regarding the integration of App Check with Vertex AI in Firebase, especially for Flutter developers.

    Currently, there is no mention in the official Firebase documentation that Flutter developers must initialize Vertex AI using:

    final model = FirebaseVertexAI.instanceFor(appCheck: FirebaseAppCheck.instance)
    .generativeModel(model: 'MODEL');

    Without this step, even when App Check is properly set up across the project, the Firebase dashboard continues to show 0% verified requests under "Vertex AI in Firebase."

    This not only leads to confusion but also prevents teams from safely enforcing App Check across all services, as doing so risks breaking… more

    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  ·  App Check  ·  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. API for NotebookLM

    Developer api to interact with notebooklm

    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

    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

14. Give access to dir outside home like /opt, /mnt. etc.

    It is getting hard to setup the existing open source project on google idx as we only has access to /home dir and all other are only in read only mode which is making hard for use to develop new project on the idx

    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

    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

15. Allow to change the connected git repository from the console

    For a variety of reasons there are cases where the name of the repository (or organization, so the name too) changes, or we need to change the connected repository. Currently, this will require to create a new backend to configure it all over again.

    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

    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

16. Automatic GraphQL schema from existing SQL schema

    When onboarding an existing postgres database, Data Connect can read the postgres schema and attempt to generate a corresponding GraphQL schema. Users with existing databases can immediately benefit from Data Connect client SDKs, query based auth, and connector connection pooling without manually writing GraphQL that matches their database schema.

    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

    0 comments  ·  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. CLI deploy and link blocking functions

    Function Deployment & Validation Flow:

    When deploying cloud functions with recognized lifecycle hook names (e.g., beforeCreate, beforeSignin), the system should:

    .
    Detect Blocking Function Patterns
    Check if the deployed function's name matches known blocking trigger conventions.

    .
    Assignment Validation
    Verify whether the detected function is registered as a blocking trigger in the system configuration.

    .
    Interactive Guidance
    If unassigned, display CLI prompt:
    "Seems like you want to deploy a 'Blocking' function named <FUNCTION_NAME> but no blocking trigger is assigned. To configure this function visit: <CONSOLE URL>"

    .
    Key Function Patterns:

    beforeCreate | beforeSignin | afterSignout | customBeforeHook
    

    Why This Matters:

    Proactively addresses common configuration gaps through contextual prompts, reducing deployment errors and cognitive load for developers while maintaining automation compatibility.

    Function Deployment & Validation Flow:

    When deploying cloud functions with recognized lifecycle hook names (e.g., beforeCreate, beforeSignin), the system should:

    .
    Detect Blocking Function Patterns
    Check if the deployed function's name matches known blocking trigger conventions.

    .
    Assignment Validation
    Verify whether the detected function is registered as a blocking trigger in the system configuration.

    .
    Interactive Guidance
    If unassigned, display CLI prompt:
    "Seems like you want to deploy a 'Blocking' function named <FUNCTION_NAME> but no blocking trigger is assigned. To configure this function visit: <CONSOLE URL>"

    .
    Key Function Patterns:

    beforeCreate | beforeSignin | afterSignout | customBeforeHook
    

    Why This Matters:

    … more

    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

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. CLI deploy and link blocking functions

    Function Deployment & Validation Flow:
    When deploying cloud functions with recognized lifecycle hook names (e.g., beforeCreate, beforeSignin), the system should:

    Detect Blocking Function Patterns
    Check if the deployed function's name matches known blocking trigger conventions.

    Assignment Validation
    Verify whether the detected function is registered as a blocking trigger in the system configuration.

    Interactive Guidance
    If unassigned, display CLI prompt:
    "Seems like you want to deploy a 'Blocking' function named <FUNCTION_NAME> but no blocking trigger is assigned. Would you like to configure this function now? (y/N)"

    Key Function Patterns:
    ```
    beforeCreate | beforeSignin | afterSignout | customBeforeHook

    (Additional supported hooks)

    
    Why This Matters:
    Proactively addresses common configuration gaps through contextual prompts, reducing deployment errors and cognitive load for developers while maintaining automation compatibility.
    

    Function Deployment & Validation Flow:
    When deploying cloud functions with recognized lifecycle hook names (e.g., beforeCreate, beforeSignin), the system should:

    Detect Blocking Function Patterns
    Check if the deployed function's name matches known blocking trigger conventions.

    Assignment Validation
    Verify whether the detected function is registered as a blocking trigger in the system configuration.

    Interactive Guidance
    If unassigned, display CLI prompt:
    "Seems like you want to deploy a 'Blocking' function named <FUNCTION_NAME> but no blocking trigger is assigned. Would you like to configure this function now? (y/N)"

    Key Function Patterns:
    ```
    beforeCreate | beforeSignin | afterSignout | customBeforeHook

    (Additional supported hooks)

    
    Why

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

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Export / Import single document on firestore console

    Please add an option to export or import a single document from firestore console in firebase page, not in gcloud. Same way like we can do on firebase database export and import a json file with the data.

    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

    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

20. Delivery logging in iOS

    Does anyone know why Firebase doesn't support notification delivery on iOS? This is supported by other messaging frameworks such as OneSignal by hooking into Notification Service Extensions.

    Firebase does have a FIRMessagingExtensionHelper class which has an exportDeliveryMetricsToBigQuery method — however I didn't see references to this in the docs, how it should be used, or whether it suits my needs.

    The ideal scenario is that Firebase can just report iOS delivery rates in the console. It's confusing to me why this is not made simple, and if anyone has some insight here it would be much appreciated.

    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

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