Unreal crash reports are received but dropped

[ypoeymiroudnd]

Environment

SaaS (https://sentry.io/)

Version

No response

Steps to Reproduce

1. Setup Unreal Crash Reporter to send events to Sentry.io
2. Provoke a crash
3. Observe on Sentry.io that the event is received but dropped
4. Note that the return code of the HTTP request is 200 (so no error)

Unreal 5.0 preview (CL 18553731)

Expected Result

Unreal crash reports to be processed as issues and not dropped

Actual Result

Issues received but dropped

(note that the 2 issues received were manual tests I did from my computer using sentry-cli.exe, sending basic events)

[ypoeymiroudnd]

I notice more people having similar issue:
https://forum.sentry.io/t/unreal-engine-4-investigating-dropped-errors/16314
https://forum.sentry.io/t/unreal-engine-5/16411/2
#33859 (comment)

However, the fix form their issue seems already release, while I still have it on my side.

[ypoeymiroudnd]

I can provide a CrashReporter's format crash package (minidump, CrashContext.runtime-xml, etc.) if needed

[getsentry-release]

Routing to @getsentry/owners-native for triage. ⏲️

[Swatinem]

@ypoeymiroudnd Hi! Can you rather try to capture the http traffic going out from the crash reporter? I’m currently investigating similar reports, and I’m trying to confirm if the uploader provides a correct zlib stream, which I have seen it sometimes does not.

[Swatinem]

Also, can you give me your SaaS slug/url? We are internally tracking the reason (outcome) for why events are being dropped.

Here is another breadcrumb, that will eventually classify compression-related rejections differently: getsentry/relay#1237

[ypoeymiroudnd]

Hi Swatinem,

Does this Unreal's Curl verbose log is sufficient for you ? (anonymized)
RequestOutput.txt
I can't install easily an HttpInterceptor tool on my machine due to strict corporation's policy, sorry. Though, if you really need more logging, I can push for it, let me know.

For the SaaS slug-url, should we communicate in private message ?

Thank you,

Yvan

[ypoeymiroudnd]

Here is a raw interception of the HTTP request. Hoping it helps.
RequestInterceptionRaw.log

[Swatinem]

@ypoeymiroudnd thank you so much, this was very helpful! I was able to reproduce this and fix the underlying bug! 🎉

[ypoeymiroudnd]

Wow, that's awesome, thank you ! :-)
How can I track when the fix would be available on the SaaS ?
Thank you

[Swatinem]

This will trickle down through a couple of releases, dependency updates, and finally a deploy. These things do take some time and its not quite easy to track them I’m afraid.

[ypoeymiroudnd]

Thank you.
Any way to get more info on that ? Someone I can contact ?
Overall, are we talking hours, days, weeks ? :-)

[Swatinem]

Its rather days, shouldn’t take too long now ;-)

[ypoeymiroudnd]

Thank you !

[Swatinem]

@ypoeymiroudnd this should be deployed now. Can you please double-check and close this issue in that case?

[ypoeymiroudnd]

Hi @Swatinem, thank you I confirm that the fix works! :-)