Stay up to date with the latest iOS CI/CD news

Every two weeks, directly to your inbox and packed with everything you need to know and be aware of so that you're always prepared for the next app release!

Read and trusted by engineers from:

Issue 82

Sponsored

​​Try new Amazon EC2 M4 instances​​​

Provision and access macOS environments within minutes, dynamically scale capacity as needed, and benefit from pay-as-you-go pricing. Available as M4 and M4 Pro for your demanding CI pipelines, EC2 M4 instances deliver up to 20% better build performance than M2 instances.

Hey everyone! I hope you’ve all had a fantastic couple of weeks — welcome to another issue of the newsletter!

Diving right into the content this time, here’s what you can expect from today’s newsletter:

  • How to optimize your xcodebuild logs for AI agents.
  • GitHub Actions workflows for Swift Packages.
  • How to improve your SwiftUI app’s performance.
  • How git hooks can save you unnecessary CI/CD runs.

​🤖 How could AI understand Xcode build logs?​​

Have you ever tried scrolling through hundreds — or even thousands — of lines of xcodebuild output just to understand what happened in your build?

As Pedro Piñera rightly points out in his article on the Tuist blog, the build system speaks a language optimised for machines, not for humans or AI agents. It raises an important question: how could we evolve this in the future to make build output more parseable for both developers and AI?

Pedro’s article is a must-read. He highlights some of the work already happening in this space — including tools like xcsift by Łukasz Domaradzki, which I shared back in Issue 77 of the newsletter. It reformats xcodebuild output to make it far more approachable and AI-friendly.

​​💨 [Workshop] How to improve your SwiftUI app’s performance with Xcode 26​​​​

Have you ever spent hours trying to diagnose UI hangs or hitches, or received user feedback about your app feeling sluggish on certain devices? And when you did, did you feel unsure where to even begin?

You’re not alone! I’ve spent much of my career working on products where performance was critical to their success, and over time I’ve learned how to track down and fix the subtle — and sometimes not-so-subtle — bottlenecks that make native Apple apps stutter.

Join me next week for an online workshop where I’ll share all these techniques and insights!

​​​📦 A list of ready-to-use GitHub Actions workflows for Swift Packages​​​​​

Do you maintain a Swift Package and find yourself doing the same manual, repetitive tasks over and over?

If so, you should definitely check out the new collection of GitHub Actions workflow examples that Daniel Saidi has added to his open-source project Swift Package Scripts. From building and testing your package across multiple platforms to generating a binary .xcframework, it’s a great starting point for automating your entire workflow.

Start streamlining your process today!

​⏭️ Skip unnecessary CI/CD runs with Git Hooks​​​​​​

While it’s important to ensure your coding style and best practices are enforced in CI/CD, running full workflows just to catch formatting issues can be inefficient and costly.

A better approach is to handle these checks locally by setting up git hooks that prevent you from pushing code that would otherwise break your CI/CD workflows. This creates a much faster and more efficient feedback loop — like the approach Keith Harrison shares in his article.