Summary

The MacCatalyst Controls Tests Helix work item exits with code 70 (XHarness app-launch failure) and produces no test result files for both the Mono and CoreCLR legs. The test app crashes or fails to launch on the macOS Helix runners.

Build Information

• Pipeline: maui-pr-devicetests (ID 314)
• Build: 1455984 (latest), 1455596
• Branch: net11.0
• First seen: 2026-06-09 (build 1455596)
• Occurrences: 2 in last 2 builds

Affected Legs

• net11.0 Mono MacCatalyst Helix Tests — Run DeviceTests MacCatalyst (Mono) — Controls Tests, exit code 70
• net11.0 CoreCLR MacCatalyst Helix Tests — Run DeviceTests MacCatalyst (CoreCLR) — Controls Tests, exit code 70

Error Message

Category file not found after 60 seconds...

ERROR: No test result files found. All test processes may have crashed.

No results file found in any of the following formats: xunit, junit, trx

+ exit 70
['Controls Tests' END OF WORK ITEM LOG: Command exited with 70]

(Helix job 9c6c7cbe-65be-49f3-9dfe-4bde8ace9945, work item Controls Tests, build 1455984 Mono)

Recommended Action

1. Check recent changes to Microsoft.Maui.Controls.DeviceTests for anything that could prevent the test host from initializing on macOS.
2. Inspect the full Helix console log for the work item — the test categories file is never written, suggesting the app crashes before the test runner initializes.
3. Compare with passing MacCatalyst legs (e.g., Essentials, Core) to narrow down whether this is a Controls-specific regression or a runtime issue.
4. Note: a separate issue ([ci-scan-net11] MacCatalyst CoreCLR device tests always timeout on osx.15.arm64.maui.open Helix queue (net11.0) #35746) tracks a CoreCLR-only timeout failure on osx.15.arm64.maui.open. This new failure is exit code 70 (app crash, not timeout) affecting both Mono and CoreCLR and appears to be a different root cause.

Generated by CI Failure Scanner (net11.0) · sonnet46 10.9M · ◷