[jamescrosswell]

Follows #5566 (RC 1) through to RC 2, targeting version7.

Closes #5724

The version bump

	RC 1	RC 2
SDK (global.json)	11.0.100-rc.1.26425.128	11.0.100-rc.2.26504.105
workload set (global.json)	11.0.100-rc.1.26458.5	11.0.100-rc.2.26509.2
prerelease Microsoft.* package refs	11.0.0-rc.1.26425.128	11.0.0-rc.2.26504.105
iOS / Mac Catalyst TFM	net11.0-ios26.5 / net11.0-maccatalyst26.5	net11.0-ios27.0 / net11.0-maccatalyst27.0

The workload set is the one the macios RC 2 release names. NuGet also has a later 26513.2, but its manifests are identical.

Android didn't move. The 37.2 RC 2 pack binds API 37.1 and 37.2, but still defaults to 37.0. It does switch Release assembly stores to Zstandard level 22 (dotnet/android#12415), which Sentry.Android.AssemblyReader already decodes.

Xcode 27: the runner image, the platform version and XHarness

The RC 2 Apple packs (27.0.12212) accept only platform version 27.0 and require Xcode 27.0. Three things follow from that.

• Runner image. macos-26 tops out at Xcode 26.6; Xcode 27 is only on the preview xcode-27 image (macOS 27). Every macOS job moves there, and the Xcode pin moves to /Applications/Xcode_27.app, which is the real path (the 27.0 names are symlinks). It's a preview image, so expect some queueing. net10.0-ios app builds would need Xcode 26, but CI only builds the latest iOS TFM.
• Platform version. It's spelled out in more places than Directory.Build.props: the device test app's TargetPlatformVersion, integration-test/common.ps1, ios.Tests.ps1, the integration test app and the simulator picker in device-test-utils.ps1. Only the device test app failed the build (NETSDK1140); the rest would have failed at test time.
• XHarness. Xcode 27 replaced Simulator.app with DeviceHub.app. The mlaunch in our pinned XHarness (26117.1) can't start the simulator, and XHarness reports that as exit code 80 APP_CRASH, even though the app never launched. 26506.3 handles it.

Apps built with Xcode 27 must adopt the UIScene lifecycle

Apple now requires scene adoption for apps built with the 27 SDKs, and MAUI RC 2's templates adopt it. Our apps hadn't. On an iOS 27 simulator, Sentry.Samples.Maui sat on the .NET launch screen for minutes; with a UIApplicationSceneManifest and a SceneDelegate it renders immediately. The device test app and the iOS integration test app would have hung the same way. Changes:

• MAUI apps (Sentry.Samples.Maui, Sentry.Maui.Device.TestApp, integration-test/maui-device): the manifest plus an empty MauiUISceneDelegate subclass, as in the templates.
• Sentry.Samples.Ios: it already had an unused SceneDelegate. The UI moves into it from AppDelegate.FinishedLaunching, and the manifest is added. Sentry.Samples.MacCatalyst was already scene-based.

Three SDK bugs RC 2 surfaced

1. in_foreground disappears from MAUI events on iOS and Mac Catalyst. Sentry.Maui set InForeground from the app-level OnActivated/OnResignActivation/DidEnterBackground lifecycle events. Under the scene lifecycle UIKit doesn't call those; MAUI raises SceneOnActivated and friends instead. InForeground stays null, and the event processor writes that over the enricher's value. Now it listens to both.

The integration test app's OnActivated hook had the same problem and moves to its SceneDelegate. That test now also asserts "in_foreground":true; without the fix it fails in both Release and Debug.

