Failure signature
During Provision system dependencies, the required iOS 16.0 simulator is unavailable through xcodebuild, so provisioning falls back to Apple's downloadable simulator index. The runtime download then fails with:
curl: (56) Recv failure: Connection reset by peer
Failed to download the iOS 16.0 simulator runtime.
The iOS 16.0 simulator is not installed, and it couldn't be downloaded.
Confirmed occurrences
Total: 3 jobs across 2 distinct monitored PRs.
First observed: 2026-07-24 00:07 UTC. Latest observed: 2026-07-24 01:04 UTC.
Classification and impact
This is a CI infrastructure/network failure, not a source build or test failure:
- It reproduces on unrelated PRs and three different workers.
- The failure occurs before repository tests start.
- Later missing TestSummary, HtmlReport, and drop artifacts are cascading errors caused by provisioning not completing.
Investigation performed
- Inspected each Azure timeline and selected the first failed task in each job.
- Verified the exact simulator asset and normalized curl error in the provisioning task logs.
- Searched all open and closed
dotnet/macios issues using the exact exception, simulator runtime name, task name, and downloadable-index fallback; no matching issue existed.
- Kept this separate from Xcode archive transport failures because the affected asset and provisioning phase differ.
Retry status and workaround
Both affected builds are still active, so no retry has been submitted. Once each run is terminal, refresh the PR head and mergeability, reconcile retry budgets, confirm no equivalent attempt is active, then rerun failed jobs.
Azure task logs have limited retention.
Failure signature
During
Provision system dependencies, the required iOS 16.0 simulator is unavailable throughxcodebuild, so provisioning falls back to Apple's downloadable simulator index. The runtime download then fails with:Confirmed occurrences
c6514d837dbf5f878369ed1176979040e1d2ab93AcesShared 61c6514d837dbf5f878369ed1176979040e1d2ab93AcesShared 7384d989d3c2e6b0423d061fa59431d104157c895dAcesShared 103Total: 3 jobs across 2 distinct monitored PRs.
First observed: 2026-07-24 00:07 UTC. Latest observed: 2026-07-24 01:04 UTC.
Classification and impact
This is a CI infrastructure/network failure, not a source build or test failure:
Investigation performed
dotnet/maciosissues using the exact exception, simulator runtime name, task name, and downloadable-index fallback; no matching issue existed.Retry status and workaround
Both affected builds are still active, so no retry has been submitted. Once each run is terminal, refresh the PR head and mergeability, reconcile retry budgets, confirm no equivalent attempt is active, then rerun failed jobs.
Azure task logs have limited retention.