1216 results found

1. كتابه
   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  App Distribution  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Disables support for TLS 1.0 and TLS 1.1 as these are vulnerable versions

   Is there a plan to disable support for TLS 1.0 and 1.0 version across the domains e.g. firebase console, fcm.googleapis.com and other services?

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

3. Firebase Auth with IP address whitelist & blacklist

   Blacklist scenario: Let's say that a device is detected for fraud/scam activity. I want to blacklist the device for 1 year based on the previously logged-in IP address, so the scammer is no longer able to use their devices. Even though the scammer created a new Firebase account, they won't be able to do that because of the IP address blacklist.

   Whitelist scenario: Let's say that I have an internal app. I want this app to be used by my employees only, so only specific devices are allowed to login.

   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  ·  Authentication  ·  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. Table Event Triggers

   In additional to the onMutationExecuted, we would love to have events on table mutations.

   • onRowUpdated
   • onRowCreated
   • onRowDeleted

   onMutationExecuted is already launched in Nov 2026. https://firebase.blog/posts/2025/11/dataconnect-nov25

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

5. Nikhil petkar

   Any update online voting

   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

   3 comments  ·  Dynamic Links  ·  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. Add support for pnpm workspaces

   While it does support for pnpm, it does not support pnpm workspaces. The reason for this is because it currently looks for the pnpm-lock.yaml file in the workspace app directory, but this file is actually in the root directory when using workspaces. This causes lots it to switch to using npm and the build to fail.

   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

7. Data connect Full-text Search

   First of all, thank you so much for the new Full-text Search feature! :)
   In our team, we would really love the following more advanced features, if possible, related to it:
   - Fuzzy matching: it would allow searches to be resilient to common typos and misspellings.
   - Prefix matching: it would enable users to find words that start with a specific string of characters, such as "invoic" returning "invoice," "invoices," and "invoicing."
   - Column-Specific Search: Instead of searching across all marked "searchable" columns, I would like to choose to focus a specific query on a specific subset. This would be useful to our catalog feature where we have suggestions that, when clicked, should search only on a specific column. At the state of art, the only way possible to obtain this would be to create different tables.
   - Getting All Results When the Query is Empty: When the search bar is empty, the system would display all data in the selected table or view. At the current state of art, this is only possible by creating two separate queries: one for the empty search bar, and one when the search bar has a query on it.

   First of all, thank you so much for the new Full-text Search feature! :)
   In our team, we would really love the following more advanced features, if possible, related to it:
   - Fuzzy matching: it would allow searches to be resilient to common typos and misspellings.
   - Prefix matching: it would enable users to find words that start with a specific string of characters, such as "invoic" returning "invoice," "invoices," and "invoicing."
   - Column-Specific Search: Instead of searching across all marked "searchable" columns, I would like to choose to focus a specific query on a specific subset. This would be… more

   11 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

8. 103605920

   5.000$

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Agent Skills  ·  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. Integrate Firebase product and developer notifications with Google Cloud Essential Contacts

   Larger customers often use Google Cloud Essential Contacts for ensuring critical notifications get to the right people. Currently Firebase product and developer communications seem to go out via email to named user accounts where the customer has no control who this goes to and it may miss its intended audience.

   It would be great if FIrebase notifications could be integrated with Google Cloud Essential Contacts to give customers more control over where critical notifications go to and to make this consistent with other Google Cloud services.

   https://docs.cloud.google.com/resource-manager/docs/managing-notification-contacts

   Thank you!

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

10. More information in errors for native sql statements

    Errors in native sql statements like in _execute always result in the same "Invalid SQL statement" error without any further information, which makes it really difficult to debug. More data - for example the part of the SQL statement that is invalid - would be really helpful! Especially as this error also seems to be thrown when the SQL is perfectly fine but a wrong _execute syntax is used, which should not throw an "Invalid SQL statement" error, as it is not about SQL!

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

11. Fastlane - Get automatically app key from google-services.json

    All Android application that included Firebase have mandatory this file : google-services.json

    When we want automatize delivery with fastlane on Firebase, we need to provide many informations on the lane such like "app", "servicecredentialsfile",...

    In fact, many Android projects has one or more build flavors and the delivery can be harder with the configuration on which target we want to deploy.

    We need to store many sensitive informations like key on the env file.
    We not push this file on the repository and it's not a good practice to have them has CI variables.

    The purpose of this feature request is to automatize the retrieve of app key from google-services.json.
    For this, we just need few informations on env / CI file :
    - location of google-services.json (that can be split in an other feature) *1;
    - package name declared on env / CI file.

    Only with your package name, you can retrieve (or not) your app key from google-services.json.
    This is a snippet of code for make this one :

    Parse the JSON content

    jsondata = JSON.parse(filecontent)

    Search for the appid corresponding to the packagename

    appid = ""
    jsondata["client"].each do |client|
    if client["clientinfo"]["androidclientinfo"]["package_name"] == targetpackagename
    appid = client["clientinfo"]["mobilesdkapp_id"]
    break
    end
    end

    All Android application that included Firebase have mandatory this file : google-services.json

    When we want automatize delivery with fastlane on Firebase, we need to provide many informations on the lane such like "app", "servicecredentialsfile",...

    In fact, many Android projects has one or more build flavors and the delivery can be harder with the configuration on which target we want to deploy.

    We need to store many sensitive informations like key on the env file.
    We not push this file on the repository and it's not a good practice to have them has CI variables.

    The purpose of this… more

    15 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

