iOS CI Newsletter - Issue #60

ISSUE 60 28th of January 2025

Sponsor Supercharge your GitHub Actions with M4 Pro runners from the creators of Tart Enjoy the fastest Apple Silicon chips at a fixed monthly price — fully managed so you can focus on shipping great code. Get an additional 50% off your first month with code IOSCI50OFF — exclusively for subscribers. Start your free 10-day trial now.

COMMUNITY ARTICLES 😱 Your app might be removed from the EU App Store In Issue #53 of the newsletter, I mentioned that Apple was implementing changes to apps available in the European Union to comply with the Digital Services Act. One of these changes requires developers to declare their trader status to keep their apps available in the European Union's App Stores. This requirement will take full effect on February 17th. Starting on this date, any app without a declared and verified trader status will be removed from the App Store in the European Union until the status is provided and approved. If you haven't addressed this yet, act NOW!

📦 The Tuist Swift Package Manager Registry Since I started using Swift Package Manager as my dependency manager of choice for Apple platform apps, I've been hoping for a registry-based solution that allows developers to download source archives of dependencies instead of cloning entire repositories. Not only does this approach improve performance, but it also mitigates some potential security risks. Although Package Registry standard has been around for some time, this registry built by Tuist is the first fully-fledged solution I've seen that's ready to use right away.

🌳 How to use Git Flow as your branching strategy Do you work in a team and often struggle with merge conflicts or determining if your development branch is production-ready? Do you not have a clear branching strategy for your repository? If these challenges sound familiar, you should check out this article by Chase!

👨‍✈️ Give Copilot context about your repository GitHub has just improved the Copilot chat experience by allowing developers to provide specific context about a repository, making the chat in Visual Studio Code or Github.com more useful and tailored to the repository's needs. To set this up, simply follow the instructions in the announcement post and create a configuration file where you define the context for Copilot. This file helps Copilot better understand your project, enabling more relevant suggestions and guidance while coding.

BEFORE YOU GO... Did you know that if you don't use an App Group to set up Swift Data, your database file might end up in a folder that's shared with other apps, which can have unexpected consequences? 😱

Unsubscribe | View in the browser