1236 results found

1. Emulator: Firestore requests with descending order + clear button

   The Firestore requests page in the emulator currently sorts the requests by ascending execution time, which requires to scroll to the very bottom every time to see the last request. Very cumbersome.

   The emulator should order by default by descending order and also offer a "clear" button to empty the list upon request.

   6 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  ·  Emulators  ·  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. dynamic robots.txt and favicon

   Add capability to dynamically change robots.txt and favicon. The current behavior returns 404.

   6 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

3. Adding Republic of Moldova to a preview list of Gemini

   Could you please add Moldova to the list of countries who can preview Gemini? We cannot use it in Android Studio and have to use other AI.

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

4. Can FirebaseAnalyticsOnDeviceConversion have multiple input functions?

   hi
   Documentation: https://firebase.google.com/docs/tutorials/ads-ios-on-device-measurement/step-2?hl=zh-tw
   First, let me explain my understanding of FirebaseAnalyticsOnDeviceConversion
   I understand that this SDK is to solve the problem that IDFA may not be obtained on iOS 14 and above, causing ads advertisers to be unable to track which user it is.
   Therefore, Google provides an SDK. By entering the user's email or mobile phone number, ads advertisers can perform tracking and comparison.
   but
   The [FIRAnalytics initiateOnDeviceConversionMeasurementWithEmailAddress:] method can only be set once in the app
   So if the app has a member login function that can switch accounts, the user analysis data received by ads advertisers may be wrong.
   So I hope it can provide multiple input methods to ensure accuracy?
   Not sure if my understanding of this document is correct?
   Thanks

   hi
   Documentation: https://firebase.google.com/docs/tutorials/ads-ios-on-device-measurement/step-2?hl=zh-tw
   First, let me explain my understanding of FirebaseAnalyticsOnDeviceConversion
   I understand that this SDK is to solve the problem that IDFA may not be obtained on iOS 14 and above, causing ads advertisers to be unable to track which user it is.
   Therefore, Google provides an SDK. By entering the user's email or mobile phone number, ads advertisers can perform tracking and comparison.
   but
   The [FIRAnalytics initiateOnDeviceConversionMeasurementWithEmailAddress:] method can only be set once in the app
   So if the app has a member login function that can switch accounts, the user analysis data received by ads advertisers may… more

   6 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

5. Increase request size over 32Mb

   Right now, a Firebase function can only accept a request payload size up to 32Mb.
   Using it as webhook for some external APIs, we would need to have no limits or at least 100Mb limit

   6 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

