51 results found
-
Crashlytics alerts do not work if Firebase permissions have been granted from Google Cloud IAM roles
Make Crashlytics alerts work with permissions granted from Google Cloud IAM roles rather than from the Firebase console's own permissions
5 votes -
Broaden Crashlytics velocity error range to allow larger percentages than 1%
We would like to broaden the Crashlytics velocity error percentage so that we can trigger velocity alerts at larger percentages than 1%. 3% would be ideal for our purposes.
4 votes -
Export CFU(Crash Free Users) Stats to BigQuery
The CFU is only available in Crashlytics dashboard.
With the current info exported to BigQuery it's not possible to calculate it.
4 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.4 votes -
Compare crash rates across multiple versions
In the Crashlytics console you can filter crashes based on version, however it would be nice when you select multiple versions to have a comparison graph rather than a combined graph (something like Analytics does with time periods) so that I can confirm that crashes are resolved in newer versions.
4 votes -
Jira Server integration
Currently, Crashlytics does not support integration with Jira Server (on premise) v9.0+. I suggest that also this variant of Jira is supported since everybody isn't running Jira Cloud.
4 votes -
notes
Add Crashlytics Issue Notes to the Crashlytics Schema [1] for BigQuery Export [2]
[1] https://firebase.google.com/docs/crashlytics/bigquery-export#schema-columns
[2] https://firebase.google.com/docs/crashlytics/bigquery-export3 votes -
Crashlytics Velocity alerts should contain impacted user count
We would like to have Crashlytics Velocity alerts contain the impacted user count so we can determine how problematic a velocity alert actually is.
3 votes -
Pull Firebase Crashlytics Custom Key values into the slack integration
It would be very helpful if custom key information could be pulled out of Crashlytics into e.g., the Slack integration.
3 votes -
Crashlytics Section should have User perceived ANR Filter
There are lot of ANR like https://github.com/firebase/firebase-android-sdk/issues/6147#issuecomment-2417385067
Which has no solution even Firebase team concluded that.
So, there should be a filter to segregate user perceived ANRs on crashlytics.3 votes -
HTTPS Proxy with Authentication
Firebase currently does not have a clear way of supporting HTTPS proxy. If the network is limited by OEM's restrictions, or firewalls then Firebase Crashlytics won't operate. Probably no Firebase service will be able to work.
We can set the domain and the port for HTTP proxy, but then it is not authenticated.
3 votes -
Stability score
Currently firebase crashlytics shows crash free users and crash free sessions, although ANRs are also equally important. ANRs create a bad user experience which is comparable to a crash.
By showing a stability score which considers ANRs as well as crashes, we can show a true representation of app health. This can be at the session level.
2 votes -
linux
What feature would you like to see?
I would like to see FlutterFire plugins add support for the Linux platform. This enhancement would allow developers to build applications that leverage Firebase services on Linux, enabling cross-platform compatibility and expanding Flutter's reach.Why would it be useful?
Adding Linux support would:Enable developers to target a wider range of platforms with their Flutter apps.
Provide parity with other supported platforms (e.g., iOS, Android, Web).
Leverage Firebase's capabilities (e.g., authentication, cloud storage, and Firestore) in desktop environments where Linux is widely used.2 votes -
Crashlytics support for react JS based application.
Crashlytics support for react JS based application.
2 votes -
Dart SDK for Crashlytics
I use Dart on the server, via Serverpod. I would love to be able to record server exceptions to Crashlytics, but right now the Dart support for Crashlytics only works in Flutter, because it relies on the Android and iOS native API support. Dart servers don't/can't run Flutter. There is no REST API for Crashlytics, so the Flutterfire developers can't support pure Dart (I asked them). Can you please add a pure Dart API for Crashlytics, and/or provide a REST endpoint?
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 -
Filter by package name
Should be interesting to filter bugs by package name
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 -
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
- Don't see your idea?