Skip to content

General

General

Categories

JUMP TO ANOTHER FORUM

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

30 results found

  1. Documentation about conditions for iOS and Android is lacking proper description for semver logic on parameter 'AppVersion'

    It seems that the condition properly evaluate operators
    >
    >=
    <
    <=
    when the app version is a semver string i.e. 1.18.10 > 1.18.2

    but the documentation states that above operators are only working with numeric values :

    "...
    For string values:
    exactly matches,
    contains,
    does not contain,
    contains regex

    For numeric values:
    <, <=, =, !=, >, >=
    ..."

    The logic behind semver is very important and specific.
    To use it safetly we really need to be sure that the comparison is…

    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)
  2. 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)
  3. Current data fetch is not filtered at query level and all of your config fetches to your frontend. This means for example, IOS app fetches IOS, Android and Web config if all apps fall under the same project.

    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)
  4. This would allow developers to find out if a certain feature is causing a terrible user experience for a small group of users, despite not showing up in top level metrics.

    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)
  5. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Remember sort order for remote config view so you don't have to change the sort every time the console page is refreshed.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. We have several events with the prefix "Firebase_" for irrelevant reasons. These events were successfully added to Google Analytics by sending them via mParticle.

    We can view statistics for these events, but we cannot use them as goals for A/B tests. The UI displays the following error:
    "Error: Error saving experiment: Can't validate experiment data."
    The server response states:
    "Cannot use reserved event name: '<event name>'."

    The suggested workaround is to create new events with non-reserved names based on these existing events. However, there are limits on the number of events you can create, and this adds unnecessary work.

    Since…

    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  ·  Remote Config  ·  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. Remote config fetched values are not encrypted and it's kept as plain text. Is there any function that can be used to clear this data after a successful fetch? At least we can keep the data safe on our own if there's a way to clear the local file content. I know currently it keeps the last fetched time in the same file but a clear function can clear all values except values like last fetch time. Will be very useful for those who want to use remote config data securely

    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  ·  Remote Config  ·  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. Consider the scenario where you create a new Remote Config parameter in your template.json file and deploy it via the Firebase CLI to TEST and PROD environments with a default value. You then modify the value in PROD via the Firebase console. The next time you deploy Remote Config to PROD the value is overwritten. It would be useful for CI/CD deployments to have an option that would only deploy new parameters and would NOT overwrite the values for existing parameters. This would allow you to structure your template.json file to have default values for new non-PROD environments without having…

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

    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  ·  Remote Config  ·  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 Next →
  • Don't see your idea?