761 results found

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

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

3. Flutter support for App Hosting

   Allow Firebase App Hosting to build and deploy Flutter apps.

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

   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.

   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

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

7. Dart support for the Firebase's Admin SDK

   Firebase has a server (backend) library called the Admin SDK, which has privileged (admin) access to some Firebase services. There are several language implementations of the Admin SDK: JavaScript/TypeScript (Node.js), Java, Python, Go, and C# (.NET). However, Firebase does not currently support the Dart language.

   This is a problem for full-stack Flutter developers, who need to use both the front-end and back-end of a Firebase application. Currently, they need to use different languages for each, such as Dart for the front-end and JavaScript/TypeScript for the back-end. This can lead to decreased productivity and a worse developer experience.

   For example, developers may need to switch between languages frequently, which can be time-consuming and error-prone. They may also not be able to use powerful features like Hot Reload, which can slow down development.

   Firebase should add support for the Dart language to the Admin SDK. This would make it easier for full-stack Flutter developers to build and maintain Firebase applications.

   Firebase has a server (backend) library called the Admin SDK, which has privileged (admin) access to some Firebase services. There are several language implementations of the Admin SDK: JavaScript/TypeScript (Node.js), Java, Python, Go, and C# (.NET). However, Firebase does not currently support the Dart language.

   This is a problem for full-stack Flutter developers, who need to use both the front-end and back-end of a Firebase application. Currently, they need to use different languages for each, such as Dart for the front-end and JavaScript/TypeScript for the back-end. This can lead to decreased productivity and a worse developer experience.

   For example, developers… more

   143 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  ·  SDKs  ·  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. Increase the size of remote config from 1MB to 10MB

   Why not increase the file size for remote config? Right now it only holds 1MB of text, but if you zip a 1MB plain text file you can reduce it to 100kb or less. So, why not increase the configuration size to 10MB?

   1MB remoteconfig.json ==> compress file ==> 80kb remoteconfig.zip

   12 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

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

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

12. Broaden Crashlytics velocity error range to allow larger percentages than 1%

    We would like to broaden the Crashlytics velocity error percentage so that we can trigger velocity alerts at larger percentages than 1%. 3% would be ideal for our purposes.

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

    Submit Rating

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

14. Vertex AI only for authenticated users

    Currently, App Check is the only mechanism to control access to the Vertex API. This is not always practical and does not allow per-user access control.
    Please add a mechanism similar to Security Rules for Firestore, to enforce only authenticated Firebase users to access the AI APIs.

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

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. WearOS support for App Distribution

    WearOS App Distribution feature is recommended, so Firebase can be used for deploying WearOS apps and updates for test users, and even for production/enterprise apps

    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

    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

18. custom remote git support

    Support for self hosted gitlab or other git remote sources

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

    Submit Rating

19. Firestore indexes in emulator

    Currently, the Firestore emulator allows all queries without checking if the query requires an index. It would be great if the emulator checks the Firestore indexes file if the index exists.

    123 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

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

    Submit Rating

20. Daily usage limitation chart

    We were keep getting the Firestore Quota message tough the usage was just 2% in our billing.
    After reaching out to the Firebase team, we found out that there are also daily limitations for each action (Read, Write,..) that was hidden in google cloud console.

    The suggestion is to make the daily limitation chart visible in Firebase, as this error is effecting the users directly.

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