docs(dotnet): Remove outdated 4.12.0 iOS troubleshooting entry

[SatvikMishra08]

DESCRIBE YOUR PR

Removes the "Updating to 4.12.0 broke my .NET iOS App" section from the .NET troubleshooting page. It covered the Xcode 16 / iOS workload mismatch in SDK 4.12.x, and as @jamescrosswell noted in getsentry/sentry-dotnet#5636, that MAUI version is no longer supported. Nothing else on the docs site links to that heading.

Resolves getsentry/sentry-dotnet#5636

IS YOUR CHANGE URGENT?

• Urgent deadline (GA date, etc.): YYYY-MM-DD
• Other deadline: YYYY-MM-DD
• No deadline: Not urgent, can wait up to 1 week+

SLA

Please give the docs team up to 1 week to review.

PRE-MERGE CHECKLIST

• Checked Vercel preview for correctness, including links
• PR was reviewed and approved by any necessary SMEs (subject matter experts)
• PR was reviewed and approved by a member of the Sentry docs team

LEGAL BOILERPLATE

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

EXTRA RESOURCES

• Sentry Docs contributor guide

[vercel]

@SatvikMishra08 is attempting to deploy a commit to the Sentry Team on Vercel.

A member of the Team first needs to authorize it.

[cursor]

The plan checks client errors on the changed troubleshooting page. It also watches sibling .NET page errors and site-wide client errors. An issue escalates when new errors appear on that page or .NET error volume rises.

Services: sentry-docs.

Mention @change-monitor in a comment to update the plan.

Plan

What changed

The .NET troubleshooting page no longer shows the Updating to 4.12.0 iOS section. sentry-docs must deploy before this change is live. The client runtime tag sentry-docs matches that catalog id. The pull request names issues/5636.

Risk

A broken MDX rebuild can fail that page or other .NET docs pages. Readers who still use SDK 4.12.x lose the old Xcode 16 note. The blast radius is the changed page and sibling .NET docs.

Intended effect

This docs edit has no queryable Sentry signal. Sentry does not record whether a heading is present. The executor cannot set intended_effect from telemetry. absent would mean the live page still shows the 4.12.0 heading.

Regression watch

This diff can break render of the .NET troubleshooting page. It can also break sibling .NET docs that share the same catch-all route. Watch client errors users would see. Traces sample at 30 percent.

The 24h error window is quieter than the prior 7d total of 12032 events. That 7d total may include a burst of Algolia and kapa fetch noise. Do not treat a return of those same titles as this change.

Signal	Baseline	Window	Rule	Source
Production errors on url platforms/dotnet/troubleshooting	0 events	2026-10-07T07:28:18Z to 2026-10-08T07:28:18Z	Hold at zero. Any new event is a regression.	Sentry org sentry project docs. Query environment:production AND url:*platforms/dotnet/troubleshooting*
Production errors on url platforms/dotnet	17 events. Share of site errors 17 of 98.	2026-10-07T07:28:18Z to 2026-10-08T07:28:18Z	Hold at or below 17 events. Escalate if the count or the 17 percent share rises.	Sentry org sentry project docs. Query environment:production url:*platforms/dotnet*
Production client errors	98 events	2026-10-07T07:28:18Z to 2026-10-08T07:28:18Z	Hold near 98 events. Escalate if new MDX or render titles appear. Current top titles are Algolia fetch, kapa fetch, and removeChild.	Sentry org sentry project docs. Query environment:production with count()

.NET url errors in this window were mostly removeChild plus Algolia fetch. Those titles already exist. A new title on the troubleshooting url is the first user-facing failure for this diff.

Not observable

Heading text on the live page is not in Sentry. Pageload traces filtered by http.url platforms/dotnet/troubleshooting returned no rows in the same 24h window.