762 results found

1. The errors thrown for a wrong password and an account that does not exist should be different

   This is a problem I have encountered while using Firebase with Swift. I want to be able to prompt the user to sign up if they do not have an account. However, the error returned from Auth.auth().signIn(withEmail, password) is the same if the user enters the wrong password or an email the doesn't exist. If the errors were different I would be able to show the sign up prompt only if that specific error is thrown.

   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

   Submit Rating

2. Add Q&A about including Firebase Analytics in a library to be used by arbitrary 3rd party apps

   It seems it is not recommended or possible, but I lack an official answer:

   https://stackoverflow.com/questions/60076980/how-to-add-firebase-analytics-in-a-library

   https://stackoverflow.com/questions/38790977/include-firebase-analytics-in-library?noredirect=1&lq=1

   https://www.reddit.com/r/androiddev/comments/fpxna8/firebase_analytics_in_android_library/?rdt=40331

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

   Submit Rating

3. Please change "Get Started" button to "Create Firebase Storage".

   Please do kindly consider changing the button name from "Get Started" more specifically to "Create Firebase Storage" within Firebase console. One gets the impression via "Get Started" that the user is in for marketing fluff than actual and crucial utility. Thank you.

   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  ·  Cloud Storage for Firebase  ·  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

   Submit Rating

4. Support Functions on App Hosting

   Firebase Functions don't seem to be well supported in App Hosting. At least if you are using Typescript in the functions, the deploy process runs into an error in the build step. It seems to be because "npm run build" runs Typescript checking everywhere, and the dependencies in functions/package.json haven't been installed.

   A user on Stack Overflow who asked about this ended up working around it by setting tsconfig.json to ignore the functions directory. They also have to do a manual deploy of the functions, because apparently the App Hosting deploy process doesn't do it.

   Ideally everything should just work; type checking in functions would happen separately from the next.js code, and functions would get deployed automatically.

   Here's the error from the build process:

   Running "npm run build"

   chatfront@0.1.0 build
   next build
   Attention: Next.js now collects completely anonymous telemetry regarding usage.
   This information is used to shape Next.js' roadmap and prioritize features.
   You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
   https://nextjs.org/telemetry
   ▲ Next.js 15.2.1
   Creating an optimized production build ...
   ✓ Compiled successfully
   Linting and checking validity of types ...
   Failed to compile.
   ./functions/src/index.ts:10:25
   Type error: Cannot find module 'firebase-functions/v2/https' or its corresponding type declarations.
   8 | */
   9 |
   10 | import {onRequest} from "firebase-functions/v2/https";
   | ^
   11 | import * as logger from "firebase-functions/logger";
   12 |
   13 | // Start writing functions
   Next.js build worker exited with code: 1 and signal: null
   Done "npm run build" (29.986122243s)

   Firebase Functions don't seem to be well supported in App Hosting. At least if you are using Typescript in the functions, the deploy process runs into an error in the build step. It seems to be because "npm run build" runs Typescript checking everywhere, and the dependencies in functions/package.json haven't been installed.

   A user on Stack Overflow who asked about this ended up working around it by setting tsconfig.json to ignore the functions directory. They also have to do a manual deploy of the functions, because apparently the App Hosting deploy process doesn't do it.

   Ideally everything should just work;… more

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

   Submit Rating

5. Realtime database, change default tab order

   Reorder the tabs in Realtime DB to prioritize displaying the rules or a landing page before the data.

   New users and analytics management find that loading the Realtime Database section from the web console impacts bandwidth usage for reads. This behavior is not ideal and could be separated from the Realtime Database landing page, especially when editing or inspecting the rules, as it requires loading larger chunks of the database before the user switches tabs.

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

6. Realtime database, change default tab order

   Reorder the tabs in Realtime DB to prioritize displaying the rules or a landing page before the data.

   New users and analytics management find that loading the Realtime Database section from the web console impacts bandwidth usage for reads. This behavior is not ideal and could be separated from the Realtime Database landing page, especially when editing or inspecting the rules, as it requires loading larger chunks of the database before the user switches tabs.

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

   Submit Rating

7. Turborepo support for Next.js apps

   AppHosting now supports nx based monorepo but we would love to see turborepo + pnpm workspace support for AppHosting.

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

   Submit Rating

8. Customizable Filename for iOS Artifacts in Firebase App Distribution

   Description:

   We have identified an area for improvement regarding the naming of iOS artifacts in Firebase App Distribution. Currently, when an IPA file is downloaded from the Firebase App Distribution console, it is automatically named app.ipa regardless of its original filename.

   Background:

   Our investigation revealed that, based on Google’s public documentation [1] [2], there is no available method to customize the filename during download.

   Firebase App Distribution automatically assigns the name app.ipa for iOS artifacts as a default behavior, and this is not configurable via the console or CLI.

   Request:

   We propose the introduction of a feature that allows users to customize the downloaded filename for iOS artifacts. This could be implemented either as an option in the Firebase console or through an additional parameter in the CLI. Such a feature would greatly enhance flexibility and usability for teams that require specific naming conventions for artifact management.

   Benefits:

   1. Improved Usability: Teams can easily align artifact naming with their versioning and distribution workflows.

   2. Enhanced Clarity: Customizable filenames can help in better identification and management of multiple builds and versions.

   3. Reduced Confusion: Avoid potential issues when integrating with other tools that expect specific naming conventions.

   [1] https://firebase.google.com/docs/app-distribution/ios/distribute-console
   [2] https://firebase.google.com/docs/app-distribution/ios/distribute-cli

   Description:

   We have identified an area for improvement regarding the naming of iOS artifacts in Firebase App Distribution. Currently, when an IPA file is downloaded from the Firebase App Distribution console, it is automatically named app.ipa regardless of its original filename.

   Background:

   Our investigation revealed that, based on Google’s public documentation [1] [2], there is no available method to customize the filename during download.

   Firebase App Distribution automatically assigns the name app.ipa for iOS artifacts as a default behavior, and this is not configurable via the console or CLI.

   Request:

   We propose the introduction of a feature that allows users… more

   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  ·  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. Update button in Firebase Storage

   Please, add an update button to the Firebase Storage Console UI

   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

   Submit Rating

