From 39e7fcd40ed0230d3be4460d3e5851b79d5d9681 Mon Sep 17 00:00:00 2001 From: Philipp Hofmann Date: Tue, 4 Mar 2025 14:59:05 +0100 Subject: [PATCH] feat(apple): How to investigate HTTP client errors (#12879) Explain that the stacktrace of HTTP client errors can be bogus and what to check instead. --- .../apple/common/configuration/http-client-errors.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/platforms/apple/common/configuration/http-client-errors.mdx b/docs/platforms/apple/common/configuration/http-client-errors.mdx index c237ab5c8542c..f33b876ff9b57 100644 --- a/docs/platforms/apple/common/configuration/http-client-errors.mdx +++ b/docs/platforms/apple/common/configuration/http-client-errors.mdx @@ -4,7 +4,8 @@ sidebar_order: 13 description: "This feature, once enabled, automatically captures HTTP client errors, like bad response codes, as error events and reports them to Sentry" --- -Once enabled, this feature automatically captures HTTP client errors, like bad response codes, as error events and reports them to Sentry. The error event will contain the `request` and `response` data, such as `url`, `status_code`, and so on. +Once enabled, this feature automatically captures HTTP client errors, like bad response codes, as error events and reports them to Sentry. The error event will contain the `request` and `response` data, such as `url`, `status_code`, and so on. Depending on your HTTP request setup, it can happen that the stacktrace of these events doesn't pinpoint the exact location of the HTTP request in your code. If that's the case, you can look at the HTTP request info of the issue, which contains things like URL and HTTP headers. + Since 8.0.0, this feature has been enabled by default. To disable it: