[CI] SDK 10 dependency updates cannot restore .NET 9.0.22 Ref/Host packs (NU1102)

[dalexsoto]

Failure signature

source-related|SDK10-servicing-Messaging-net9|ref-apphost-9.0.22-unavailable|NU1102

Release/10.0.1xx dependency-update builds fail before tests while restoring Xamarin.Messaging.Build.csproj / Xamarin.MacDev.Tasks.slnx. The requested Microsoft.NETCore.App.Ref and platform-specific Microsoft.NETCore.App.Host.<RID> packages at 9.0.22 cannot be found in the configured NuGet sources (NU1102). The Linux restore reports 9.0.21 as the nearest version on one configured runtime feed. The package publication or feed-selection reason for the missing version is not yet established.

Confirmed occurrences

Monitored PR and exact head	Azure run, initial attempt 1, job and task	Failure evidence
#26684 988de13e35a114fc315667ba53564ac8aef153e5	API diff 15425080 / Detect API changes / Build; packages 15425077 / Build packages / Build; packages 15425079 / Build packages / Build and same run / Build on Linux / Build on Linux	Four root-task records on the first head, starting 2026-09-23 02:21:50 UTC, all reporting Ref/Host 9.0.22 missing during the Messaging project restore.
#26684 b022300f3674b13a5c9a46a5b49b80828432c655	API diff 15441750 / Detect API changes / Build; packages 15441742 / Build packages / Build; packages 15441749 / Build packages / Build and same run / Build on Linux / Build on Linux	Four further root-task records on a second head of the same PR, through 2026-09-24 02:27:14 UTC. Historical build/task logs and the retained binlog evidence identify the same NuGet version mismatch.
#26769 97f74aad156dec057950ac723d15b5e1a7fcba63	Simulator run 15497195 / Linux Build Verification / Build on Linux job cd95c9ab-ceee-5f36-46bb-743e43fba63c / task e8599f2d-16cf-5ca3-8351-5ddd36575f8c, task log 85	On initial stage/job/task attempt 1, the same Messaging restore reports NU1102 for Microsoft.NETCore.App.Ref (= 9.0.22) and Microsoft.NETCore.App.Host.linux-x64 (= 9.0.22) at 2026-09-29 02:22:32 UTC. The Linux job failed; other jobs and the parent run were still active when inspected.

First observed: 2026-09-23 02:21:50 UTC. Latest observed: 2026-09-29 02:22:32 UTC. Impact: nine confirmed root-task failures across two distinct monitored PRs. Eight failures and two heads on #26684 alone did not meet the cross-PR threshold; #26769 now does. The restore error blocks build verification before NUnit or API-comparison results and may also block package builds, as previously observed on #26684.

Investigation and classification

The new #26769 Azure task log identifies the exact package names, requested version, Messaging project and restore failure. The #26684 records identify the same normalized root across package, Linux and API-diff build tasks on two heads. This is a source-related dependency/feed-version mismatch, not a test assertion or demonstrated Azure Artifacts outage. There is no evidence that attempting a CI rerun without the missing packs would resolve it.

Separate all-state searches covered the stable signature, exact project and Linux task, NU1102, both pack names, version 9.0.22 and SDK servicing components. Bodies and non-ignored comments of 19 deduplicated candidates were inspected. #26479 explicitly tracks 9.0.21 and closed #26465 tracks 9.0.20; neither records 9.0.22. The other candidates concern distinct errors or platforms. No existing issue matches this version-specific signature.

Workaround and diagnostic limits

No verified workaround or publication ETA for the requested 9.0.22 packs is available. No monitor retry or bot-branch source edit was made: this is a source-related dependency failure, other #26769 jobs remain active, and complete all-actor accepted-request histories for the 25-per-PR / 10-per-head budgets remain uncertified. These are direct Azure builds with no Helix work items or NUnit test failures. Build artifacts and task logs have limited retention; no credentials, worker identities, machine IPs or personal data are included.

