Skip to content

General

General

Categories

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

418 results found

  1. Currently, Crashlytics does not support integration with Jira Server (on premise) v9.0+. I suggest that also this variant of Jira is supported since everybody isn't running Jira Cloud.

    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)
  2. I have some queries that I perform frequently through Firestore Query Builder. It would be great to save queries to be able to run them with one click.

    1 vote

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Google requires a web link that enables users to delete all their data, even after they have uninstalled the application. For a "serverless" app that only uses Firebase Auth, it would be ideal to have a plug-and-play solution for hosting a single webpage that complies with Google Play's policy.

    8 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. The current Unity SDK supports only Android ("Google Play" in some cases), iOS and Unity Editor.
    Make it support multiple platforms, like WebGL, Consoles, etc as much as possible.

    9 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)
  5. Currently exception events are gathered as one issue depending solely on the actual exception location and its type.
    Moreover, every such event pops all previous ones as regressed.
    This makes it hard to follow the different issues. It is specifically a big problem where a fallback is used, with non-fatal crash reports in it. All crashes that ended up with the fallback are reported as one.
    My suggestion is that different call stack and/or message will be shown as different issues. (Possibly with an option to set the differing place in the stack)

    1 vote

    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  ·  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)
  6. Allow for deployments to be either a green or blue deployment to be able to have multiple instances of the same functions deployed within a single Firebase project.

    This would help cover the gap of time between releases of client apps and Cloud Functions, which if not handled correctly cause production issues.

    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)
  7. When I hosted a frontend client (React JS) and backend (NodeJS) server in hosting and functions combination, there were some scenarios where in I needed to send data (to server) which contained slash (so encoded them).

    This was where the problem rose, the encoded component was automatically decoded by the firebase hosting itself and sent the wrong url to the underlying server.

    Therefore firebase should give us the ability to turn on/off the decoding of encoded data url in firebase.json

    my current firebase.json file -

    {
    "functions": [
    {
    "source": "functions",
    "codebase": "default",
    "ignore": [
    "nodemodules",
    ".git",
    "firebase-debug.log",
    "firebase-debug.

    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

    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)
  8. Similar to the way we can define an index in firestore with firestore.indexes.json. I'm proposing a firestore.ttl.json where the TTL properties would be deployed upon firebase deploy, instead of having to go in the console UI or alternative methods.

    Those configuration files are useful when switching environment as this minimize the configuration required when going from dev, to staging, to prod. Centralizing those in one place makes it easier.

    1 vote

    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  ·  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)
  9. Most keys that can be copied in firebase have a copy icon next to it. This one does not.

    1 vote

    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  ·  Cloud Messaging  ·  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. 9 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)
    • In the Firebase CLI
    • In the Firebase Console
    9 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. 9 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)
  12. Create Firebase A/B Testing Experiments through Firebase API or Firebase SDK

    Please provide some provision to create A/B testing experiments programmatically. Apart from Firebase console, it is good to create A/B testing experiments through API or SDK or any other way?

    Please check.

    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)
  13. With Firebase, you can have real time listeners on Firestore documents, which allow to have your UI in sync with your data.

    But when you ship logic in an app, you lose control over it.

    If you want to be able to update that logic after shipping, you place it in the backend (Cloud Functions), but then you lose real time updates.
    It would be amazing to have functions that can fire real-time events based on Firestore updates.

    So the flow would be:
    - There is an update in a Firestore document (or potentially other triggers like pub/sub, analitycs, etc.)…

    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)
  14. If you have split your data in several collections there should be an easy way to update a linked document - for example if the user changes his name, all articles with the authorId = userId should be updated automatically

    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

    1 comment  ·  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)
  15. When a crashlytics issue occurs, it creates a new issue in linear with a link to the crashlytics dashboard.
    When a crashlytics issue is closed, close the associated issue in linear.
    When a linear issue is closed, close the associated issue in crashlytics.
    When a crashlytics issue receives velocity alerts, it increases issue priority in linear.

    1 vote

    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)
  16. Currently there is only a list of error codes the Admin SDK can receive, not for the web sdk.

    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)
  17. When a project grows to a certain size, you'll likely have many indexes with associated queries.

    However, queries change, or get removed, and currently there's no way to see if an index could be safely removed, after a query is; which would be a great feature.

    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Currently, we can just configure one language for every user on the authentication template page. It seems to be possible using "custom email action handlers" but this requires an additional work that is not mentioned in the doc. This lack of option and the additional work to have a usable product in a professional context should be mentioned in the Email Link Authentication doc.

    1 vote

    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  ·  Other  ·  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. It would be great to be able to have different remote config configurations (e.g. feature flags) for different preview channels.
    This is important to be even able to use/test/QA the preview channel build if we don't want to rollout the feature globally yet (mostly in the last stages of development).

    Note: For native apps we solved this by using specific version numbers (that are used only for preview builds), but for web apps the version condition is greyed out.

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