12. Evaluate Mutation Results in Realtime Refresh Conditions & Support Mutation-Side Triggers

    Currently, when configuring a refresh condition on a query, the condition can only evaluate the triggering mutation's variables and auth (uid/token). We cannot check the actual result (response) of the mutation.

    This creates a significant friction point when mutations are executed from non-client environments, such as a Cloud Function triggered by another backend service (e.g., Firebase Storage). Because the Cloud Function executes without the end-user's auth context, the only way to accurately filter the query refresh is to pass the userId into the mutation's variables. This feels like an unnecessary workaround just to satisfy the refresh condition.

    To make real-time cache invalidation cleaner and more robust for server-side triggers, you need

    • Access to Mutation Results in Query Conditions
    • Mutation-Driven Triggers:

    Currently, when configuring a refresh condition on a query, the condition can only evaluate the triggering mutation's variables and auth (uid/token). We cannot check the actual result (response) of the mutation.

    This creates a significant friction point when mutations are executed from non-client environments, such as a Cloud Function triggered by another backend service (e.g., Firebase Storage). Because the Cloud Function executes without the end-user's auth context, the only way to accurately filter the query refresh is to pass the userId into the mutation's variables. This feels like an unnecessary workaround just to satisfy the refresh condition.

    To make real-time… 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)  ·  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. Production Multi-Provider Integration Scheme For production readiness, for the Google IO 2027 release

    Production Multi-Provider Integration Scheme For production readiness, for the Google IO 2027 release a service that after staring into your devices camera for 20 seconds will log you into any account email platform or social media that's ever log your face and stored it in the cloud

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. تطبيق حجز مواعيد الأطباء وطلب الادويه

    قيام التطبيق بالحجز عند الأطباء ورفع روشته المريض لطلب الادويه من الصيدليات

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Propagate Original Client IP through Firebase Console Proxy for VPC-SC Enforcement

    We are encountering a block when placing our project under VPC Service Controls enforcement. When a user attempts to access the Storage tab in the Firebase Console, it fails with an "Unknown Error" (Audit logs show NOMATCHINGACCESS_LEVEL with an empty clientIp). The Firebase Console currently acts as an internal proxy, routing traffic through Google's internal infrastructure. Because it traverses these internal paths, the end-user's local corporate egress IP is entirely stripped before the API payload reaches the protected Storage endpoint (storage.googleapis.com). We have strict compliance requirements to restrict access solely to trusted corporate network IPs, meaning the standard VPC-SC workaround of allowing all sources (accessLevel: "*") is not an option for us. We request that the Firebase Console backend be configured to extract and propagate the end-user's context. Specifically, the One Platform service configuration should be updated to request google.rpc.context.OriginContext in the context.rules section of the service YAML. This will allow the original client IP to pass through the GFE/proxy so that VPC-SC can accurately evaluate the IP against our perimeter policies.

    We are encountering a block when placing our project under VPC Service Controls enforcement. When a user attempts to access the Storage tab in the Firebase Console, it fails with an "Unknown Error" (Audit logs show NOMATCHINGACCESS_LEVEL with an empty clientIp). The Firebase Console currently acts as an internal proxy, routing traffic through Google's internal infrastructure. Because it traverses these internal paths, the end-user's local corporate egress IP is entirely stripped before the API payload reaches the protected Storage endpoint (storage.googleapis.com). We have strict compliance requirements to restrict access solely to trusted corporate network IPs, meaning the standard… 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 Storage 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

16. Storage

    Unable nahin ho raha hai

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

17. More regions app hosting

    Please do more regions like Australia for app hosting as some businesses have strict region requirements

    16 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

    4 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. API support for insertMany and updateMany

    Currently Data Connect insertMany and updateMany mutations do not support being passed multiple records via the SDK. Figure out a way to enable this so we can insert multiple rows in the same “@transaction” via the API.

    37 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

19. Support 2nd generation (v2) Firebase Functions in Firebase Extensions

    2nd generation Functions are better in every way and are recommended for almost all new Functions, but can't be used in Extensions (for most trigger types).

    https://firebase.google.com/docs/extensions/publishers/functions

    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  ·  Extensions  ·  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. Cloud Firestore Datasource

    Support Cloud Firestore as a datasource for Data Connect in addition to Cloud SQL. Support data model mapping (e.g. @collection) and querying via GraphQL

    188 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

    11 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