728 results found

1. Auth onCreate and onDelete triggers for v2 functions
   45 votes

   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

   5 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

2. Remote Config Emulator

   Provide a native emulator for Remote Config with A/B tests will be great, but is not critical.

   4 votes

   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

3. 我在Google开发者平台提交技术支持抛出"Error submitting request. Please try again later."错误，致使我无法寻求帮助。

   我在Google开发者平台提交技术支持抛出"Error submitting request. Please try again later."错误，致使我无法寻求帮助。我不知道为什么会这样.....

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

4. Allow customization of email template message
   52 votes

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

5. Multi-line strings when A/B testing

   In firebase remote config you can have a multi-line string (ie have new lines), but as far as I can tell this isn't possible when setting up the variant in an A/B test this means we can't make small A/B test changes to multi-line text

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

6. Security key/WebAuthn 2FA

   Currently, we only have the option to use TOTP 2fa or SMS. Security keys are quickly gaining popularity, as it is a more secure option. Please add this.

   2 votes

   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

7. Projecct ID can be change

   I wish that there is at least one chance to change the project id because some times we choose random names just to test our project then we make it as production and in this state we cant change the random name we choose before

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. MLKit for Web
   50 votes

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

9. Expand auth blocking functions

   Support some additional data sent during the signInWithEmailAndPassword that can be read in the beforeCreate

   3 votes

   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

10. Make it possible to block/disable services

    For security, I would like to be able to completely disable functions in my account. So nothing can be done without an extra authentication (e.g. admin password).

    This to prevent large bills due to errors in the software or due to bad actors. Especially since this whole Google Cloud is completely connected to Firebase, the risk of a mistake or a bad actor is higher

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

11. 5 emails

    I saw this on the documentation website: "Note: The limits for email link sign-in emails were recently changed. Please add a billing instrument to go beyond 5 email link sign-in emails."

    It's really strange that you quietly set the limit of sign-in emails to 5. Why? It makes no sense. For testing it's too low, and for production of course.

    First you hook developers up to Firebase and then you quietly lower the limits. Good business practices.

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

12. Support deleting collections in the API

    Currently you can only delete collections programmatically via the CLI. Otherwise, you have to list and delete every single document in the collection. If those documents have nested collections, you have to (recursively) retrieve and delete every document in the nested collection (As deleting a document does not delete any nested collections the document has). If there are additional levels of nested collections... You get the idea.

    I wasn't sure what this other request was referring to so I made this one: https://firebase.uservoice.com/forums/948424-general/suggestions/46562317-api-support-for-deleting-directories

    7 votes

    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

13. Specify fixed version when closing a crash in Crashlytics
    49 votes

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

14. Orderby('any_potential_null_field', excludeNull: false) should exist

    OrderBy should be able to return collection item when target property is null.

    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

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

    3 votes

    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

16. The ability disable default domains
    46 votes

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

17. Allow SMS customization & add Web OTP support

    Web OTP support increased phone authorization conversion significantly.
    Currently, We are not able to customize SMS messages to comply
    https://developer.chrome.com/en/articles/web-otp/#format

    43 votes

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

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

    3 votes

    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

19. Firebase messaging SDK with proper error response message in emulator

    I encountered an issue while attempting to emulate the sending of push notifications with a Firestore Cloud Function. Despite having valid tokens set up, I received an error response. The error messages I received after attempting to send two push notifications individually were as follows:

    "Error: Requested entity was not found."
    "Error: The registration token is not a valid FCM registration token."

    Ideally, I would expect to receive a 200 or 403 response along with a message indicating that the message was sent successfully, but that this is only an emulation environment. Upon deploying the latest version of my script and testing it in a production environment, I discovered that there was nothing wrong with my code.

    I encountered an issue while attempting to emulate the sending of push notifications with a Firestore Cloud Function. Despite having valid tokens set up, I received an error response. The error messages I received after attempting to send two push notifications individually were as follows:

    "Error: Requested entity was not found."
    "Error: The registration token is not a valid FCM registration token."

    Ideally, I would expect to receive a 200 or 403 response along with a message indicating that the message was sent successfully, but that this is only an emulation environment. Upon deploying the latest version of my script… more

    3 votes

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

20. Add Query Explain to Firestore query builder (in Firebase Console)

    I would like to understand a query using Query Explain. It would be easier to have the option to use Query Explain via the Firebase Console instead of code with the SDKs (also requires to set up the credentials, etc.).

    2 votes

    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