2. Native AOT publish stopped uploading symbols — any TFM, with the .NET 11 SDK. From RC 2, PublishAot implies UseOptimizedPublish, and Publish goes through a new _PublishOptimizedBuildAlternative that runs Compile and the publish targets but never Build (dotnet/sdk#54515). CheckSentryCLI, which every upload and release target depends on, was AfterTargets="Build". So nothing ran, and nothing errored. This is decided by the SDK, not the TFM, so net8.0–net10.0 apps published with the .NET 11 SDK are hit too.

CheckSentryCLI and the release targets now also run after _PublishOptimizedBuildAlternative. This was caught by the native AOT publish cases in cli.Tests.ps1, all of which failed for net10.0 and net11.0. Release creation has no test; I checked locally that the release targets now run during an AOT publish.

3. Apple symbol upload sent the wrong PDBs for post-processed framework assemblies. #5566 probed both linked/ and postprocessed-assemblies/ on the basis that only one ever exists. RC 2 writes both. The post-processor rewrites some assemblies (Microsoft.MacCatalyst, Microsoft.Maui.Controls, Microsoft.Maui.Essentials in the MAUI sample) and gives them new PDB IDs, and only the postprocessed-assemblies copies ship in the app bundle. So every PDB was uploaded twice, and the linked/ copies of those assemblies matched nothing that ships. linked/ is now only the fallback. cli.Tests.ps1 compares file names with Sort-Object -Unique, so it couldn't have caught this; it now asserts that nothing is collected from linked/.

#1 and #2 are not specific to version7. A .NET 10 MAUI app built with Xcode 27 also has to adopt scenes. And once .NET 11 GA ships, anyone publishing Native AOT with the .NET 11 SDK hits #2, whatever the TFM. Backporting them to main is tracked separately in #5726 (in_foreground) and #5727 (AOT publish).

Worth flagging

• MAUI RC 2 fixed its Compatibility ILLink descriptors: a Release build that trims the Mac Catalyst sample produces no IL2037s. I left the WarningsNotAsErrors demotion from feat: add support for .NET 11 RC 1 #5566 in place for now.
• dotnet/sdk#56484 (open) extends optimized publish to trimmed apps. The non-AOT upload still hooks Build, so if that lands, trimmed publishes will need the same treatment.
• With SentryCreateRelease, a plain Build runs _GetSentryRelease (AfterBuild) before CheckSentryCLI (AfterTargets="Build") has set UseSentryCLI. That predates this branch and isn't touched here.

Not in this PR

• ref: Remove Android assembly store v4 support (never shipped) #5608 (dropping assembly store v4 support) was waiting on this bump, and can go next.
• runtime-deps container pins stay on the 11.0-preview-* tags, which still resolve. Per the CONTRIBUTING.md checklist they get blanked at GA.

CONTRIBUTING.md's upgrade checklist gains a row for each of these.

🤖 Generated with Claude Code

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 75.70%. Comparing base (1ce152c) to head (1416022).
⚠️ Report is 1 commits behind head on version7.

Additional details and impacted files

@@             Coverage Diff              @@
##           version7    #5725      +/-   ##
============================================
+ Coverage     75.60%   75.70%   +0.09%     
============================================
  Files           522      525       +3     
  Lines         19042    19140      +98     
  Branches       3679     3694      +15     
============================================
+ Hits          14396    14489      +93     
- Misses         3810     3812       +2     
- Partials        836      839       +3     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[jamescrosswell]

Note to reviewers wondering why this has been removed: once the app adopts scenes, UIKit stops calling OnActivated. The test hook has moved to SceneDelegate.OnActivated(UIScene)

[ric-oliv]

#5730 changed the Scene handlers after review. In 631258e, SceneOnResignActivation and SceneDidEnterBackground keep InForeground true while another window is still active. This PR still sets both to false, so the next main to version7 sync will conflict in SentryMauiAppBuilderExtensions.cs.

git cherry-pick 631258e applies cleanly on net11-rc2. With the same lines on both branches, the sync merges that file without a conflict.

[jamescrosswell]

#5730 changed the Scene handlers after review. In 631258e, SceneOnResignActivation and SceneDidEnterBackground keep InForeground true while another window is still active. This PR still sets both to false, so the next main to version7 sync will conflict in SentryMauiAppBuilderExtensions.cs.

git cherry-pick 631258e applies cleanly on net11-rc2. With the same lines on both branches, the sync merges that file without a conflict.

Cherry-picked 631258e, so the Scene handlers now match what's on main.

[ric-oliv]

Related, but outside this PR: a single-target app published without -f still uploads no debug files with the .NET 11 SDK, because NuGet imports Sentry.props before the project sets TargetFramework. Filed as #5744.

[ric-oliv]

LGTM and builds fine locally with Xcode 27...
I agree with adding the extra comment, but I'll leave it approved anyway.