[rolfbjarne]

This can't be fixed until 9.0.22 packages are publicly available.

[dalexsoto]

#26769 regenerated servicing head: four exact Messaging restore recurrences

#26769, new head d98abff6710489788699a5204cdd50f0a80a95bd: external SDK/tooling update to 10.0.403-servicing.26480.109 and regenerated darc-dotnet feed did not clear the version-specific gate. All records below are initial stage/job/task attempt 1, not retries. Each Xamarin.Messaging.Build.csproj / Xamarin.MacDev.Tasks.slnx restore fails NU1102 for Microsoft.NETCore.App.Ref (= 9.0.22) and its platform Host pack; one configured servicing source offers 9.0.21 as nearest.

Run / exact task link	Log	Host pack, also required at 9.0.22	First NU1102 UTC
15529221 / build_packages / Build	145	Microsoft.NETCore.App.Host.osx-arm64	2026-10-01T02:26:52.5772390Z
15529227 / build_packages / Build	98	Microsoft.NETCore.App.Host.osx-arm64	2026-10-01T02:18:19.2351200Z
15529227 / linux_build_verification / Build on Linux	129	Microsoft.NETCore.App.Host.linux-x64	2026-10-01T02:21:53.3502977Z
15529230 / generate_api_diff / Build	83	Microsoft.NETCore.App.Host.osx-arm64	2026-10-01T02:18:36.9011700Z

Primary binlog proof: all-binlogs-15529221-1-1 and all-binlogs-15529227-1-1 each publish macios/msbuild/.build-stamp.binlog plus eight utility binlogs. Local Microsoft.AITools.BinlogMcp overview/error/project analysis of both primary binlogs confirms failed Restore / RestoreTask, Xamarin.MacDev.Tasks.slnx, Messaging project and the exact Ref/osx-arm64 Host 9.0.22 NU1102 errors. Builds lasted 9.9s / 11.9s in those binlogs, with 3 errors / 1 warning. This new-head root is not the old unresolved 180-minute compiler stall.

API publisher and baselines: run 15529230 publisher job 443a5880-1958-5052-6859-a80de6521633, Decompress task ddab1acc-f64a-509c-ea96-e2080ffe06f6, log 123, failed downstream on ENOENT for missing change-detection.zip. It is not another root occurrence. Neither current-PR/commit nor vs-stable comparison executed; no raw API-diff artifact was produced. No binding/suppression edit is indicated.

Signature/classification: source-related|SDK10-servicing-Messaging-net9|ref-apphost-9.0.22-unavailable|NU1102, source-related dependency/feed-version mismatch, not an established Azure outage or flaky test. 13 confirmed root-task occurrences across 2 distinct monitored PRs. This adds four distinct task records on a new head of the same PR, not another distinct PR. Package publication versus feed-selection cause and publication ETA remain unestablished; the existing issue context is retained.

Issue-specific checklist: the refreshed body has no Additional info to collect section. Exact head/run/definition/stage/job/task/attempt/log, package/RID/version, nearest servicing version, Messaging project, source update, primary binlog member/digest and restore errors were collected per occurrence. Exact Linux/API-task primary binlogs are unavailable: not published for those tasks, while their task logs establish the same root. Both raw API-diff artifacts and NUnit results are unavailable: restore failed before those stages. No Helix work item applies. Worker/IP/credential details are omitted; artifacts are retention-limited.

No monitor retry, source edit, commit or push. Missing required packs do not authorize reruns, and all-actor 25-lifetime / 10-head accepted-request counters remain uncertified. New automatic runs do not count as retries; the new head does not reset the lifetime budget.

[dalexsoto]

SDK 10.0.403-servicing.26501.112: 8 new exact restore failures

