1217 results found
-
Allow listening to firestore document/query changes without getting a snapshot automatially
The default behavior when listening to a document/query is that you will always get an initial invoke of your listener.
Allowing to change this behavior would give more freedom, in the case that the developer wishes to fetch the initial values asynchronously and then have the changes delivered via the callback.3 votes -
Add support using custom SA for 2nd gen cloud functions deployment
Currently using 2nd gen cloud functions requires having the default Compute Engine Service Account and there is no way to use custom service account.
Not all projects have the service account or have any means to re-create the default SA if it has been deleted at some point and using default service accounts is anyway something that is not recommended by Google. So currently not all can move to using 2nd gen cloud functions unless support for using custom SA is added.
7 votes -
42 votes
-
Turning Off Auto Login when creating New User
The Firebase createUserWithEmailAndPassword function currently auto-logs in the newly created user. However, it's crucial to have an option to turn off auto-login, especially in admin panel scenarios. This can help prevent issues where the admin session expires due to the new user login. Providing such an option will enhance flexibility and control in user management.
12 votes -
Firebase CLI (Python version) should provide debugging information
Add better debugging information into Firebase CLI (Python) version. The CLI frequently throws the following error but does not provide any further information, even in debug mode.
Failed to call quitquitquit. This often means the server failed to start request to http://127.0.0.1:8081/__/quitquitquit failed, reason: connect ECONNREFUSED 127.0.0.1:8081 {"message":"request to http://127.0.0.1:8081/__/quitquitquit failed, reason: connect ECONNREFUSED 127.0.0.1:8081","type":"system","errno":"ECONNREFUSED","code":"ECONNREFUSED"}
or
Error: User code failed to load. Cannot determine backend specification
Details of the error can however be found in the GCP Console and Cloud Build. The same error messages should appear in the CLI as the Console is not a scalable way to maintain/deploy…
2 votes -
Django support for firebase app hosting
Django is a very popular framework. It is likely the easiest one to get up and running with, also allowing reusing the code much better than other solutions. No need to say how big Python is and Django (and even Flask) will only become bigger and bigger. Firebase app hosting must support Django. Not tomorrow, now!
2 votes -
gRPC support in firebase Performance Monitoring
firebase Performance Monitoring automatically collects all the https API called invoked from the app. Add the same support for the gRPC API calls as well.
3 votes -
Performance Network Request Integration with DIO Flutter Package
Flutter applications that use https://pub.dev/packages/dio should be able to get automatic network logging to Performance Monitoring.
4 votes -
Firestore insights dashboard
Same dashboard in GCP as Firestore in datastore mode. Collection storage space usage, index size, data size, etc.
Also, for multi tenancy apps in both modes (using subcollections or multiple databases or also schemas in native mode would be nice to have) an API that can tell how much resources - space, reads, writes, etc. did each customer use, to be able to offer some kind of pay-as-you-go type of subscription.
11 votes -
Getting started Tutorials needs critical refinement and acurate articulation of label, navigation steps
https://firebase.google.com/codelabs/firebase-nextjs#4
Labels and directions in the tutorial are not matching the Firebase console. Configuration steps are vague and not descriptive enough. Example " Add your Firebase configuration to your web app code" section Step 2 makes sense if no app was build, but at this point of the tutorial the app has been created "My Nexst.js app", so these instruction are not right. Step 3 i believe is wrong or inaccurately written. Are we to transpose the contents to the npm tab from the "SDK setup and configuration pane" to the proper variable state or if we are to replace…2 votes -
Crashlytics custom alerts
Crashlytics velocity alerting mechanism is very basic and it unfortunately generates a lot of false positive alerts. Support more advanced alarm settings
35 votes -
Site Not Found
i have deployed and when i try to go on default site i see site not found
1 vote -
Per test case history with insights
Hello, for the longest time I would like to have more insights into per-test-case data. I would love to have better viewable history of a test-case to see its performance over time. Currently, I have to dig in through every single matrix and piece together the data on my own. I wish Test Lab provided these insights for me. I want to see the health of my tests over time. What is a failure rate for a particular test? As an example metric. Other metrics, how flaky are my tests? Can I see how healthy one particular test by classname…
1 vote -
Request to Have a Firestore Profiler
Similar to RTDB, it would be good to have a way to monitor Firestore usage as it happens. There are many reads happening that I would like to better understand the source of.
40 votes -
Possibility to filter on the type of device on crashlytics
I would like to filter on the type of device (tablet, phone, tv, watch) to have crash statistics by type of device
2 votes -
Linear integration
When a crashlytics issue occurs, it creates a new issue in linear with a link to the crashlytics dashboard.
When a crashlytics issue is closed, close the associated issue in linear.
When a linear issue is closed, close the associated issue in crashlytics.
When a crashlytics issue receives velocity alerts, it increases issue priority in linear.8 votes -
Support monorepo
Firebase functions does not support monorepo structures (NPM monorepo, NX, Turborepo) during deployment.
Firebase uses custom archive logic for functions packaging (https://github.com/firebase/firebase-tools/blob/127ca3fbf7549d6c0cdf12e89e4465de9dd2b7c9/src/deploy/functions/prepareFunctionsUpload.ts), which does not support internal packages deployment out of the box.
Github discussion: https://github.com/firebase/firebase-tools/issues/653
36 votes -
Support for MySQL
Currently only PostgreSQL is supported, but we are also highly interested in mysql support. Would love to see it on the roadmap.
2 votes -
I want an API that validates custom tokens on the server.
I am testing e2e in nodejs (nestjs). Since only the 'verifyIdToken' method exists in 'firebase-admin', branching is done according to environment variables for testing.
I think that if the 'verifyCustomToken' method exists, we can conduct tests that are more similar to actual operation.1 vote -
Add Android TV support for the AppTester app
The Firebase Apptester APK is incredibly close to having full Android TV support, please add the last remaining steps to make it fully compatible.
User scenario: As a developer, I want my QA-Testers to have access to new TV builds. I can deploy these into apptester, but QA currently has to download the .apk and then manually install them via adb. It would be nice to simply install apptester onto the TV test-device and get the releases there immediately.
What I have tested: it's already possible to install the apptester apk onto a TV, and it runs beautifully: Login works,…
17 votes
- Don't see your idea?