Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Support for CaptureFailedRequests on iOS #2826

Merged

Conversation

carmichaelalonso
Copy link
Contributor

Fixes #2744

Setting either CaptureFailedRequests or FailedRequestStatusCodes previously only affected the .NET layer and was not passed to sentry-cocoa.

In production, this meant that failed requests were being tracked despite the setting being set to false in the .NET layer, which quickly added up in tracked errors on a hosted Sentry plan. This PR ensures we pass this value at init, and properly support failed status code ranges.

Fixes getsentry#2744

Setting either `CaptureFailedRequests` or `FailedRequestStatusCodes` previously only affected the .NET layer and was not passed to sentry-cocoa. In production, this meant that failed requests were being tracked despite the setting being set to false.
@bitsandfoxes
Copy link
Contributor

This looks great, thanks for the fix!

@bitsandfoxes bitsandfoxes merged commit caafeee into getsentry:main Nov 13, 2023
12 of 13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Setting CaptureFailedRequests only affects the .NET layer
2 participants