10. SDK for .NET Maui to send Push Notifications

    An SDK to integrate push notifications in .NET Maui Apps

    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  ·  Cloud Messaging  ·  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. .net maui sdk for firebase data connect

    support using Data Connect in c# and .NET Maui by having SDK for C# and generating C# types from the schema

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

    Submit Rating

12. Allows hosting and database regions in Saudi Arabia
    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

    Submit Rating

13. Show direct download link for releases as QR code to scan using phone

    Hello team,

    As AppCenter is deprecated and we're currently moving to Firebase App Distribution as our primary internal app testing platform we'd like to request a new but very valuable feature. This feature should be minor and quick to implement but would make our lives a lot simpler.

    We use Fastlane and the firebaseappdistribution plugin for deploying our builds during CI builds. This plugin generates three links to download a specific release. The first generated link is to view the release in the Firebase Console and it's the one we're currently giving our QA testers and POs so they know what version and version code to download using their phone. It's quite tedious though to look it up in their phones and verify it's the correct release as they do not use their email inbox and email you send out when new releases are deployed. They look at the JIRA for a certain feature/task and navigate to the Firebase Console using the link our CI build comments into the JIRA task.

    We'd appreciate if you could you add an option next to the Download button in the console to view the direct download link for a certain release (the one which doesn't expire after 1h) as a QR code so they can use their phone cameras to scan their laptop screen and open the link easily that way in their browser.

    Best regards
    Elvedin

    Hello team,

    As AppCenter is deprecated and we're currently moving to Firebase App Distribution as our primary internal app testing platform we'd like to request a new but very valuable feature. This feature should be minor and quick to implement but would make our lives a lot simpler.

    We use Fastlane and the firebaseappdistribution plugin for deploying our builds during CI builds. This plugin generates three links to download a specific release. The first generated link is to view the release in the Firebase Console and it's the one we're currently giving our QA testers and POs so… 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  ·  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

14. Sending arrays as parameters, to allow scaling.

    When building simple select queries in GraphQL (really simple ones), the underlying query is being transformed, sending the values through as parameters.

    As you can use arrays as parameters, that would allow the DBs to scale as it makes this more robust. Without scaling, it will limit production applications form fully investing.

    As an example you run into instances where the select for 50 columns in the schema (a standard employment record, nothing special) is transformed and we end up getting the dreaded 100 parameters error. This is a Postgres issue, but can be avoided.

    The Error for the fun of it:
    @firebase/data-connect: DataConnect (11.4.0): Error while performing request: {"error":{"code":400,"message":"cannot prepare SQL statement ... SQL Error: pq: cannot pass more than 100 arguments to a function","status":"FAILED_PRECONDITION"}}

    When building simple select queries in GraphQL (really simple ones), the underlying query is being transformed, sending the values through as parameters.

    As you can use arrays as parameters, that would allow the DBs to scale as it makes this more robust. Without scaling, it will limit production applications form fully investing.

    As an example you run into instances where the select for 50 columns in the schema (a standard employment record, nothing special) is transformed and we end up getting the dreaded 100 parameters error. This is a Postgres issue, but can be avoided.

    The Error for the fun… more

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

    Submit Rating

15. Enable Desktop App Distribution

    Allow desktop app developers to distribute DMG and EXE files via app distribution. This is part of a wider topic of enabling Firebase tooling for desktop environments but seems like a quicker win.

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

    Submit Rating

16. Allow Events with Reserved Names as A/B Test Goals

    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 the error message is unclear and the workaround is not widely known, the ideal solution would be to allow A/B tests to use any event available in Google Analytics, regardless of its name.

    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… more

    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

    Submit Rating

17. messaging reports you can select by year also so if you want to do a summary of 2024 example you can have access

    messaging reports you can select by year also so if you want to do a summary of 2024 example you can have access

    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

    1 comment  ·  Analytics  ·  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

    Submit Rating

18. Support .NET (C#) in Firebase Functions.

    Firebase has .NET SDKs for the client and admin SDKS. It would be nice if Firebase Functions supported .NET (C#) especially since GCP Cloud Run Functions already support .NET.

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

19. C# Blazor SDK

    Firestore has an C# SDK for unity. It would be nice if the C# SDK supported .NET Standard or .NET Core without any interop in C++ so that it could be used within Blazor WASM web applications.

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

20. Anomaly detection / notifications

    If using Firebase with mobile apps, under Analytics - Firebase overview

    We are able to see Anomaly detected points on the charts - but we would like to be able to receive alerts/notifications on this.

    Such a feature would be incredibly beneficial, as we have a number of projects/apps within Firebase.

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