PR #26769 advanced through superseded Maestro head 79e802c88e5d37142ffc381294b44da0565dad1d (A) to regenerated head 8de216fc8dab0a6dc0cac9e58f2a2a0fa9a3e7b2 (B, current). The SDK/tooling and 3f34effc dependency-feed update did not clear the Messaging restore gate. Actual task logs on both heads identify SDK 10.0.403-servicing.26501.112, NU1102 for Microsoft.NETCore.App.Ref (= 9.0.22) and its platform Host pack; a configured servicing source still offers 9.0.21 as nearest.

Every row is initial stage/job/task attempt 1, not a retry. All six parent runs are now terminal failed.

Head	Run / job / exact root-task link	Log / Host RID	First error UTC
A	15545226 / Build packages / Build	145 / osx-arm64	2026-10-02T02:27:08.4653810Z
A	15545228 / Build packages / Build	98 / osx-arm64	2026-10-02T02:18:27.6681310Z
A	15545228 / Linux / Build on Linux	129 / linux-x64	2026-10-02T02:21:16.2440770Z
A	15545229 / Detect API changes / Build	83 / osx-arm64	2026-10-02T02:18:46.3255810Z
B	15545230 / Build packages / Build	145 / osx-arm64	2026-10-02T02:27:07.2785290Z
B	15545231 / Build packages / Build	98 / osx-arm64	2026-10-02T02:19:01.6992220Z
B	15545231 / Linux / Build on Linux	129 / linux-x64	2026-10-02T02:20:53.4261351Z
B	15545232 / Detect API changes / Build	83 / osx-arm64	2026-10-02T02:19:15.8124770Z

Binlog proof: all-binlogs-15545226-1-1, all-binlogs-15545228-1-1, all-binlogs-15545230-1-1 and all-binlogs-15545231-1-1 each map by Azure artifact source GUID to Build packages job 600d49c6-e96b-5e8b-2c3a-9f351e2e5848. Their exact macios/msbuild/.build-stamp.binlog members were downloaded, fingerprinted and analyzed with binlog MCP overview/errors: failed Restore / RestoreTask, Messaging project, exact Ref/osx-arm64 Host 9.0.22 NU1102, 3 errors / 1 warning in each. The primary members and SHA-256 digests are retained in the occurrence ledger.

API baselines and cascades: runs 15545229 / 15545232 did not reach either the current-PR/commit or vs-stable comparison. No raw API-diff artifact was produced. Their publisher job 443a5880-1958-5052-6859-a80de6521633, Decompress task ddab1acc-f64a-509c-ea96-e2080ffe06f6, log 123, failed downstream with ENOENT for change-detection.zip; these are cascades, not additional root occurrences. No binding or suppression edit is indicated.

Signature/classification: source-related|SDK10-servicing-Messaging-net9|ref-apphost-9.0.22-unavailable|NU1102; source-related dependency/feed-version mismatch, not demonstrated infrastructure or a flaky test. 21 confirmed root-task occurrences / 2 distinct monitored PRs. This adds 8 previously unreported task records across 2 new head(s) of the same PR, not another distinct PR. No recovery or verified workaround is established; package-publication versus feed-selection cause/ETA remains unestablished.

Issue-specific diagnostics: the freshly read body has no Additional info to collect section. Each occurrence includes its exact PR/head/pipeline/definition/stage/job/task/attempt/log, SDK, required pack/RID/version, nearest servicing version and error time. Unavailable per occurrence: the four Linux/API root tasks have no published task-specific primary binlog (task logs provide the exact error); the four macOS package root tasks have the analyzed primary binlogs above. No NUnit failure result exists because restore failed before tests. For both API root tasks, both raw comparison artifacts are unavailable because neither comparison executed. No Helix work item applies to any of these direct Azure jobs. Worker/IP/credential details are omitted; remote diagnostics are retention-limited.

No monitor retry, PR source edit, commit or push. Initial automatic runs do not consume retry counts or demonstrate flakiness. Full all-actor 25-lifetime / 10-head accepted-request grouping remains uncertified; new heads never reset the PR-lifetime budget.