1220 results found

1. Add windows...
   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

2. 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

   9 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

3. Add a tick box in firebase to enable "--auto-google-login" for a test

   I need to be able to auto login a user to get past google play services auto login screens please.

   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  ·  Test Lab  ·  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. Make Preview Channel URLs predictable or reusable.

   We are looking for a way to create predictable preview URLs for our Firebase Hosting preview channels. We require this functionality to whitelist these URLs for accessing a Cloud CDN authenticated content bucket. Currently, the preview channel URLs generated by Firebase Hosting include a random hash (SITEID--CHANNELID-RANDOM_HASH.web.app), which makes them unpredictable.

   The solutions we have devised include:

   • Replace the random hash for something like https://<PROJECT_ID>--pr-<PULL_REQUEST_NUMBER>.web.app
   • Make the preview channel URL persistent when deploying new versions.
   7 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

5. هكر اخلاقي

   تعليم التهكير الاخلاقي عن طريق الثغرات

   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  ·  Analytics  ·  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. apphosting for asia-northeast1 and asia-south1

   I am trying to deploy to asia-northeast1 and asia-south1

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

7. Deactivate the automatic sending of the email template with a checkbox

   Hello everyone,

   currently not all email templates can be changed. For example, when activating multifactor authentication, you have to be satisfied with the ugly automatically generated email from firebase. It would probably be an easy to implement development if you could deactivate the automatic sending of the email template with a checkbox. Then you could implement your own email dispatch. Please provide a way to disable the automatic sending of email templates.

   Thank you and best regards

   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

8. 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 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

9. 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

   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

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

    i cant create the Storage shows An unknown error occurred.

    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

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

11. Improve Billing Verification and Support for New Firebase Users

    Many new Firebase users face serious issues when trying to activate the Blaze plan due to strict and non-transparent billing verification processes.

    In my case:
    • I attempted to verify my billing using a Revolut card (registered under my name);
    • All payment confirmations were approved through the Revolut mobile app (4–5 times), yet the verification still failed;
    • No clear error explanation was provided, and I had no way to resolve the issue;
    • I tried adding a backup Korean card, but the verification message never arrived in the Korean mobile banking app (SMS also didn’t arrive because my Korean phone number is inactive);
    • After these attempts, my billing account was suspended and my project was blocked.

    Suggested improvements:
    1. Allow users to upload supporting documents to verify card ownership;
    2. Provide clear error messages when billing verification fails;
    3. Prevent automatic suspension after just a few failed attempts — especially when the card is verified by the bank;
    4. Offer a direct way to contact Firebase Billing Support for real-time help;
    5. Add an option to manually request a billing review instead of locking out users.

    This problem affects many developers who are just starting to use Firebase. Without proper verification and support tools, it’s nearly impossible to access key features like Cloud Functions and Hosting. Please consider improving this part of the onboarding process.

    If others have experienced similar issues — please vote for this idea. Let’s make Firebase more accessible for everyone.

    Many new Firebase users face serious issues when trying to activate the Blaze plan due to strict and non-transparent billing verification processes.

    In my case:
    • I attempted to verify my billing using a Revolut card (registered under my name);
    • All payment confirmations were approved through the Revolut mobile app (4–5 times), yet the verification still failed;
    • No clear error explanation was provided, and I had no way to resolve the issue;
    • I tried adding a backup Korean card, but the verification message never arrived in the Korean mobile banking app (SMS also didn’t arrive because my… 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

12. 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 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

13. Give firebase studio/project idx access to cloudshell scripts

    I want an ide with gemini which i can use to edit my cloudshell scripts, I see that there is cloud shell environment, would be nice if it is same as firebase studio.

    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  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. We want the code editor to be free for everyone.

    If it was free for everyone, we would be able to create beautiful and different projects, and the subscription should only be on Fire, or data storage, or Google's digital cloud. The code editor should not have a monthly subscription. It should be free for everyone, and this is the meaning of technology, that the basis should be free, but the dependencies should be paid. If it is necessary, for example, a free artificial intelligence model should be placed for the code editor, and also make it paid. But the code editor should be free for everyone, and this is an idea that will help everyone, and other than that, it will build a very huge community.

    If it was free for everyone, we would be able to create beautiful and different projects, and the subscription should only be on Fire, or data storage, or Google's digital cloud. The code editor should not have a monthly subscription. It should be free for everyone, and this is the meaning of technology, that the basis should be free, but the dependencies should be paid. If it is necessary, for example, a free artificial intelligence model should be placed for the code editor, and also make it paid. But the code editor should be free for everyone, and this is… more

    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

    1 comment  ·  Analytics  ·  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. PERSIST FIRESTORE COLLECTION SORTING CONDITIONS
    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

    2 comments  ·  Firestore  ·  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. Supabase intergation

    Linking supabase into Firebase like a MCP server

    12 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  ·  MCP Server  ·  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. 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

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

18. 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

19. API for NotebookLM

    Developer api to interact with notebooklm

    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

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

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