Xcode@4 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
- replacement with input changes
- Automatic rewrite
- Not yet. Automatic rewrite is planned for this kind of task (replacement with input changes). Today, trasloco modernize --check finds the step and you change it by hand.
- Recommended action
- Replace Xcode@4 with Xcode@5 and review the replacement inputs before updating the pipeline.
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@4?
On , Azure Pipelines shows a retirement error for Xcode@4, but the run does not fail. On , pipelines that still use Xcode@4 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@4' --include='*.yml' --include='*.yaml' .
How to migrate
Replace Xcode@4 with Xcode@5 and review the replacement inputs before updating the pipeline.
The task definition of the replacement is linked under official sources above.
Xcode@4 retirement FAQ
Is Xcode@4 deprecated?
Yes. Xcode@4 is retired on 2026-10-15. Azure Pipelines shows a retirement error, but the run does not fail until removal.
When does Xcode@4 stop working?
Xcode@4 is removed on 2027-03-15. Pipelines that still use it fail after removal.
What should I use instead of Xcode@4?
Replace Xcode@4 with Xcode@5.
Related retired tasks
- ArchiveFiles@1 — replacement with input changes
- AzureFunction@0 — replacement with input changes
- CacheBeta@0 — replacement with input changes
- cURLUploader@1 — replacement with input changes
- DotNetCoreCLI@0 — replacement with input changes
- Xcode@2 — manual migration
- Xcode@3 — manual migration
- XcodePackageiOS@0 — manual migration