1556 results found

1. ram

   Could you please add an option to get more RAM for our workspaces? The current amount (seems around 8GB) often isn't enough when running bigger Android projects, especially with the emulator and build tools going at the same time. Things can get pretty slow.

   It would be really helpful if we could choose a higher RAM configuration, maybe 16GB or 32GB, even if it's an upgrade option. This would make developing larger apps in Project IDX much smoother.

   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  ·  Firebase Studio  ·  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. "I need to talk with them using audio or video.", live streem audio and video sharing

   "I need to talk with them using audio or video.", live streem audio and video sharing

   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  ·  Firebase Studio  ·  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 ile yap yazdığım halde kendi varsayılan aracını kullanmaya devam ediyor

   flutter ile yap yazdığım halde kendi varsayılan aracını kullanmaya devam ediyor, promp kısmının altından seçim yaptığımda da boş bir proje oluşturuyor

   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  ·  Firebase Studio  ·  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 Azion Edge SQL Database

   I would like to see full Azion EdgeSQL support. That is a serverless database based on Sqlite and LibSQL. Supports Vector Store for AI and LLMs.

   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  ·  Firebase Studio  ·  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. Private Repo import similar to IDX

   I noticed that currently only public repositories are supported. Are there any plans to support private repositories as well?

   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  ·  Firebase Studio  ·  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. needs a restore button

   Above each prompt, add a restore button to restore code back to point before prompt. Then you can restore, re-write prompt, and see what happens with the next prompt.

   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  ·  Firebase Studio  ·  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. It would be awesome to have a template that provided BOTH a backend and frontend experience. E.g. a next.js + mongodb instance

   It would be awesome to have a template that provided BOTH a backend and frontend experience. E.g. a next.js + mongodb instance

   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  ·  Firebase Studio  ·  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. Supports Custom Streamlit Components Consistently Fail to Load in IDX - Even with ngrok Tunneling

   Bug: Streamlit Components Fail in IDX

   Summary: Custom Streamlit components consistently fail to load in Project IDX, even w/ ngrok. Error: "app.[comp] from [ngrok_url] hasn't received Streamlit.setComponentReady()." Suggests IDX bug.

   To Reproduce: 1. IDX. 2. Basic Streamlit (app.py) + React/Webpack component (frontend/). 3. Simple React comp: Streamlit.setComponentReady() on mount. 4. package.json: webpack serve, Webpack: streamlit external. 5. ngrok.yml: ports 3001, 8501. 6. devserver.sh: ngrok, URLs, start Streamlit. 7. ./build.sh. 8. Start: npm start, ngrok start --all, ./devserver.sh. 9. Access Streamlit.

   Expected: Component loads.

   Actual: Component fails. Error: "app.[comp] from [ngrok_url] hasn't received Streamlit.setComponentReady()."

   Troubleshooting: 1. Minified comp. 2. Verified Streamlit.setComponentReady(). 3. Correct Webpack. 4. ngrok used. 5. Browsers. 6. No index.html. 7. Cleaned env. 8. Dev/prod. 9. Restarts.

   Probable Cause: IDX's handling of component requests, even w/ ngrok. Internal proxy issue.

   Impact: Impossible to dev/test Streamlit components in IDX.

   Request: Investigate.

   Code: Code in the env.

   Info: Exhaustive troubleshooting done. Problem is in IDX.

   Bug: Streamlit Components Fail in IDX

   Summary: Custom Streamlit components consistently fail to load in Project IDX, even w/ ngrok. Error: "app.[comp] from [ngrok_url] hasn't received Streamlit.setComponentReady()." Suggests IDX bug.

   To Reproduce: 1. IDX. 2. Basic Streamlit (app.py) + React/Webpack component (frontend/). 3. Simple React comp: Streamlit.setComponentReady() on mount. 4. package.json: webpack serve, Webpack: streamlit external. 5. ngrok.yml: ports 3001, 8501. 6. devserver.sh: ngrok, URLs, start Streamlit. 7. ./build.sh. 8. Start: npm start, ngrok start --all, ./devserver.sh. 9. Access Streamlit.

   Expected: Component loads.

   Actual: Component fails. Error: "app.[comp]… 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  ·  Firebase Studio  ·  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. Balboa currency

   Project IDX to facilitate Google Pay transactions for country Panama.
   Digital Balboa currency with Google Wallet.

   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  ·  Firebase Studio  ·  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. It all about the game
    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  ·  Firebase Studio  ·  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. Streamline the process of adding .env variables to the build configuration

    I like the idea that you can use Cloud Secret Manager to store and encrypt the secrets within the app.

    Coming from using .env files in Next.js and Vercel hosting could this process be made simpler e.g. reading the .env file from your app directly and intelligently placing the key/value pairs in the apphosting.yaml file or the rollout during creation.

    This would be good to keep things simple and straight forward.

    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

    Submit Rating

12. boynak019@gmail.com

    Nak

    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  ·  Firebase Studio  ·  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. 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

    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

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

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

    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

    Submit Rating

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

17. Apple “Action Required: Apple Push Notification Service Server Certificate Update”

    Good afternoon,

    We received this email from Apple “Action Required: Apple Push Notification Service Server Certificate Update” but since our notification service is managed by the Microsoft Azure platform through the Firebase platform, do we have to update something or is the platform updated automatically?

    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

18. Clickable results in firebase query mode

    When using Firebase UI query mode, the results are not really human readable. I'd like the document ID field to be clickable, taking me to the panel view of that document, so I can see the document in a readable way.

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

    Submit Rating

19. Support a repl/shell in firebase CLI

    Some operations can only be preformed through the firebase-admin SDK, or sometimes you just want to run/test some Firestore query.

    The Firebase CLI can provide a "shell" command that opens a Node.js REPL with the firebase-admin SDK preconfigured and global variables such as "db", "auth" that you can then use to interact with Firebase.

    This was so much needed that I implemented this by myself in our project as a custom package.json scripts.

    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  ·  Firebase CLI  ·  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. Support skipping deploy targets that are configured empty

    Sometimes you have deploy target that you want to not deploy in some projects.

    Currently if a deploy target is not configured or empty, the CLI will error.

    It would be nice if it just skipped deploying that configuration if the deploy target is explicitly configured empty.

    This is also useful to allow varying configuration in different projects, as you can deploy different target configurations depending on the selected project this way.

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