Xcode@2 is retired: replace it with Xcode@5
The short answer
- Retirement date
- Removal date
- . Pipelines that still use it fail after removal.
- Replacement
Xcode@5- Kind of migration
- manual migration
- Automatic rewrite
- No. This task needs a manual migration. trasloco modernize --check still finds the step.
- Recommended action
- Migrate this step manually to Xcode@5, reviewing the documented behavior and input differences.
Official sources
- Official task retirement announcement
- Task definition: Xcode (task.json)
- Task definition: XcodeV5 (task.json)
Last verified:
Why does my pipeline show a retirement error for Xcode@2?
On , Azure Pipelines shows a retirement error for Xcode@2, but the run does not fail. On , pipelines that still use Xcode@2 fail.
Find it in your pipelines
With trasloco:
trasloco modernize --check
Install trasloco from the latest release.
With plain grep, nothing to install:
grep -rniwF 'Xcode@2' --include='*.yml' --include='*.yaml' .
How to migrate
Migrate this step manually to Xcode@5, reviewing the documented behavior and input differences.
The task definition of the replacement is linked under official sources above.
Xcode@2 retirement FAQ
Is Xcode@2 deprecated?
Yes. Xcode@2 is retired on 2026-10-15. Azure Pipelines shows a retirement error, but the run does not fail until removal.
When does Xcode@2 stop working?
Xcode@2 is removed on 2027-03-15. Pipelines that still use it fail after removal.
What should I use instead of Xcode@2?
Replace Xcode@2 with Xcode@5.
Related retired tasks
- AndroidBuild@1 — manual migration
- AndroidSigning@1 — manual migration
- AndroidSigning@2 — manual migration
- AzureCLI@0 — manual migration
- AzureMonitor@0 — manual migration
- Xcode@3 — manual migration
- Xcode@4 — replacement with input changes
- XcodePackageiOS@0 — manual migration