54 results found
-
Custom quality control for "latest release"
Latest Release is a very useful functionality. For us, even when we have crashes that are worth hot-fixing, it shows as successful. It must go terribly wrong in order to see "Needs investigation" label. This is because these thresholds are hard-coded. It would be great to configure these thresholds
7 votes -
7 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.6 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.
5 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.
5 votes -
Filtering crashes for the latest release shouldn't change time range
When pressing "Filter crashes" on the info banner about the latest release, the time selection also silently changes from "Last 7 days" to "Last 24 hours".
It would be easier to compare between all crashes and crashes from the latest release if the time span didn't change unasked like that.
4 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.
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-export4 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.
4 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.4 votes -
Crashlytics support for react JS based application.
Crashlytics support for react JS based application.
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 -
Allow changing title or at least subtitle of crash group
What happened to us was Crashlytics decided to group only loosely related crashes, same uncaught Objective-C exception in the title field but totally different error message and root cause (displayed as subtitle).
But now we have fixed the original first issue, and the remaining crashes have a different message than the one that still appears in the subtitle field on Crashlytics dashboard, which causes confusion each time a new developer takes a look at the open crashes ("didn't we fix this one already?") before realising it's now a different issue.
It would be great if we could at least choose…
3 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.3 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?
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 -
Add event ids for browser viewing into Crashlytics BigQuery tables
I had trouble with finding a specific crash event in the group of crashes. BigQuery gave me an event_id, but I was not able to use this id in the URL query param to open a specific crash in browser. Browser event ids and bigquery event ids are different. Not sure if I’ll need it in the future again, but it was a bit annoying to get all the threads and stacktraces from bigquery
3 votes -
NDK Thread Names
Crashltyics seems to display thread names for iOS apps, but not for Android. Sorting through Thread #1...50 is not ideal in a complex application. Nearly all our threads are in the NDK, and are just pthreads. The call to obtain the (15+endofstring) thread name is one line of code from the pthread_id.
This was my original query about adding this support, and has the pthread query.
https://groups.google.com/g/firebase-talk/c/cIRb75V5Jxw2 votes -
Sort event parameters by key in Logs and breadcrumbs view
The log event parameters appear in a random order, changing from event to event, crash to crash, making it hard to search and find the parameter of interest. It would be nice if the parameters would be sorted by key, so the one of interest would be easy to find.
(Maybe the order is whatever happened to be serialised in the original crash report. But since it was attached as an unordered
Dictionary<String, Any>via the FirebaseAnalytics API, there's no way to control the order in which they appear in crash logs.)2 votes
- Don't see your idea?