1215 results found

1. Can y'all give me a better Data Science Engineering Base like the original Patton Oracle I use last time

   Original Oracle I used when I had the Motorola g play 4 phone

   2 votes

   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  ·  Extensions  ·  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. Support firebaseui-web

   This highly valuable library is out of date with many issues.

   74 votes

   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

   9 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

   Submit Rating

3. Mag voice over at mag sasalita lang ako at gagawin nya

   Maraming salamat po sa tulung ni AI

   3 votes

   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 ML  ·  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. Allow specifying number of stored releases when creating a preview channel

   Preview channels by default store 10 previous releases per channel. When running firebase hosting:channel:create there is the --expires option to set when the channel expires, but there is no option to tell firebase how many previous releases to store.

   In my case I don't need previous releases at all, and the extra storage is completely unneeded and makes us hit the quota earlier.

   3 votes

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

5. Design an app that uses the phones full potential

   To help the homeless is my reason cause I am currently homeless so the news is great also it has a Robin Hood theme cause we are gonna use the money from the people that are lying and down if to the ones the actually need it .... Using facial recognition and heart beat and want eher else the phone is capable of

   3 votes

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

   Submit Rating

6. I would like this to be a team effort

   My idea is that the collective will come together and use that to our advantage anything to make this become a reality

   2 votes

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

