Skip to content

Ensures are incorrectly reported to sentry as "Fatal" errors #189

@skauker-iw

Description

@skauker-iw

Environment

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

Which version of the SDK?
0.1.1

How did you install the package? (Git-URL, Assetstore)
Git-URL

Which version of Unreal?
Unreal 4.26.1

Is this happening in Unreal (editor) or on a player like Android, iOS, Windows?
All cases I have tested -- Win64 Editor and packaged Win64 Development configurations (Shipping untested)

Steps to Reproduce

  1. Make sure your project is set up with the crash reporter to report to sentry via the unreal specific endpoint.
  2. Open the project (works both in editor or in a packaged game) without a debugger attached
  3. Open the debug console, debug ensure, which triggers a non-fatal ensure failure. This should trigger the crash reporter to send it to sentry automatically to the configured crash endpoint.

Expected Result

I would expect a failing ensure to be at most a yellow "warning" or "error" when shown in the UI.

Actual Result

In the Sentry web UI, ensures are incorrectly marked as "Fatal"
image

I absolutely could be missing something here, or if there was a way to modify the CrashReportClient to allow changing the error level. I'd love to be able to be able to sort out actual crashes vs. failing ensures that correspond to less-critical logic errors.

Metadata

Metadata

Assignees

Labels

BugSomething isn't working

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions