1222 results found
-
Expose createTime & updateTime in scheduled Firebase LevelDB exports
I am using this procedure for regular backups: https://firebase.google.com/docs/firestore/solutions/schedule-export
and some tooling to locally analyze data in the resulting (downloaded) LevelDB backups.The Admin SDK exposes (internally, but still) createTime, readTime and updateTime properties on snapshots. I don’t see these properties included in the database exports; which makes them less complete as backups, and less useful for data analysis.
2 votes -
should include updating the In-App messaging data dynamically based on the triggered event bundle received from the app
The current functionality of the In-App messaging feature is basically a one-way communication from Firebase to app for the means of providing data with just the triggering point from the app side. It would be great if the event triggered carries a bundle data to update the In-App message data before showing it in the app. This will be a game changer in my opinion.
2 votes -
Add support to programmatically configure social providers for tenants
Add the ability to configure social authentication methods like Google, Facebook, etc. like how OIDC and SAML can be done.
Also, the ability to use the parent configuration for Google Authentication so it is just an enable like in the Web Console UI. This reduces the overhead code that we need to provide if all we are doing is splitting into different tenants for management reasons.
2 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 -
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 -
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 -
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 -
Support Firestore emulator in Datastore mode
It is now possible to run the Firestore emulator in Datastore mode, however, it must be run through the gcloud cli.
It would be great if the firebase cli supported using datastore mode in the firebase.json configuration and if the firestore emulator UI supported datastore mode
2 votes -
Increase request size over 32Mb
Right now, a Firebase function can only accept a request payload size up to 32Mb.
Using it as webhook for some external APIs, we would need to have no limits or at least 100Mb limit2 votes -
Firebase Realtime Chat SDk
Integrate a real-time chat SDK into Firebase to streamline the development process of creating chat applications from scratch.
2 votes -
Need a .net MAUI support on Apple sign-in for authentication
Need a .net MAUI support on Apple sign-in for authentication
2 votes -
Allow reverse chrono time sort of files in cloud storage in the Firebase UI
I need to go to the underlying cloud storage UI to do this currently which is a pain and I need to leave the Firebase environment.
2 votes -
Remove "Recent Projects" list from Firebase homepage
Removes "Recent Projects" list from Firebase homepage, or hide it when there are a total of 8 projects or less. I have to switch across projects frequently, and the recent projects list is not useful as we only have 8 projects. 5 projects are duplicated on the page and this confuses my eyes a lot. Perhaps alternatively have a table of projects?
2 votes -
Go: Implement ProjectManagement API
Go developers should be able to interact with Project Management API using the SDK like Node.js/Python devs can do
2 votes -
azure
For Firebase / Flutter administrators who would like to use Entra AD (Azure AD) for Flutter Android,iOS and Web apps, the administrative setup and documentation should be easy to follow. The administrative process should be consistent with the Google authentication scenario.
2 votes -
Raise the Firestore Rules Expression Limit
Raise the maximum expression limit for firestore rules to make more complex doc schema validation possible.
2 votes -
Filter by package name
Should be interesting to filter bugs by package name
2 votes -
custom gpt to firestore
I wanted to create my own GPT using OpenAI's new GPT builder which has "Functions" in it, and I wanted it to be able to use Firestore API to perform CRUD operations, but unfortunately I struggled to find documentation on how to do that.
2 votes -
Support named database data retention with import and export-on-exit flags
Now that we can create named databases and see those databases in the firestore emulator, it would be nice if the import and export-on-exit flags also respected these named databases and imported the data previously exported into the correct database.
2 votes
- Don't see your idea?