32 results found
-
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 -
Filter by package name
Should be interesting to filter bugs by package name
2 votes -
Export event state to BigQuery
Currently the events exported from Firebase to BigQuery don't have the issue state, which requires additional work to check the issue state without the information on when the state was updated.
The proposal is that real-time exporting can consider the issue state at the time of receiving the event.
E.g.
- Issue ID 1 currently has an open state
- Issue ID 1 receives event ID A at 10:30am
- Issue ID 1 is set to a closed state at 10:31am
- Issue ID 1 receives event ID B at 10:32am
- BigQuery has event ID A set as open…6 votes -
Integration with Google Chat
Would be great to have the option to integrate crashlytics alerts with google chat
5 votes -
Allow custom Slack webhook URLs when integrating with Crashlytics
Problem
When filling out the form to add a Slack webhook URL for a Crashlytics project the form only allows URLs that begin with https://hooks.slack.com/..., however, some companies have their own proxy URLs to manage the Slack webhooks for their enterprise Slack instance (e.g. https://hooks.mycompanydomain.com/...).
Feature request
Please relax the client-side only form validation to allow other hostnames besides "hooks.slack.com".
7 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 -
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.1 vote -
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 -
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 -
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 -
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.
5 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 -
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
17 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…
1 vote -
Crashalytics to support SDK
I need crashlytics to track crashes of my SDK not the crashes of the app which is implementing my SDK
1 vote -
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)
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
4 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
2 votes
- Don't see your idea?