732 results found

1. Web SDK generation to also export schema types

   Currently the dataconnect:sdk:generate command in firebase-tools will generate functions for queries and mutations. There are cases where having TypeScript interface reflections of the schema types would also be beneficial.

   AFAIK there's no existing tooling that will conveniently do this mapping (due missing types that one can find in .dataconnect/schema/prelude.gql when the emulator is running).

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

2. Make AngularFire an offcially supported library

   The AngularFire library gets updated really slow so we miss out on some of the latest features. There are lots of issues that doesn't get solved and the documentation is very lacking. They are both Google products and make an awesome combination but if the library does not get enough support/resources we're forced to migrate to plain javascript firebase. Please make it an official library or something so more resources are assigned to AngularFire.

   35 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

   11 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

3. Real Android TV devices in Firebase Testlab

   At the moment we only have emulators for Android TV. Would be nice to have the option to have Android TV real devices as well.

   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

   2 comments  ·  Test Lab  ·  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

4. SSO accross subdomains
   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  ·  Authentication  ·  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

5. API Revoke Token

   Simple API to revoke the token/refresh token from a backend without using the SDK.

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

6. Fix GitHub integration

   Issues:

   1. In the app hosting wizard: Connecting a GitHub account that is not the owner of the GitHub repository and then removing it breaks the GitHub integration process and the App Hosting set up process.
   2. Being just a collaborator to a GitHub repo doesn't make it visible in the App Hosting Set Up wizard, you have to connect with the GitHub account of the owner of the repo.

   Error messages:

   1. Connection verification failed: unable to verify the authorization token: GET https://api.github.com/user: 401 Bad credentials []: failed precondition.
   2. Error: Request to https://developerconnect.googleapis.com/v1/projects/PROJECT-ID/locations/europe-west4/connections/firebase-app-hosting-github-oauth:fetchGitHubInstallations had HTTP Error: 400, Failed to list GitHub installations

   I described the issue in detail in this r/Firebase reddit post:
   .

   https://www.reddit.com/r/Firebase/comments/1i1k4ln/firebase_app_hosting_and_github_issue/

   .

   Improvement suggestions:

   1. Don't make the GitHub integration step mandatory as I only wanted to manually deploy at that stage.

   2. Let the user know he needs to be the owner and can't change the "bot-account" later.

   3. Add the ability to remove the account and change to another.

   4. Make it work not only with repos where you are the owner but also to repos where you are collaborator

   5. Add the ability to "Factory reset" a firebase project.

   6. Add the ability to reuse a project ID if it's been deleted already.

   Issues:

   1. In the app hosting wizard: Connecting a GitHub account that is not the owner of the GitHub repository and then removing it breaks the GitHub integration process and the App Hosting set up process.
   2. Being just a collaborator to a GitHub repo doesn't make it visible in the App Hosting Set Up wizard, you have to connect with the GitHub account of the owner of the repo.

   Error messages:

   1. Connection verification failed: unable to verify the authorization token: GET https://api.github.com/user: 401 Bad credentials []: failed precondition.
   2. Error: Request to https://developerconnect.googleapis.com/v1/projects/PROJECT-ID/locations/europe-west4/connections/firebase-app-hosting-github-oauth:fetchGitHubInstallations had HTTP Error: 400, Failed to list GitHub installations

   … 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

   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

7. Hard Spending Limit on Firebase Resources

   A Hard Spending Limit option in Firebase Billing settings would allow developers to set an absolute cap on resource spending for their Firebase projects. Once this limit is reached, Firebase would automatically pause or throttle resources to prevent any charges beyond the specified amount. This feature would enhance budget control and predictability for developers and organizations of all sizes.

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

8. Accept Firebase Terms of Service via Terraform

   There is no possibility to accept Firebase Terms of Service automatically (or at least manually in advance, without the need to go through manual Firebase project creation process) when using Firebase via Terraform.
   When trying to create a Firebase project using Terraform (add googlefirebaseproject resource), apparently unaccepted ToS cause 403 "Error creating Project".
   After at least one Firebase project is created manually via Firebase Console, creation project via Terraform works.
   It would be great to separate accepting ToS from project creation or at least improve error message in this case.
   Here are some examples:
   https://stackoverflow.com/a/79345435/14866192

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

9. Add ability to choose Test Lab's device location

   Some applications are very dependent (in performance perspective) on resources from CDNs & backend location - it would be great if we can choose location of the Test Lab's device location (preferably Android real devices) to set it closer to CDN & backend.

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

10. Log thirdPartyPrincipal in storage audit logs, similar to firestore

    It seems GCP audit logs can capture all the operations on the firebase storage bucket, but the actor that shows up in the logs is a service account, rather than the end user. Is there a way to capture the end user who is requesting storage objects?

    When I look at audit logs for firestore, I see a thirdPartyPrincipal that includes the end user, but this doesn't show up in the storage audit logs.

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

11. support SvelteKit in app hosting

    support SvelteKit apps in the new App Hosting

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

12. Support storing unstructured json in Postgres jsonb column

    Postgres support jsonb column that can store arbitrary jsonb objects, very suitable to store unstructured / semi-structured API output.

    Postgres also supports index on fields within jsonb.

    Can data connect support jsonb column? Mapping fields of API object to Postgres columns can be a headache

    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

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

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

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

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

    142 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

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

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

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

    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

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

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