46 results found
-
Filter by package name
Should be interesting to filter bugs by package name
2 votes -
28 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
1 vote -
23 votes
-
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.
6 votes -
20 votes
-
It is recommended that firebase add native crash and java crash filtering
Translation: It is recommended that firebase add native crash and java crash filtering to facilitate checking the crash-free rate of native and java crash, and also to facilitate timely discovery of some problems.
Original: 建议 firebase 加上 native crash 与 java crash 的过滤，便于查看 native 与 java crash 的 crash-free 率，也便于及时发现一些问题
1 vote -
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 -
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.3 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 -
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 -
16 votes
-
15 votes
-
API Access to Crash and Performance Data.
Provide Crash Free Metric, Performance metrics, Alerts and Insights via API to integrate with existing systems
9 votes -
13 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 -
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 -
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.
8 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".
1 vote -
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
- Don't see your idea?