6. Remote Config REST API Improve Documentation

   For the Remote Config REST API, the documentation is fairly ugly around how to go about safely getting a valid ID token for a user to be able to use it. I'm suggesting you put the Remote Config API behind a set of user rules, similar to other Firebase technologies. If that cannot happen for some reason, then one of two things should:

   1. There should be some sort of option in Remote Config or Authentication to automatically give new users a valid credential that allows them to only retrieve the Remote Config (perhaps it automatically creates a Service Worker Account in IAM and generates the JWT for you, which it then returns and shows the user in their config json?). You suggest doing this via a Cloud Function, but many projects won't be on the Blaze plan (and can't), but this would still be useful for them. I know it's not much to ask to switch to Blaze for this, but then they also have to implement the Cloud Function and figure out how to do it for all authenticated accounts because there's no extension to set it up, which there should be (maybe that's a second request here).

   2. At least improve the documentation so that it's a lot more straight-forward to create a Service Worker Account in IAM and then generate a valid JWT for that SWA (I think it should be automatic and you should just be provided with it). I had to go through more than 10 steps to figure out how to do that, and the Firebase help person couldn't figure out an easier way to do it either (he just repeated back a bunch of the links I sent him to ask for help). Part of the issue is that the site you've selected to create the JWT is either different from when the docs were originally written, or it simply never worked and the person who wrote the docs was taking an extra step or two to make it work that aren't documented.

   There's also no indication after creating the JWT how to store it, which obviously is not up to you good folks, but the question I guess is whether or not letting it become public is secure. I know letting your private key become public isn't, but I wonder about the resultant JWT. With many applications that use the REST API, they are not encrypted in any way at rest, and so you end up having just an open JWT token that can be used with any permissions the SWA has - my GodotFirebase library being the primary example I can think of. I have mine locked down to just the RC read permission, but still, others might not know how to do this stuff inherently and make mistakes.

   Edit: I just realized that the Service Worker Account approach is really only intended for server-related work, which means it won't even work for my scenario. The documentation REALLY needs an update to make that clear. Now I have to suggest that if my users want to use my completely free and open source library, they have to go Blaze Plan and create a whole Cloud Function, and I have to supply the Cloud Function so they can automatically add Remote Config permissions to their user IDs that get returned. This is so, so ugly.

   Edit 2: I just realized what my issue is. I don't have access to the new Installations API through REST. Is it possible to allow that? That way, at least I can get an appropriate token to be able to send to the API without having to store the token somehow on my device, or force my users to use a Cloud Function and have to go paid while removing their ability to use A/B testing (the Admin SDK only returns the default template).

   For the Remote Config REST API, the documentation is fairly ugly around how to go about safely getting a valid ID token for a user to be able to use it. I'm suggesting you put the Remote Config API behind a set of user rules, similar to other Firebase technologies. If that cannot happen for some reason, then one of two things should:

   1. There should be some sort of option in Remote Config or Authentication to automatically give new users a valid credential that allows them to only retrieve the Remote Config (perhaps it automatically creates a Service Worker Account… more

   6 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

7. Manual reloading of firebase functions in emulator

   I'm suggesting this feature of nodemon:

   https://github.com/remy/nodemon?tab=readme-ov-file#manual-restarting

   Sometimes when inner dependencies changes, firebase emulator don't detect changes. So whenever I make a change in my large project, I have to always shutdown firebase emulator and restart it.

   6 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  ·  Emulators  ·  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. Descriptions for Tester groups

   It would be nice to be able to add a description to App Distribution tester groups so that we can add instructions for other admins that manage the same dashboard. We impose limits on who should and shouldn't be added to certain groups, and while this is enforced by tooling we periodically run, it would be nice to have proactive instructions for other admins to see instead of always having to reactively act to revert unwarranted changes.

   6 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

9. RecaptchaVerifier should provide access to the shared secret

   I'm creating a Contact form in a React app, which stores the user input in firebase. I'd like to secure the form with a visible reCAPTCHA, and I'm trying out firebase's built-in reCAPTCHA functionality.

   firebase/auth/RecaptchaVerifierdoes provide a callback, which can be used to sign in a user, and documentation shows it working when signing in with a phone number. Can it be used with anonymous authentication though?

   When the form is submitted, I have a server component that saves the form fields to firestore. However, how can I verify the recaptcha before committing the data to firestore?

   I feel like the server component that commits to firestore needs to first verify g-recaptcha-response submitted with the FormData. But to do that, to use the reCaptcha API to verify the recaptcha response, requires a secret shared between my site and the reCaptcha API. Can my server component handling the form submission access the shared secret that firebase auth automatically creates?

   Some references:-

   https://firebase.google.com/docs/auth/web/phone-auth#set-up-the-recaptcha-verifier
   https://developers.google.com/recaptcha/docs/verify

   I'm creating a Contact form in a React app, which stores the user input in firebase. I'd like to secure the form with a visible reCAPTCHA, and I'm trying out firebase's built-in reCAPTCHA functionality.

   firebase/auth/RecaptchaVerifierdoes provide a callback, which can be used to sign in a user, and documentation shows it working when signing in with a phone number. Can it be used with anonymous authentication though?

   When the form is submitted, I have a server component that saves the form fields to firestore. However, how can I verify the recaptcha before committing the data to firestore?

   I feel… more

   6 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

10. Encrypted Collections in Firestore

    Ability to mark certain collections to be Encrypted so it's not readable even in the firebase console.

    There are some application types that require this sort of behaviour to increase security.

    Say you are building a messaging app, you would not want the messages between your users to be seen on the console.

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

11. Firebase Test Lab IAM should allow making Test Results, with records and what not, fully publicly accessible

    See https://github.com/google/android-fhir/issues/2218:

    For e.g. public open source projects, it would be very useful if Firebase Test Lab IAM could be configured to allow making Test Results, with records and what not, fully publicly accessible.

    According to the discussion on Firebase Support Case 10251960, "Making test results publicly available is something that's not yet possible on our end. "

    6 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  ·  Test Lab  ·  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. Apple Privacy Manifest

    Dear SDK developer,

    Apple has introduced a new privacy policy at WWDC2023, requiring privacy-impacting SDKs to provide:

    1. Signed version. （https://developer.apple.com/videos/play/wwdc2023/10061）

    2. Privacy manifest file embedded in the SDK. （https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_data_use_in_privacy_manifests）

    Therefore, we would like to know:

    1. Which version of the SDK currently meets Apple's requirements?

    2. If the SDK is still under development for privacy-related features, how long until a version compliant with the new regulations can be provided?

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

13. Support hierarchical google-services.json

    When you define multiple build types for your application you need to create a google-services.json file for each build type, eg : app/src/flavor1, app/src/flavor2, app/src/flavor_3

    This becomes cumbersome when using multiple build flavors. It would be great if
    1. the flavor directories acted as optional overrides of a default
    2. the hierarchy for google-services.json respected initWith, e.. if I create a buildType1 with "initWith debug" I should be able to use the debug/google-services.json unless I try to overwrite it.

    6 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. Pass all cookies to Cloud Functions or Cloud Run

    Right now only a _session Cookie is passed.
    https://firebase.google.com/docs/hosting/manage-cache#usingcookies

    6 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

15. A/B Testing activation and goal event with event params

    Currently in A/B Testing users can set activation and goal events using only event names.

    It would be awesome to have an option to use a generic event with its params. Eg. using a screen_view event with screen_name as activation event for entering a specific screen instead of creating a custom event just for testing purpose.

    It would be beneficial for heavy A/B Testing users, especially taking into account that they can create only 500 custom event names. And don't make me tell you that creating a custom event or two for every A/B test can burn those 500 event names pretty fast.

    Currently in A/B Testing users can set activation and goal events using only event names.

    It would be awesome to have an option to use a generic event with its params. Eg. using a screen_view event with screen_name as activation event for entering a specific screen instead of creating a custom event just for testing purpose.

    It would be beneficial for heavy A/B Testing users, especially taking into account that they can create only 500 custom event names. And don't make me tell you that creating a custom event or two for every A/B test can burn those 500 event… more

    6 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

16. Customise device name for Events DebugView's device selector

    The device selector mentioned here: https://firebase.google.com/docs/analytics/debugview#device_selector consist of only generic device names (e.g. x86 64 for iOS simulator). For our app we can see many sessions (e.g. 6/8 right now) and all of them show "x86 64". It always takes few minutes to find "my" session for debugging.
    It would be nice to have a way e.g. to customize device name (e.g. via Firebase API Analytics.setDeviceName("Przemyslaw's simulator")) so a developer could find their session immediately.

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

17. Phone number for testing in firebase emulator

    It would be great to be able to configure static MFA validation codes / phone numbers for testing in the emulator, like in the normal firebase auth product.

    This would make testing an application with automated tests a lot easier.

    6 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  ·  Emulators  ·  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. Lazy loading of items in firebase console for firestore

    Console has become laggy and returns a wait for page to load alert if a document has to many fields

    6 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  ·  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. Execution ID in logs generated by Firebase Functions v2

    Logs generated by Firebase Functions v1 have the property labels.execution_id that can be used to correlate logs that pertain to the same execution. However, that property doesn't exist in logs generated by Firebase Functions v2. It's very important for debugging.

    6 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

    3 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

20. Wildcard index exemptions

    Firestore automatically indexes all fields in all collections adding to storage size and slowing write performance.

    We can add single-field exemptions but we need to list all fields separately and there is a database-wide limit of 200 field exemptions.

    In a highly optimised use case we would want to index only specific fields that we know we query on, and just exclude all others.

    It's almost like the current behaviour is a database for novices, but we can't optimise for serious production.

    We need either a wildcard exclusion, or effectively just a switch/setting that says "only fields with explicit index definitions".

    Firestore automatically indexes all fields in all collections adding to storage size and slowing write performance.

    We can add single-field exemptions but we need to list all fields separately and there is a database-wide limit of 200 field exemptions.

    In a highly optimised use case we would want to index only specific fields that we know we query on, and just exclude all others.

    It's almost like the current behaviour is a database for novices, but we can't optimise for serious production.

    We need either a wildcard exclusion, or effectively just a switch/setting that says "only fields with explicit index… more

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