Failure signature
fsharplibrary embeds ILLink.Substitutions.xml, but its resource-removal directives name six resources absent from the assembly: FSharpSignatureDataB.fsharplibrary, FSharpOptimizationInfo.fsharplibrary, FSharpOptimizationData.fsharplibrary, FSharpSignatureData.fsharplibrary, FSharpSignatureInfo.fsharplibrary, and FSharpOptimizationDataB.fsharplibrary. _RunILLink reports six IL2040 errors, then NETSDK1144. This is a source/dependency resource mismatch before test execution, not a flaky test or CI infrastructure outage. The upstream step that produced the mismatched descriptor has not been isolated.
Confirmed monitored PRs and occurrences
- #26683: 170 confirmed configuration failures across three heads/runs, one distinct PR:
204bc97f6a535e1dfc37d1f0231ad8722386fa24 / run 15441688 (59 records, five jobs; e.g. T: monotouch_macos / Run tests); 5cb483e94709208bac50a4a7b28350032626419b / run 15445962 (58 records, four jobs); e1ab40f6e574416ce3684d64243b04e9cd4f6ae5 / run 15461912 (53 records, four jobs). Azure TestSummary and per-variation binlogs confirm the same six-resource signature on macOS, Mac Catalyst, iOS, and tvOS.
- #26695: head
4fc295ad233069ddec98069c6f2239f858122846, simulator run 15482109 / Build macOS tests / Package macOS tests, stage/job/task attempt 1, one new confirmed occurrence. The preceding Build task succeeded, but build-maccatalyst-dotnet-arm64-monotouch-test failed while packaging tests at 2026-09-27 22:34:01 UTC with the identical six IL2040 resources and NETSDK1144. The parent run was still active at diagnosis. A newer head 837a18b460563abb04e7c5cc1aabc1c510f9e9a1 has separate CI; it does not establish a fix for this root.
Totals: 171 confirmed failure records across two distinct monitored PRs, not 171 independent PRs. First failure time: 2026-09-24 03:27:58 UTC (run 15441688). Latest: 2026-09-27 22:34:01 UTC (run 15482109).
Impact and investigation
The error blocks mac-test-package.zip and numerous simulator test builds before NUnit runs. #26683's failed-variation binlogs and #26695's Azure task log show the exact same resource names and linker codes. #26695 also has separate Xamarin.MacDev.csproj .NET 10.0.13 restore failures in other jobs; those NU1102/NU1103 failures are not counted here.
Separate searches across all open and closed dotnet/macios issues for the signature, exact F# resource names, IL2040, NETSDK1144, monotouch-test, Package macOS tests, and ILLink.Substitutions.xml found no matching root. Inspected candidates included #26017 (IL2036 unresolved type), #26390 (IL2015 enum substitution), and #14257 (different assembly/resource behavior). No existing canonical issue or verified workaround was found. Identify where the descriptor and assembly diverge, then validate the correction on each affected branch; rerunning a deterministic source failure merely to make CI green is not a workaround. Azure diagnostic artifacts have limited retention.
Failure signature
fsharplibraryembedsILLink.Substitutions.xml, but its resource-removal directives name six resources absent from the assembly:FSharpSignatureDataB.fsharplibrary,FSharpOptimizationInfo.fsharplibrary,FSharpOptimizationData.fsharplibrary,FSharpSignatureData.fsharplibrary,FSharpSignatureInfo.fsharplibrary, andFSharpOptimizationDataB.fsharplibrary._RunILLinkreports sixIL2040errors, thenNETSDK1144. This is a source/dependency resource mismatch before test execution, not a flaky test or CI infrastructure outage. The upstream step that produced the mismatched descriptor has not been isolated.Confirmed monitored PRs and occurrences
204bc97f6a535e1dfc37d1f0231ad8722386fa24/ run 15441688 (59 records, five jobs; e.g.T: monotouch_macos/Run tests);5cb483e94709208bac50a4a7b28350032626419b/ run 15445962 (58 records, four jobs);e1ab40f6e574416ce3684d64243b04e9cd4f6ae5/ run 15461912 (53 records, four jobs). Azure TestSummary and per-variation binlogs confirm the same six-resource signature on macOS, Mac Catalyst, iOS, and tvOS.4fc295ad233069ddec98069c6f2239f858122846, simulator run 15482109 /Build macOS tests/Package macOS tests, stage/job/task attempt 1, one new confirmed occurrence. The precedingBuildtask succeeded, butbuild-maccatalyst-dotnet-arm64-monotouch-testfailed while packaging tests at 2026-09-27 22:34:01 UTC with the identical sixIL2040resources andNETSDK1144. The parent run was still active at diagnosis. A newer head837a18b460563abb04e7c5cc1aabc1c510f9e9a1has separate CI; it does not establish a fix for this root.Totals: 171 confirmed failure records across two distinct monitored PRs, not 171 independent PRs. First failure time: 2026-09-24 03:27:58 UTC (run 15441688). Latest: 2026-09-27 22:34:01 UTC (run 15482109).
Impact and investigation
The error blocks
mac-test-package.zipand numerous simulator test builds before NUnit runs. #26683's failed-variation binlogs and #26695's Azure task log show the exact same resource names and linker codes. #26695 also has separateXamarin.MacDev.csproj.NET 10.0.13 restore failures in other jobs; thoseNU1102/NU1103failures are not counted here.Separate searches across all open and closed
dotnet/maciosissues for the signature, exact F# resource names,IL2040,NETSDK1144,monotouch-test,Package macOS tests, andILLink.Substitutions.xmlfound no matching root. Inspected candidates included #26017 (IL2036unresolved type), #26390 (IL2015enum substitution), and #14257 (different assembly/resource behavior). No existing canonical issue or verified workaround was found. Identify where the descriptor and assembly diverge, then validate the correction on each affected branch; rerunning a deterministic source failure merely to make CI green is not a workaround. Azure diagnostic artifacts have limited retention.