sentry-java

sentry-java copied to clipboard

Self-Hosted Version

22.9.0 self-hosted (https://develop.sentry.dev/self-hosted/)

CPU Architecture

x86_64

Steps to Reproduce

Sending via addAttachment in captureMessage on Android and iOS.

ios:

SentrySDK.capture(message: issueId) { scope in
            scope.addAttachment(attachment)
        }

android:

Sentry.captureMessage(issueId) { scope ->
                    scope.addAttachment(
                        Attachment(attachment)
                    )
                }

Expected Result

Behavior like on ios with the creation of different issues

Actual Result

When sending through addAttachment in captureMessage on iOS, a new issue is created each time with the title specified in the message. On Android, they collapse into the first created issue.

android

ios

Event ID

No response

Assigning to @getsentry/support for routing ⏲️

hi @Damned163 thanks for the feedback! We'll investigate and get back to you!

hi @Damned163 do you use the same message in captureMessage for those that are collapsed?

hi @romtsn no, the message is generated every time a new one(modernized UUID is used)

In Android we catch the stacktrace at the time Sentry.captureMessage is called. That stacktrace is then used by the backend to merge different messages into one issue (as the stacktrace is the same, as captureMessage is called in the same place) @brustolin @philipphofmann Does iOS capture the stacktrace by default when capturing messages? If so, we have to improve our fingerprinting on Android side. Otherwise we have to decide wether to capture stacktraces by default (or improve fingerprinting anyway)

Does iOS capture the stacktrace by default when capturing messages

Yes, but only from the current thread.

Both iOS and Android should group events captured with captureMessage by stacktrace. @Damned163, please share the event grouping information at the bottom of an event with us. You can retrieve it by clicking on show details.

The event grouping information looks like this

Then, we know how your issues get grouped. Please also post the Sentry SDK versions you use for Android and iOS.

oh since this is an older version of self-hosted, probably uses an outdated grouping config?

That could also be @romtsn. Updating self-hosted Sentry to the latest version could solve the problem.

Link to the Sentry version used: https://github.com/getsentry/sentry/releases/tag/22.9.0

@romtsn @philipphofmann updated to the latest version, the problem remained

@Damned163 would you be able to share the grouping information as described above? You can attach it here or send it to [email protected]