EnableAutoCrashCapturing to false is ignored for some type of crashes

[user37337]

Environment

How do you use Sentry?
Sentry SaaS (sentry.io)

Which version of the SDK?
sentry-unreal-0.18.0-engine5.4-github.zip

How did you install the package? (Git-URL, Assetstore)
Update files in Plugin folder manually

Which version of Unreal?
UE 5.3.2 and UE 5.4.2 (self compiled)

Is this happening in Unreal (editor) or on a player like Android, iOS, Windows?
Editor and Win64 packaged build

Steps to Reproduce

1. Start Editor with EnableAutoCrashCapturing=False
2. Get crash (e.g.: UE_LOG(LogTemp,Fatal,TEXT("Testcrash"));

Expected Result

Unreal Crash Reporter should open

Actual Result

Crash was sent by sentry crashpad

For other types of crashes (e.g. nullptr exception) Unreal Crash Reporter is used correctly
Also it worked correctly in version 0.17.1

Any logs or screenshots

Script Stack (2 frames) :
/Game/Editor/DebugTools/BP_Crash.BP_Crash_C.ExecuteUbergraph_BP_Crash
/Game/Editor/DebugTools/BP_Crash.BP_Crash_C.Run

[2024.07.03-08.48.33:407][925]LogSentrySdk: Verbose: merging scope into event
[2024.07.03-08.48.33:472][925]LogSentrySdk: Verbose: invoking `before_send` hook
[2024.07.03-08.48.33:475][925]LogSentrySdk: Verbose: adding attachments to envelope
[2024.07.03-08.48.33:475][925]LogSentrySdk: Verbose: sending envelope
[2024.07.03-08.48.33:475][925]LogSentrySdk: Verbose: submitting task to background worker thread
[2024.07.03-08.48.33:475][925]LogSentrySdk: Verbose: executing task on worker thread
[2024.07.03-08.48.33:476][925]LogSentrySdk: Verbose: sending request using winhttp to "https://xxxx.ingest.us.sentry.io:443/api/xxxx/envelope/":
x-sentry-auth:Sentry sentry_key=xxxx, sentry_version=7, sentry_client=sentry.native.unreal/0.7.6
content-type:application/x-sentry-envelope
content-length:411895

[tustanivsky]

@user37337 Thanks for raising this - we'll try to reproduce it on our end and let you know. Also, recently we've made somewhat related changes in #586 yet I'm not sure if this fix covers the above issue

[user37337]

@tustanivsky Thank you. It seems this PR fixed the issue.

[tustanivsky]

Great, the fix should be available with the next plugin release. I'm closing this for now, but please feel free to re-open if issues with Crash Reporter persist.