24 results found
-
36 votes
-
25 votes
-
22 votes
-
14 votes
-
12 votes
-
12 votes
-
10 votes
-
11 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
9 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.
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)1 vote -
24 hour format for Crashlytics graphics
The "last 24 hours" and "last 60 minutes" graphics in Crashlytics show the time axis in AM/PM format. I'd like to be able to change it to 24 hour format.
2 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.
2 votes -
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 -
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.
1 vote -
6 votes
-
Why can't we see the historical crash statistics
Recently I find that we can only check the recent four days' crash data even I select 'past 30 days', is there anything wrong? or why we are not allowed to check historical crash data?
1 vote -
One view for all apps in Crashlytics
In a large project with 10+ apps, you have to select projects one by one to see crashes and all other details. Just like Google Analytics and some others (in the same tool), treat app ids as filters and provide ability to see everything at once.
5 votes -
Allow Trending Stability Notifications via the Slack integration
I would like the option to be able to receive trending stability notifications via the slack integration
1 vote -
API Access to Crash and Performance Data.
Provide Crash Free Metric, Performance metrics, Alerts and Insights via API to integrate with existing systems
3 votes
- Don't see your idea?