Investigate Discrepancy in Stack Traces for Duplicate Sentry Events

[Kobby-Bawuah]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/remix

SDK Version

7.76.0

Framework Version

No response

Link to Sentry event

No response

SDK Setup

No response

Steps to Reproduce

A user shared that Sentry reported an issue (see Sentry Issue #4509508468) with no stack trace.
I am not able to reproduce but the user noted that the stack trace is visible when reproducing the error locally but is missing in the Sentry event.

The user provided a URL for reproduction: https://syncwith.com/airtable/app/appUeLa7Vc2PT7Xj/new/ls~facebook-ads2
He said two Sentry events were generated for the same issue:
[Sentry Issue #4567281403](https://syncwith.sentry.io/issues/4567281403/?project=5880196&query=is%3Aunresolved&referrer=issue-stream&statsPeriod=14d&stream index=0)
[Sentry Issue #4509508468](https://syncwith.sentry.io/issues/4509508468/?project=5880196&query=is%3Aunresolved&referrer=issue-stream&statsPeriod=14d&stream index=1)

I don't see errors within the network tool.

Zendesk ticket: https://sentry.zendesk.com/agent/tickets/106056

Expected Result

The Sentry event generated for the reproduced issue (https://syncwith.sentry.io/issues/4567281403) should display the same stack trace as observed locally.

Actual Result

The local reproduction of the issue shows a stack trace in the Remix web app, indicating that the error has a stack trace.
However, the Sentry event (https://syncwith.sentry.io/issues/4509508468) for the same issue does not display a stack trace, creating a discrepancy between the local and Sentry environments.

Additionally:
Two Sentry events were generated for the same issue (https://syncwith.sentry.io/issues/4567281403 and https://syncwith.sentry.io/issues/4509508468), raising questions about why there are multiple events for a single error.

[alexblack]

Thanks @Kobby-Bawuah please let me know if more information is needed

I'd actually express the problem this way: when reproducing this issue (by browsing to the mentioned url), I expected just 1 event to show up in Sentry, instead we get two events.

Recent we upgraded from Remix 1.19.3 to 2.1, which required us to make changes to our sentry-remix integration as per your documentation. This problem appears to have started after that.

In the past, before the upgrade, we would only get one event in sentry per issue (which is correct/expected).

[Lms24]

Hi @alexblack 👋 and thanks @Kobby-Bawuah for writing this up!

I tried reproducing this but I don't even get one error event being sent when looking at my network tab in dev tools. Is there anything I need to do on the page to reproduce this or should it appear just when opening it?

Thanks for providing the additional information of the Remix v1 -> v2 upgrade. Once we can reproduce this, we can check if my suspicion is true: I somewhat guess that we catch the error once (with a stack trace) and don't mark it as already caught or it is somehow rethrown as a new error which the SDK believes to have never been seen before.

To debug this further, we'd greatly appreciate a minimally reproducible example that we can debug locally. Any chance you can help us with this, Alex? Thank you!

[alexblack]

Hi as I'd explained to Kobby the error is server side, so there is no way you'd see it in the network tab.