7. Consistent and documented behavior for on*WithAuthContext

   When Functions use e.g. onDocumentCreatedWithAuthContext to handle Firestore event triggers, the meaning of event.authType and event.authId are not documented and are inconsistent between the production and emulator environments.

   The documentation [https://firebase.google.com/docs/functions/firestore-events?gen=2nd#auth-context](here) says "For information about the data available in the authentication context, see..." and links to a page that is not specific to Firebase. That page lists some possible values, but it's not clear what values would be used. The most sensible guess is that authType would be "appuser" or "user" if the document was created from the client-side web SDK, and "serviceaccount" if created from a Cloud Function. But those are not the values used.

   In production, if the document is created from the client-side web SDK, authType is "api_key" and authId is the ID of the logged in user. If it's created from a Cloud Function, authType is "unknown" and authId is the ID of the default service account. Thus it is possible to tell the difference, although since the behavior is undocumented, we can't assume that the behavior won't change.

   In the emulator environment, authType is always "unknown" and authId is always "fake-auth-id@gmail.com". This is inconsistent with the production environment and makes it impossible to tell how the document was created.

   The behavior should be consistent and sensible and well documented.

   When Functions use e.g. onDocumentCreatedWithAuthContext to handle Firestore event triggers, the meaning of event.authType and event.authId are not documented and are inconsistent between the production and emulator environments.

   The documentation [https://firebase.google.com/docs/functions/firestore-events?gen=2nd#auth-context](here) says "For information about the data available in the authentication context, see..." and links to a page that is not specific to Firebase. That page lists some possible values, but it's not clear what values would be used. The most sensible guess is that authType would be "appuser" or "user" if the document was created from the client-side web SDK, and "serviceaccount" if created from a… more

   4 votes

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

8. i cant create the Storage shows An unknown error occurred.

   i cant create the Storage shows An unknown error occurred.

   2 votes

   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

   2 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

   Submit Rating

9. Custom Serverless Resolvers

   Write Node.js resolvers to enhance Data Connect with arbitrary server logic. Resolvers will be authored alongside the Data Connect schema and deployed to serverless infrastructure. Resolvers can either provide new top-level Query and Mutation fields or integrate with SQL table types.

   39 votes

   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  ·  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. Allow For Different Rollout Percentages

    Currently, the highest allowed rollout percentage is 50% (before going to 100%). While we understand that higher percentage won't allow to compare the groups correctly, having an ability to gradually release a feature from 50% to 100% would be a very nice and common requirement.

    6 votes

    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  ·  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. Obfuscate or hide GoogleService-Info.plist

    Secret information in GoogleService-Info.plist is easily accessible by downloading .ipa from App Store via Apple Configurator and unpacking it. That is a big security issue.

    1 vote

    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

12. Localize

    I would like the ability to be able to localize notifications like we can with in-app messages please. Because as it is now, we have to make a separate message for each language which uses up our allotted messages limit quickly.

    1 vote

    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 Messaging  ·  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. please as a developer i need to be able to personally edit my code for my self
    1 vote

    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

14. @Model Operations support in Schema (@auth derivative)

    Right now we have separate Query and Mutation. To streamline, especially when using @auth

    enum ModelOperation {
    create
    update
    delete
    read
    }

    @auth object types that are annotated with @auth are protected by a set of authorization rules that give additional controls than the top level authorization on an API.

    Use the @auth directive on object type definitions and field definitions in the project's schema.

    When using the @auth directive on object type definitions that are also annotated with @model, all resolvers that return objects of that type would be protected. When using the @auth directive on a field definition, a resolver will be added to the field that authorize access based on attributes found in the parent type.

    Right now we have separate Query and Mutation. To streamline, especially when using @auth

    enum ModelOperation {
    create
    update
    delete
    read
    }

    @auth object types that are annotated with @auth are protected by a set of authorization rules that give additional controls than the top level authorization on an API.

    Use the @auth directive on object type definitions and field definitions in the project's schema.

    When using the @auth directive on object type definitions that are also annotated with @model, all resolvers that return objects of that type would be protected. When using the @auth directive on a field definition,… more

    2 votes

    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  ·  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. Fix error messages when deploying Functions

    Several error messages often occur when deploying Firebase Cloud Functions that should not occur. My first time attempting to deploy functions in a new project, I got:

    i extensions: ensuring required API firebaseextensions.googleapis.com is enabled...
    ⚠ extensions: missing required API firebaseextensions.googleapis.com. Enabling now...

    Error: Request to https://serviceusage.googleapis.com/v1/projects/********/services/firebaseextensions.googleapis.com had HTTP Error: 429, Quota exceeded for quota metric 'Default requests' and limit 'Default requests per minute' of service 'serviceusage.googleapis.com' for consumer 'project_number:********'.

    I don't know if that happens every time. It appears to be just a failure to wait long enough after enabling the API.

    The second time, it got further, but errored again:

    ⚠ functions: missing required API eventarc.googleapis.com. Enabling now...
    ✔ functions: required API pubsub.googleapis.com is enabled
    ✔ functions: required API storage.googleapis.com is enabled
    ✔ functions: required API run.googleapis.com is enabled
    ✔ functions: required API eventarc.googleapis.com is enabled
    i functions: generating the service identity for pubsub.googleapis.com...
    i functions: generating the service identity for eventarc.googleapis.com...
    ✔ functions: functions folder uploaded successfully
    i functions: creating Node.js 22 (2nd Gen) function onMessageCreated(us-central1)...
    ⚠ functions: Request to https://cloudfunctions.googleapis.com/v2/projects/********/locations/us-central1/functions?functionId=onMessageCreated had HTTP Error: 400, Validation failed for trigger projects/*****/locations/us-central1/triggers/onmessagecreated-119882: Invalid resource state for "": Permission denied while using the Eventarc Service Agent. If you recently started to use Eventarc, it may take a few minutes before all necessary permissions are propagated to the Service Agent. Otherwise, verify that it has Eventarc Service Agent role.
    ⚠ functions: Since this is your first time using 2nd gen functions, we need a little bit longer to finish setting everything up. Retry the deployment in a few minutes.
    ⚠ functions: failed to create function projects/**/locations/us-central1/functions/onMessageCreated
    Failed to create function projects/*****/locations/us-central1/functions/onMessageCreated

    Functions deploy had errors with the following functions:
    onMessageCreated(us-central1)
    i functions: cleaning up build files...
    ⚠ functions: Unhandled error cleaning up build images. This could result in a small monthly bill if not corrected. You can attempt to delete these images by redeploying or you can delete them manually at https://console.cloud.google.com/gcr/images/********/us/gcf

    Error: There was an error deploying functions

    Again, it appears to be a timeout issue.

    Subsequent deploys have been successful, but I get this warning every time:

    ⚠ functions: Unhandled error cleaning up build images. This could result in a small monthly bill if not corrected. You can attempt to delete these images by redeploying or you can delete them manually at https://console.cloud.google.com/gcr/images/********/us/gcf

    That implies there may be a storage leak happening on every deploy.

    None of these errors should be happening, as far as I can tell.

    Several error messages often occur when deploying Firebase Cloud Functions that should not occur. My first time attempting to deploy functions in a new project, I got:

    i extensions: ensuring required API firebaseextensions.googleapis.com is enabled...
    ⚠ extensions: missing required API firebaseextensions.googleapis.com. Enabling now...

    Error: Request to https://serviceusage.googleapis.com/v1/projects/********/services/firebaseextensions.googleapis.com had HTTP Error: 429, Quota exceeded for quota metric 'Default requests' and limit 'Default requests per minute' of service 'serviceusage.googleapis.com' for consumer 'project_number:********'.

    I don't know if that happens every time. It appears to be just a failure to wait long enough after enabling the API.

    The second time, it got further, but… more

    4 votes

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

16. Transaction should update the local offline cache

    It is a surprise to users (and Gemini) that writing documents using a transaction does not result in the local offline cache being updated when the transaction completes successfully. I'm not sure that it makes sense for the SDK to do this automatically but the firestore docs need to be updated (including the code examples) to make it clear that the local cache does not get updated. There may be some documents in the set being written that are never written by other users, in which case the local user is not expecting to have to have a listener running on those documents. If all the documents being written are in the same collection then having a listener running on that collection is the easy way to get the local cache updated. The docs for batched write could also point out that the local offline cache will be automatically updated. For all of the "set", "update" and batched write commands, the docs should explain whether the local cache gets updated or not even if the command fails. Also the docs should explain that a document read won't actually fetch a new copy of a document if the local offline cache is already up to date, which saves on egress costs but still incurs a document read charge because the document is actually read in the cloud, just not sent back to the client. Also in the docs, explain that for flutter web apps, the offline cache is disabled by default and that browsers (and end users) can delete some or all of the local cache and for IOS and maybe MACOS, if the web app isn't used for seven days, the operating system might delete the local cache.

    It is a surprise to users (and Gemini) that writing documents using a transaction does not result in the local offline cache being updated when the transaction completes successfully. I'm not sure that it makes sense for the SDK to do this automatically but the firestore docs need to be updated (including the code examples) to make it clear that the local cache does not get updated. There may be some documents in the set being written that are never written by other users, in which case the local user is not expecting to have to have a listener running… more

    2 votes

    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  ·  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. Creating a project directly into the Server or Hosting would be great.

    When users who accept security risks give their hosting information directly... artificial intelligence should be able to create files and databases within this host and create a project with the desired features in natural language...

    2 votes

    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  ·  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. Icp Cube

    NLB.com Jrr.com

    2 votes

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

19. PROPULSION VIA Q compute

    continue DoD WORK VIA Q compute©

    3 votes

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

20. datos de contacto para mi aplicacion

    necesito que mi aplicacion recolecte los datos del consultante Nombre, Whatsapp con codigo de pais + email de contacto

    2 votes

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