Skip to content

General

General

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

546 results found

  1. Emulators are meant for rapid testing.

    There should be a tool that enables easy fine/grain control for importing and exporting data from the Firebase UI for Firestore, Storage, and Auth from the user interface.

    Trying to manually modify data in the interface is fairly awful.

    It would be nice to be able to mix and match different pre-made documents or collections to set up different types of environments.

    The command line import/export is ok, but still fairly tedious and limiting in its setup.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Emulators  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 16 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Currently, it is entirely possible for a user to reset a password that is unsecure with firebase's miniapp

    it does not validate against the default password conditions or reference the identity toolkit policies

    a community member has created a temporary fix
    https://betterprogramming.pub/firebases-password-reset-is-insecure-here-s-how-to-fix-it-882629e3b779

    I propose this reset dialog gets enhanced to a standard.
    and allow projects to integrate password policies from the identity toolkit
    https://cloud.google.com/identity-platform/docs/password-policy

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Allow deployment from CLI of specific extensions, to avoid uploading and updating all extensions unnecessarily.

    i.e. firebase deploy --only extensions:<name of extension>

    Just like we can with functions.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Firebase CLI  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Currently you can only add blocking functions for User signup and User sign in. I want to be able to add a Blocking function for User Reset password.

    This way I can customize password requirements at the API level and implement features in Cloud functions + Firestore such as preventing previous password reuse.

    I would have used Cloud Functions + Firestore for my Blocking function, but because this feature didn't exist I ultimately decided to move my auth password checks to my AWS hosted backend API.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. 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.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. I work for a company that enable people to record sports using video and the storage footprint are often very huge (10GB+). While building an app for iOS, I notice that Firebase don't support continuing uploads across process restarts on iOS which is a major deal-breaker for continuing using Cloud Storage for Firebase.
    I see support for this on Android and I will encourage you to add this to iOS in the future. Ref: https://firebase.google.com/docs/storage/android/upload-files#continuing_uploads_across_process_restarts

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. GitHub Apps are now the preferred alternative to GitHub Oauth Apps. When authenticating with Firebase Auth and a GitHub App, the app is "authorised" but not "installed", which can lead to inconsistent behaviour (https://github.com/orgs/community/discussions/61677). It would be nice if the GitHub provider had an option for prompting the user to "Authorise and Install" rather than only "Authorise".

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 15 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Extensions  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 16 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Jvm languages are not supported in Cloud Functions today, so developers need to use more than one language in their code base.

    15 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SDKs  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. I just spent a week implementing a plugin before realizing it was using Node 12. Deleted all my extensions after that, all using Node 16.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Extensions  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Crashlytics SDK provide support for in iOS app extensions. including the extensions that run in background. For example Location Push Service Extension.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Crashlytics  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Squarespace has a featured for "site-wide password protection" which is useful for staging unlaunched websites for stakeholders to review. This would help guard against any potential leaks.

    Figma also has a feature similar to this.

    We currently have to create a custom express.js server with an authentication middleware, but this is undesirable for several reasons:

    • We'd have to re-create all of firebase hosting's serving features (i18n fallbacks, redirects, pretty urls, etc.)
    • We can't easily test endpoints that are proxied to Functions/GCR
    15 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Hosting  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. There is a limit of 200 indexes per database currently. Sometimes I create indexes in development that never get used again. I do not want to delete indexes "I think are not being used". Having a "Last Used" column for indexes would allow me to know whether or not I can delete an index.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. In this code await admin.auth().createUser({
    email: email,
    displayName: name,
    uid: uid,
    emailVerified: false,
    password: password,
    disabled: false,
    });, if email and password are created, please create the user via that login method and if only phone is provided and no email, then let the user be created via phone auth. So that later on, when they try to sign in via phone auth, the system doesn't create a whole new user with a new uid but just lets the user sign into that account

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. 16 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Hosting  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. 16 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Crashlytics  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. 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.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?