1238 results found
-
Remove extensions with unsupported Node versions from Extensions Hub
I just spent a week implementing a plugin before realizing it was using Node 12. Deleted all my extensions after that, all using Node 16.
2 votes -
make AppCheck a click process, for cloud functions
Looking at the setup instructions for adding AppCheck, plus replay protection to cloud
functions, it looks to me like you should be able to simply add a wrapper around each
cloud function call, to implement said functionality. Ideally, just as I can enable AppCheck for my firestore database with a few clicks, I want to be able to enable AppCheck, for my cloud functions with a few clicks. Also, concomitantly add replay protection to cloud functions, as there's no significant downside to doing so..2 votes -
Crashlytics SDK provide support for in iOS app extensions. Specifically Location Push Service extension.
Crashlytics SDK provide support for in iOS app extensions. including the extensions that run in background. For example Location Push Service Extension.
2 votes -
Add a copy button to copy web vapid key in cloud messaging
Most keys that can be copied in firebase have a copy icon next to it. This one does not.
2 votes -
use the name of the Firebase project instead of the code in the email sent to the user (Authentication by Email Link )
The email template should use the Firebase project name instead of the technical code.
2 votes -
Set GCP resource location locally or have it be faked when using Firebase without a project.
I'm currently learning Firebase and want to have a sandbox with the emulators without creating a project on the website every time I want to make another. Currently Firebase Storage does not work without setting a GCP resource location and the only way to set it is via the web console. If there was a way to set it locally via the CLI or a config file that would make it a lot easier to experiment with Firebase.
2 votes -
Jira Cloud Integration for Post production issue type:
Currently, Crashlytics only supports Bug issue type with Jira Integration. It would be helpful if it allowed other issue types, such as post-production issues.
This solution allows users to integrate with their organization's Jira issue-type standards, including Pre-production, Post-production, and Defects, instead of relying solely on the issuetype "bug".
2 votes -
2 votes
-
Api to retrieve the list of subCollections present in a collection
We have unstructured data and each document can have different subcollections.
We want to know get the names of all the subcollections present in a collection.Currently we have to iterate over all the documents present in a collection and for each document we are pulling the list of subcollections present in it.
This process is very resource consuming and slow. We have to fire a query for each document present in the collection.Please provide an api something like db.collection("collectioName").listSubCollectionNames();
2 votes -
Crashlytics will report different stacks as different crash
Currently exception events are gathered as one issue depending solely on the actual exception location and its type.
Moreover, every such event pops all previous ones as regressed.
This makes it hard to follow the different issues. It is specifically a big problem where a fallback is used, with non-fatal crash reports in it. All crashes that ended up with the fallback are reported as one.
My suggestion is that different call stack and/or message will be shown as different issues. (Possibly with an option to set the differing place in the stack)2 votes -
Split Android & Wear OS app
Since Android & Wear OS must use the same package name to be able to communicate, we have no way to split apart Android & Wear OS crash reports.
This is an issue because we use Flutter for the mobile app and Kotlin/Jetpack Compose for the Wear OS app. The two apps share essentially nothing in common except for the package name and we have two separate teams working on them.Filtering for device type sounds like it should work, but the we only have phone & tablet in that list even though there's at least one crash guaranteed to…
2 votes -
User Ratings metric for A/B testing in Android apps
This would allow developers to find out if a certain feature is causing a terrible user experience for a small group of users, despite not showing up in top level metrics.
2 votes -
next.js dockerfile
I am deploying using the Firebase CLI with Next.js. I find it incredibly effective and I am very grateful for it, however, I've encountered a bit of a problem.
When running code with SSR that requires a certain package, an error occurs and I'm unable to proceed.
Is it possible to use a Dockerfile or a Docker container image that I've prepared myself?
Thank you very much for your assistance.
2 votes -
Text recognition for web apps.
I'm using firebase with a Vue.js app, so I'd love to see documentation on how to use the text recognition ML feature with a web app.
2 votes -
Authentication feature in Android Wear / WearOS application
The ability to handle autentication and registration feature in android wear / wearos applications, using FirebaseUI or the official firebase auth library in gradle.
Ideally, the same features promoted to android apps but in the wearable world, taking in account the considerations related to battery, performance and data fetching and processing applied to wearables.
2 votes -
Authentication feature in Android Wear / WearOS application
The ability to handle autentication and registration feature in android wear / wearos applications, using FirebaseUI or the official firebase auth library in gradle.
Ideally, the same features promoted to android apps but in the wearable world, taking in account the considerations related to battery, performance and data fetching and processing applied to wearables.
2 votes -
Quick navigation
A quick navigation/search bar with a keyboard shortcut like cmd+k or / like gcp console will be really handy for fast navigation across all the products
2 votes -
Whitelisted email address for testing with passwordless email link
It would be great to have a whitelisted email address to use for testing, like we have for SMS authentication, to avoid this message:
"[firebase_auth/too-many-requests] We have blocked all requests from this device due to unusual activity. Try again later."2 votes -
Apply filters from crash issues list (eg. state = open) to the graphs above.
This can be either done by directly adding the filter option to the graphs above, or by a toggle which applies filters from the list to the graphs. (not by default, to prevent confusion/regression from current behaviour)
2 votes -
Support for getting values stored in user properties
The functionality to get values currently stored in user properties at runtime would be extremely useful.
Something like "mFirebaseAnalytics.getUserProperty("favorite_food");"This would allow checking values and correcting them when necessary, as well as recovering information that may have been lost between one session and another of the application.
2 votes
- Don't see your idea?