Error name as class name instead of exception name

SDKs
5

thanks for your reply @committedteadrinker

Actually, this was like that and it has been changed to keep compatibility with the older version of the Android SDK aka v1

See: https://github.com/getsentry/sentry-android/issues/363

Both ways would have a valid use case, it really depends on the nature of the Exception and how you’ve raised them.

A workaround would be to reverse the order of the exception list, because the title, subtitle and culprit are inferred from that list, based on the sorting.

See: https://develop.sentry.dev/sdk/event-payloads/exception/

Try to set a BeforeSend and reverse it, and check if this actually solves your problem.

SentryAndroid.init(
        this,
        options -> {
            options.setBeforeSend((event, hint) -> {
                if (event.getExceptions() != null) {
                    Collections.reverse(event.getExceptions());
                }
                return event;
            });
        });

If you believe that we should change this in the SDK instead, please open an issue on https://github.com/getsentry/sentry-android/issues and we can discuss this further along with more interested people.

1 Like