如何在Crashlytics（Fabrics）中有效地将非致命异常分组？ [英] How to effectively group non fatal exceptions in Crashlytics (Fabrics)?

问题描述

我们正在应用中使用Crashlytics作为崩溃报告工具。
对于Android本机崩溃，它可以正常工作并正确地对崩溃进行分组。
我们的应用程序在本地本机中也很少。对于这些组件中发生的崩溃，我们将其捕获，然后将它们作为非致命异常记录到Crashlytics中。

We are using Crashlytics in our app as the crash reporting tool. For Android native crashes, it's working fine and grouping the crashes correctly. Our app also has few components in react-native. For the crashes which occur in these components, we catch them and then log them to Crashlytics as non-fatal exceptions.

public class PlatformNativeModuleCallExceptionhandler implements 
NativeModuleCallExceptionHandler {
@Override
public void handleException(Exception e) {
    try {
        .
        .
        .
        Crashlytics.logException(new Exception(exceptionString));
    } catch (Exception ex) {}
}

崩溃已记录在Crashlytics信息中心中，但它在单个标签中显示了所有崩溃。这些可能是相同或不同的本机组件的不同崩溃。

Crashes are getting logged in Crashlytics dashboard, but it's showing all the crashes inside a single tab. These might be different crashes of the same or different react-native components.

由于这个原因，我们无法找出特定崩溃的实例。需要手动处理每个崩溃实例。

Due to this we are not able to find out the instances of a particular crash. Need to manually go through each instance of the crash.

我想它取了创建异常的类的名称，在这种情况下为 PlatformNativeModuleCallExceptionHandler 。
我尝试创建自己的自定义异常类，但这也无济于事。

I guess it takes the name of the class where exception gets created, in this case PlatformNativeModuleCallExceptionHandler. I tried creating my own custom exception class but that also did not help.

有人知道我们如何在这里更好地对非致命异常进行分组吗？
所有类似的崩溃应与它们的总实例一起分组。

Does anybody know how we can group the non fatal exceptions better here? All the similar crashes should be grouped together with their total instances.

推荐答案

Crashlytics使用方法和崩溃行号将崩溃分组，因此，如果您对所有非致命事故都拥有异常处理程序方法，则会将它们组合在一起。当前没有解决方法。

Crashlytics uses the method and crash line number to group crashes, so if you have an exception handler method for all of your non-fatals, they'll be grouped together. There isn't currently a workaround for this.

这篇关于如何在Crashlytics（Fabrics）中有效地将非致命异常分组？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！