HTTPClientError (Status Code 500) is reported continuously in Unity, cannot be filtered or suppressed (already fixed in React SDK)

[oztrkemree]

We are experiencing a persistent HTTPClientError with status code 500 that is being reported to Sentry from our Unity (iOS) application.
These errors should not be reported, but they continue to appear in Sentry despite multiple attempts to suppress or filter them.

We have noticed that a very similar issue exists in GitHub issues, and it appears that this problem has already been handled/fixed in the React SDK, but the same behavior still exists in Unity SDK.

Observed Behavior:
Error type: HTTPClientError
Status code: 500
Platform: Unity (iOS)
Environment: production
Frequency: High (appears continuously and affects thousands of users)
These errors are not actionable for us and create significant noise in Sentry.

Expected Behavior:
HTTP 500 responses originating from client-side network tasks should not automatically be reported as errors, or
There should be a reliable way to suppress / ignore / filter these errors in the Unity SDK, similar to what is available in React.

Additional Notes:
This behavior is already discussed and resolved for React, but Unity SDK still reports these errors.
This makes Sentry noisy and reduces signal quality for real crashes.

Request:
Is this a known limitation of the Unity SDK?
Is there a recommended or upcoming fix?
Can Unity SDK behavior be aligned with React SDK regarding HTTP client errors?

[linear]

ENG-6337

UNITY-200

UNITY-199

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[bitsandfoxes]

Hey @oztrkemree, sorry to see you run into issues and thank you for reaching out.
I assume you're referencing this issue: getsentry/sentry-react-native#4924

If I read this correctly, then you're getting spammed by HTTPClientErrors originating from the native layer on iOS, meaning the reporting SDK at the bottom of the issue page is sentry.cocoa.unity?
Could you provide me with the link to a sample event so I can dig around before following up with a fix?

If the errors are coming from the C# layer and you're using the Sentry HTTP Client instrumentation the SDK provides a couple of options to allow filtering

// Option 1: Only capture 501-599 (excludes 500)
options.FailedRequestStatusCodes = new List<HttpStatusCodeRange>
{
    (501, 599)
};
// Option 2: Capture 4xx and 502-599 (excludes 500, 501)
options.FailedRequestStatusCodes = new List<HttpStatusCodeRange>
{
    (400, 499),
    (502, 599)
};
// Option 3: Disable entirely
options.CaptureFailedRequests = false;

If it is an exception that is getting thrown instead you can add an exception filter

using Sentry.Extensibility;
using Sentry.Unity;
public class Http500ExceptionFilter : IExceptionFilter
{
    public bool Filter(Exception ex)
    {
        // Return true to filter OUT the exception (not captured)
        return ex is HttpRequestException httpEx 
            && httpEx.Message.Contains("500");
    }
}
// Add the filter to options
options.AddExceptionFilter(new Http500ExceptionFilter());

I see the failed request codes are also get passed down to the native layer on iOS, but only when initializing at build time. The runtime support for that is missing. Let me fix that.