# Xcode Published articles for Xcode. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Automating App Store Screenshots DevFeed: [Automating App Store Screenshots]() Original publisher: [Read original article]() Author: Khan Academy Published: 2017-03-27T22:00:00Z Content type: tutorial Language: en Sources: [Khan Academy]() Topics: [iOS](), [ui-testing](), [Xcode](), [Sketch](), [Mobile](), [Testing]() Tags: [app-store](), [design](), [engineering](), [fastlane](), [ios](), [iphone](), [mobile](), [news](), [screenshots](), [testing](), [ui-testing](), [xcode]() ### AI overview A tutorial describing how Khan Academy automated App Store and Play Store screenshots with Xcode UI tests, Fastlane, a Snapfile, and a homegrown Sketch file. The team reduced screenshot update time from about a week to about an hour. ### Source excerpt By Bryan Clark One of the more tedious design tasks is keeping your App Store promo images up-to-date. ... Read more ## Introducing SwiftTweaks DevFeed: [Introducing SwiftTweaks]() Original publisher: [Read original article]() Author: Khan Academy Published: 2016-05-09T22:00:00Z Content type: release Language: en Sources: [Khan Academy]() Topics: [Swift](), [iOS](), [Xcode](), [Objective-C](), [feature flags]() Tags: [code](), [engineering](), [feature](), [feature-flags](), [interface](), [ios](), [mobile](), [news](), [objective-c](), [swift](), [xcode]() ### AI overview Khan Academy introduces SwiftTweaks, a Swift library for adjusting parameters in iOS apps on a device without recompiling. The article explains how to create tweak libraries, use tweak values and bindings, adjust animation settings, and access the runtime interface. ### Source excerpt By Bryan Clark Today, we're releasing SwiftTweaks, a way to adjust your Swift-based iOS app without needing to ... Read more ## Open-Source Project Brings Full iOS 27 Virtualization to Apple Silicon DevFeed: [Open-Source Project Brings Full iOS 27 Virtualization to Apple Silicon]() Original publisher: [Read original article]() Author: Sergio De Simone Published: 2026-09-12T16:00:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [iOS](), [Tooling](), [Command-line interface](), [debugging](), [App]() Tags: [apple](), [cli](), [debugging](), [development](), [ios](), [ios-27-virtualization](), [iphone](), [kernel](), [macos](), [mobile](), [mobile-testing](), [news](), [open-source](), [research](), [reverse-engineering](), [security](), [ssh](), [testing](), [virtualization](), [xcode]() ### AI overview vphone-cli runs a full iOS 27 system as a virtual machine on Apple Silicon using Apple's Virtualization.framework. The article contrasts it with the Xcode iPhone Simulator and highlights uses in security research, reverse engineering, debugging, and automated testing. ### Source excerpt The open-Source project vphone-cli enables a full iOS 27 system to run as a virtual machine on Apple Silicon. Built on Apple's own Virtualization.framework rather than traditional emulation, the project opens up new possibilities for security research, reverse engineering, and automated iOS testing. By Sergio De Simone ## Moving from XCTest to Swift Testing \[FREE\] DevFeed: [Moving from XCTest to Swift Testing \[FREE\]]() Original publisher: [Read original article]() Author: renan.dias Published: 2026-09-11T18:41:42Z Content type: tutorial Language: en Sources: [Kodeco | High quality programming tutorials: iOS, Android, Swift, Kotlin, Unity, and more]() Topics: [Swift Testing](), [Unit testing](), [Xcode](), [agentic-coding](), [SwiftUI](), [iOS]() Tags: [agentic](), [agentic-ai](), [app](), [apple](), [article](), [free](), [how-to](), [ios](), [swift-testing](), [swiftui](), [testing](), [xcode]() ### AI overview A tutorial on migrating unit tests from Apple's XCTest framework to Swift Testing. It explains common testing scenarios, Swift Testing's newer syntax and constructs, and how Xcode's Agentic Coding can assist with the migration while working on a SwiftUI coffee-ordering app. ### Source excerpt Swift Testing is Apple's replacement for the objective-C XCTest unit testing framework. Discover how to migrate your existing XCTest suites over to Swift Testing, including how to get some assistance from Xcode's agentic AI tooling. ## A Mac App, Not an iOS App on a Mac DevFeed: [A Mac App, Not an iOS App on a Mac]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-09-06T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [macOS](), [iOS](), [Xcode]() Tags: [ios](), [mac](), [macos](), [release](), [xcode]() ### AI overview Codename One's macOS build now targets AppKit directly instead of using Mac Catalyst to run an iPad application. The change provides native window handling, rendering, desktop operations, input-method support, and independent monitor scaling while preserving existing project APIs and build targets. ### Source excerpt Codename One's macOS build now targets AppKit directly, with NSWindow, NSMenu, NSTextInputClient, NSScreen, and an independent Metal surface for every window. ## Maintenance release: Godot 3.6.3 DevFeed: [Maintenance release: Godot 3.6.3]() Original publisher: [Read original article]() Author: lawnjelly Published: 2026-08-22T12:00:00Z Content type: release Language: en Sources: [Godot Engine Official]() Topics: [Godot](), [Android](), [iOS](), [Xcode]() Tags: [android](), [android-16](), [ios](), [maintenance](), [release](), [xcode]() ### AI overview Godot 3.6.3 is a maintenance release that updates Android and iOS export requirements, including Android API level 36, an iOS minimum version of 15.0, and removal of 32-bit iOS export. It also includes fixes across networking, audio, build systems, core, rendering, and other areas. ### Source excerpt Godot 3.6.2 has been our recommended stable LTS version of 3.x for a while now, but the time has come to make a new build, primarily due to changes in requirements for Android and iOS. ## Swift Testing explained with code examples DevFeed: [Swift Testing explained with code examples]() Original publisher: [Read original article]() Author: Antoine van der Lee Published: 2026-08-17T08:51:15Z Content type: tutorial Language: en Sources: [SwiftLee]() Topics: [Swift](), [Xcode](), [Code]() Tags: [examples](), [net-conf](), [swift](), [swift-testing](), [testing](), [xcode]() ### AI overview This tutorial introduces Swift Testing, the modern Swift testing framework built around expressive macros such as @Test, #expect, and #require. It explains how Swift Testing replaces XCTest, reduces repetitive boilerplate, defines tests globally, and organizes them with structs, traits, and tags. ### Source excerpt Swift Testing is the modern framework for writing tests in Swift, built around expressive macros like @Test, #expect, and #require. It's the successor to XCTest and the default testing framework for new projects in Xcode. Instead of dozens of assertion methods, you work with a single expressive macro that tells you exactly why a test ... -> The post Swift Testing explained with code examples appeared first on SwiftLee. ## @MainActor in Swift explained with code examples DevFeed: [@MainActor in Swift explained with code examples]() Original publisher: [Read original article]() Author: Antoine van der Lee Published: 2026-08-02T12:04:47Z Content type: tutorial Language: en Sources: [SwiftLee]() Topics: [Swift](), [Concurrency](), [Code](), [Xcode]() Tags: [article](), [code](), [concurrency](), [dispatchqueue](), [examples](), [guide](), [how-to](), [main-thread](), [swift](), [thread](), [xcode]() ### AI overview This tutorial explains how Swift's @MainActor global actor ensures that properties, methods, instances, and closures execute on the main thread. It also covers compiler-enforced main-thread execution, global actor isolation, nonisolated methods, and changes to default actor isolation in Swift 6.2 and Xcode 26. ### Source excerpt @MainActor is a global actor that performs its tasks on the main thread. You can use it to dispatch to the main thread by marking properties, methods, instances, or closures with the attribute. Instead of manually dispatching using DispatchQueue.main.async, you let the compiler enforce main thread execution for you. If you're new to Actors in ... -> The post @MainActor in Swift explained with code examples appeared first on SwiftLee. ## How to free up Xcode disk space safely with an AI Agent DevFeed: [How to free up Xcode disk space safely with an AI Agent]() Original publisher: [Read original article]() Author: Antoine van der Lee Published: 2026-07-27T08:34:16Z Content type: tutorial Language: en Sources: [SwiftLee]() Topics: [Xcode](), [AI Agent](), [Agent Skill](), [Open Source]() Tags: [agent-skill](), [agent-skills](), [ai-agent](), [ai-development](), [derived-data](), [developer-tools](), [disk-space](), [how-to](), [open-source](), [workflow](), [xcode]() ### AI overview This tutorial explains why Xcode can consume substantial disk space, especially when multiple AI agents use separate Git worktrees. It introduces an open-source Xcode Disk Cleanup Agent Skill that searches common storage locations and requires explicit approval before deleting anything. ### Source excerpt Xcode disk space can grow rapidly without you noticing. Especially these days, with multiple agents turning multiple worktrees into silent disk space occupiers. Where I used to only focus on deleting old Simulators every now and then, I'm now also actively managing worktrees and derived data folders. There are great Mac apps and open-source projects ... -> The post How to free up Xcode disk space safely with an AI Agent appeared first on SwiftLee. ## How to Test iOS Apps in Different Time Zones on a Physical iPhone DevFeed: [How to Test iOS Apps in Different Time Zones on a Physical iPhone]() Original publisher: [Read original article]() Author: Antoine van der Lee Published: 2026-07-20T12:27:42Z Content type: tutorial Language: en Sources: [SwiftLee]() Topics: [iOS](), [Xcode](), [USB]() Tags: [how-to](), [ios](), [iphone](), [simulator](), [testing](), [usb](), [validation](), [xcode]() ### AI overview This tutorial explains how to test iOS apps across time zones on a physical iPhone or iPad using RocketSim, Xcode 27, and a USB connection. Simulating a location lets iOS update the device's system time zone, enabling validation of behaviors such as local time changes, focus modes, and driving mode. The workflow requires specific device settings, Developer Mode, and an app launched from Xcode; Xcode 27 is identified as being in beta in the supplied text. ### Source excerpt Testing iOS Time Zones is a typical validation path that's difficult without actually traveling yourself. You can apply all kinds of protocols and mock versions of your app, but having iOS act like it's actually traveling between time zones is a real challenge. Ideally, you'd test apps like travel apps in such a way that ... -> The post How to Test iOS Apps in Different Time Zones on a Physical iPhone appeared first on SwiftLee. ## User Diagnostics Reports: Solving app bugs faster with AI Agents DevFeed: [User Diagnostics Reports: Solving app bugs faster with AI Agents]() Original publisher: [Read original article]() Author: Antoine van der Lee Published: 2026-07-13T07:21:09Z Content type: article Language: en Sources: [SwiftLee]() Topics: [App](), [debugging](), [bug](), [Open Source](), [HTML](), [Xcode](), [Artificial Intelligence]() Tags: [ai-agents](), [bugs](), [debugging](), [diagnostics](), [html](), [open-source](), [optimization](), [xcode]() ### AI overview The article introduces Diagnostics, an open source library for app support and bug investigation. It generates a detailed HTML diagnostics report containing app and OS versions, device and storage details, session information, and system or debug logs. The report can be attached when users submit feedback, reducing back-and-forth and helping developers analyze issues; the article also notes support for agentic development. ### Source excerpt A user diagnostics report that helps you solve bugs and improve user support at the same time. I've been writing apps since 2009, and the Diagnostics repository is an outcome of all that experience. Used by major apps from companies like WeTransfer, it has proven its value time after time. I've seen consistent inefficiency at ... -> The post User Diagnostics Reports: Solving app bugs faster with AI Agents appeared first on SwiftLee. ## Codename One Adds Cross-Platform Printing and Apple Wallet Issuer Provisioning DevFeed: [Codename One Adds Cross-Platform Printing and Apple Wallet Issuer Provisioning]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-06-16T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [API](), [cross-platform](), [iOS](), [Extension]() Tags: [api](), [cross-platform](), [extensions](), [ios](), [native](), [release](), [xcode]() ### AI overview This release adds a cross-platform printing API that sends documents to the native print system and reports whether the handoff was completed, cancelled, or failed. It also adds iOS build hints that generate Apple Wallet issuer-provisioning extensions, while card data is provided through the app and encrypted pass payloads are produced by the issuer backend. ### Source excerpt A new cross-platform printing API hands PDFs and images to the native print dialog on every port, and iOS builds can now generate Apple Wallet issuer-provisioning extensions from build hints with no native code. ## WWDC 2026 Viewing Guide DevFeed: [WWDC 2026 Viewing Guide]() Original publisher: [Read original article]() Author: Keith Harrison Published: 2026-06-15T09:16:45Z Content type: tutorial Language: en Sources: [K. Harrison]() Topics: [Swift](), [SwiftUI](), [Xcode](), [WebAssembly](), [gRPC](), [MLX](), [NumPy](), [Testing]() Tags: [2026](), [apple](), [auto-layout](), [comparison](), [ios](), [ios27](), [macos27](), [objective-c](), [swift](), [swiftui](), [webassembly](), [wwdc](), [xcode]() ### AI overview A guide to planning and watching WWDC 2026 sessions, highlighting platform themes and selected updates in Swift, SwiftUI, Xcode, WebAssembly, gRPC, and MLX. ### Source excerpt My WWDC 2026 viewing guide to help you plan the sessions you want to watch. Where Do I Start? The two big themes for the year are again Liquid Glass and Apple Intelligence. Start by watching the Platforms State of the Union (SOTU) for a summary of what's new this year. If you only have five minutes try the SOTU recap. You don't have to learn everything new today! There are over 100 sessions and a lot of new stuff to learn. You may feel like you're getting left behind. Don't let it overwhelm you. You've got time. Don't burn yourself out trying to keep up. Watching The Sessions I watch the videos using the Apple Developer app. It's available on macOS and iOS. The video player supports from 0.5x to 2x playback, most videos have transcripts and summaries, and allow copying of the onscreen sample code. You can also watch on YouTube. There are a lot of sessions, but many are short (15-20 minutes). There's no padding and Apple's engineers get to the point quickly. Swift Swift 6.4 is here with some quality of life improvements: What's new in Swift Condense long @available attributes with anyAppleOS, @diagnose to control compiler deprecation warnings. Double-colon module selector. Standard Library task cancellation shield, dictionary mapKeyedValues, new FilePath type. XCTest interop with Swift Testing. Subprocess 1.0. New ProgressManager. @C attribute for Swift-C interop. Compile to WebAssembly. New @inline(always) and @specialized attributes. Iterable protocol for noncopyable elements. Build real-time apps and services with gRPC and Swift gRPC Swift package to generate and deploy network code for remote procedure call services. Explore numerical computing in Swift with MLX NumPy-like API. Examples of computing the Mandlebrot set, heat distribution, and curve fitting. SwiftUI Liquid Glass changes and some welcome improvements: What's new in SwiftUI Liquid Glass is now mandatory. Minimal menu icons by default. Resize live previews in Xcode. Prominent tab role. Toolbar visibil ## Announcement: Xcode15 Deprecation in Semaphore DevFeed: [Announcement: Xcode15 Deprecation in Semaphore]() Original publisher: [Read original article]() Author: Pete Miloravac Published: 2026-05-12T10:56:42Z Content type: release Language: en Sources: [Semaphore Engineering]() Topics: [Xcode](), [ci](), [macOS]() Tags: [announcement](), [ci](), [deprecated](), [lifecycle](), [product-news](), [scheduled](), [september-2026](), [switching](), [xcode]() ### AI overview Semaphore announces the deprecation and end of life of its macOS Xcode15 build environments. Brownout periods will precede removal on July 6, 2026, and users are advised to migrate their pipelines to a supported Xcode version, preferably Xcode26. ### Source excerpt MacOS Xcode15 reached the end of its supported lifecycle on Semaphore. To ensure the security, reliability, and maintainability of our platform, we are announcing the deprecation and end of life of MacOS Xcode15 build environments. Semaphore users should consider switching to Xcode26 as Xcode16 is scheduled for deprecation in September 2026. Why We're Deprecating Xcode15 [...] The post Announcement: Xcode15 Deprecation in Semaphore appeared first on Semaphore. ## Flutter 3.44 will make Swift Package Manager the default for iOS and macOS apps DevFeed: [Flutter 3.44 will make Swift Package Manager the default for iOS and macOS apps]() Original publisher: [Read original article]() Author: Jenn Magder Published: 2026-04-30T15:57:00Z Content type: release Language: en Sources: [Flutter - Medium]() Topics: [Flutter](), [Dependency management](), [Swift](), [iOS](), [macOS](), [Package manager](), [Command-line interface](), [Xcode]() Tags: [cli](), [cocoapods](), [dependencies](), [dependency-management](), [flutter](), [flutter-app-development](), [ios](), [macos](), [migration](), [release](), [swift](), [swift-package-manager](), [xcode]() ### AI overview Flutter 3.44 will make Swift Package Manager the default dependency manager for iOS and macOS apps, replacing CocoaPods. The Flutter CLI will migrate projects automatically, temporarily fall back to CocoaPods for unsupported plugins, and allow developers to opt out if SwiftPM causes breaking issues. ### Source excerpt Dash migration! Starting with the next stable Flutter release, 3.44, Swift Package Manager (SwiftPM) replaces CocoaPods as the default dependency manager for iOS and macOS apps. This means no more messing around with Ruby or CocoaPods installations just to get your app running! CocoaPods is officially in maintenance mode, and its registry will permanently become read-only on December 2, 2026. While existing builds will still work, no new versions or pods will be added to the trunk after this date. To ensure that your apps continue receiving dependency updates and to provide access to the Swift package ecosystem, Flutter is transitioning to Apple's supported dependency management solution: Swift Package Manager. If you've already migrated your plugin(s) to use SwiftPM, read the "Plugin developers" section below for new migration requirements. Here is how to manage the transition. App developers For app developers, the Flutter CLI handles the migration. When you run or build your iOS or macOS app, the CLI automatically updates your Xcode project to use Swift Package Manager. Check out the Flutter migration docs for app developers for more details. If your app relies on plugins that haven't adopted Swift Package Manager yet, Flutter will print a warning listing exactly which of your dependencies are unsupported. Flutter will temporarily fall back to CocoaPods for plugins that have not adopted Swift packages yet. Because CocoaPods support will eventually be removed entirely, if a plugin hasn't updated and breaks your build, file an issue with the dependency's maintainer to request Swift package support or find an alternative package. We know that migrations can sometimes hit a snag. If SwiftPM causes a breaking issue, you can temporarily disable it for your project. Open your pubspec.yaml file, navigate to the flutter section, and set enable-swift-package-manager to false under the config block: flutter: config: enable-swift-package-manager: false If you opt out, please ## Xcode 26 Migration, UIScene Rollout, Initializr Localization Bundles, and More DevFeed: [Xcode 26 Migration, UIScene Rollout, Initializr Localization Bundles, and More]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-03-07T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Xcode](), [iOS](), [Localization (l10n)](), [Internationalization (i18n)](), [migration](), [Android](), [Documentation]() Tags: [adaptive](), [android](), [developer-guide](), [ios](), [migration](), [tooling](), [updates](), [xcode]() ### AI overview A Codename One update reports a staged Xcode 26 migration, initial UIScene support for testing, and Initializr-generated localization resource bundles. It also covers localization workflow improvements, Android adaptive icons, iOS notification replacement fixes, and UI and resource tooling updates. ### Source excerpt We started the Xcode 26 migration rollout, Initializr now generates localization resource bundles, and there are several useful platform updates you should know about. ## XcodeGen and the quest to modularize the Wealthfront iOS app DevFeed: [XcodeGen and the quest to modularize the Wealthfront iOS app]() Original publisher: [Read original article]() Author: Matthew Bommer Published: 2026-03-02T17:56:41Z Content type: tutorial Language: en Sources: [Wealthfront]() Topics: [XcodeGen](), [iOS](), [Swift](), [Xcode](), [Command-line interface](), [configuration](), [Development]() Tags: [automation](), [careers](), [declarative](), [infrastructure](), [ios](), [modularization](), [swift](), [wealthfront-engineering](), [xcode](), [xcodegen](), [yaml]() ### AI overview Wealthfront describes adopting XcodeGen to generate Xcode project files from declarative YAML, reducing project-file merge conflicts and making build configuration more reviewable. The team also plans to use it to support modularizing its large iOS application into independently compilable modules. ### Source excerpt Every iOS application starts as a monolith. Xcode's default project structure places all source files, resources, and build configuration into a single module (or target, for all the iOS devs reading this). For small apps, this works fine. For a 10+ year old financial application with roughly 2,000 Swift and a handful of Objective-C files,... Read more ## Unlocking the Codex harness: how we built the App Server DevFeed: [Unlocking the Codex harness: how we built the App Server]() Original publisher: [Read original article]() Published: 2026-02-04T13:00:00Z Content type: article Language: en Sources: [OpenAI News]() Topics: [codex](), [API](), [Remote Procedure Call (RPC)](), [JSON](), [ide](), [Command-line interface](), [VS Code Extension](), [vs-code](), [Xcode](), [MCP](), [MCP Server](), [site-reliability-engineering]() Tags: [api](), [cli](), [codex](), [engineering](), [ide](), [json](), [mcp](), [openai](), [rpc](), [software-development](), [vs-code](), [xcode]() ### AI overview OpenAI explains how the Codex App Server evolved into a bidirectional JSON-RPC API for embedding the shared Codex harness across products and partner integrations. The article covers its architecture, protocol, streaming progress, tool use, approvals, diffs, and integration with Codex surfaces such as the CLI, IDE extension, web app, and macOS app. ### Source excerpt Learn how to embed the Codex agent using the Codex App Server, a bidirectional JSON-RPC API powering streaming progress, tool use, approvals, and diffs. ## Discovering iOS Memory Leaks IV: Detecting via Unit Tests DevFeed: [Discovering iOS Memory Leaks IV: Detecting via Unit Tests]() Original publisher: [Read original article]() Author: Amanjeet Singh Gurtatta Published: 2026-01-07T01:46:06Z Content type: tutorial Language: en Sources: [Amanjeet Singh]() Topics: [iOS](), [Memory Leaks](), [unit tests](), [Xcode](), [macOS]() Tags: [ios](), [macos](), [memory](), [memory-leak](), [memory-leaks](), [tests](), [unit-tests](), [xcode]() ### AI overview This article explores detecting real iOS memory leaks with unit tests instead of UI tests. It describes running the macOS leaks tool against the Firefox process during unit-test teardown in the iOS simulator to shorten the feedback cycle and broaden coverage. ### Source excerpt Using unit tests and macOS leaks tool to catch real iOS memory leaks. ## LightBuddy: A Mac Display Lighting Prototype Superseded by macOS Edge Light DevFeed: [LightBuddy: A Mac Display Lighting Prototype Superseded by macOS Edge Light]() Original publisher: [Read original article]() Published: 2025-12-16T18:00:00Z Content type: opinion Language: en Sources: [Rambo Codes]() Topics: [GUI](), [macOS](), [Xcode](), [coding]() Tags: [apple](), [engineering](), [gui](), [macos](), [xcode]() ### AI overview Gui Rambo recounts creating LightBuddy, a Mac display-based lighting prototype for video calls, and how Apple later integrated a similar Edge Light feature into macOS. He reflects on how shipping the app first might have felt to be overshadowed by Apple. ### Source excerpt Gui Rambo writes about his coding and reverse engineering adventures. ## Why Legacy Xcode Projects May Benefit from Replacing Groups with Folders DevFeed: [Why Legacy Xcode Projects May Benefit from Replacing Groups with Folders]() Original publisher: [Read original article]() Author: Elye - A Dev By Grace Published: 2025-12-07T13:07:57Z Content type: article Language: en Sources: [Mobile App Development Publication - Medium]() Topics: [Xcode](), [legacy](), [iOS]() Tags: [apple](), [coding](), [ios](), [ios-development](), [legacy](), [mobile-app-development](), [structure](), [xcode](), [xcode-16]() ### AI overview This article explains how Xcode project file organization differs between Groups and Folders. It notes that projects created before Xcode 16 use Groups by default, while new projects use Folders, and introduces reasons for considering Folders in legacy projects. ### Source excerpt Seven Reasons Folders Are Better -- Especially for Legacy Projects Continue reading on Mobile App Development Publication " ## Using Stencil Templates for Code Generation in iOS Development DevFeed: [Using Stencil Templates for Code Generation in iOS Development]() Original publisher: [Read original article]() Author: CleverDevilV (hh.ru) Published: 2025-12-04T09:45:15Z Content type: tutorial Language: ru Sources: [HeadHunter RU]() Topics: [iOS](), [Swift](), [Figma](), [Kotlin](), [JSON](), [Sublime Text](), [Visual Studio Code](), [Xcode]() Tags: [figma](), [filter](), [ios](), [ios-92ecabba3495](), [join](), [kotlin](), [split](), [swift](), [tag-3383f6fe7741](), [tag-e95ee8b94dca](), [text](), [vscode](), [xcode]() ### AI overview A tutorial introducing Stencil, a template language used to automate code and file generation in iOS development. It explains the language's syntax, data structures, filters, and tags, and describes applications involving Swift, Figma-exported design-system data, analytics events, Kotlin files, JSON input, and editor support. ### Source excerpt Что любят все разработчики? Конечно, автоматизировать рутинные повторяющиеся действия! Я расскажу, как в этом может помочь язык Stencil, широко известный в узких кругах iOS-разработчиков. Читать далее ## Format Swift with a Git Commit Hook DevFeed: [Format Swift with a Git Commit Hook]() Original publisher: [Read original article]() Author: Keith Harrison Published: 2025-11-24T10:29:58Z Content type: tutorial Language: en Sources: [K. Harrison]() Topics: [Swift](), [Git](), [configuration](), [Development](), [Code]() Tags: [auto-layout](), [bash](), [configuration](), [developer](), [development](), [git](), [git-commit](), [ios](), [objective-c](), [swift](), [wwdc](), [xcode](), [xcode-16]() ### AI overview This tutorial explains how to format Swift code automatically with swift-format and a Git pre-commit hook. It covers Xcode 16's bundled formatter, .swift-format configuration files, a Bash hook that formats staged Swift files, hook installation, and bypassing the hook when needed. ### Source excerpt How do you automatically format your Swift code every time you commit it to your Git repository? Swift Format There are several Swift formatting tools. Xcode 16 shipped with swift-format included in the toolchain: $ xcrun --find swift-format /Applications/Xcode.app/Contents/Developer/Toolchains/ XcodeDefault.xctoolchain/usr/bin/swift-format To run the formatter: $ swift format MyFile.swift Note: This runs the swift-format bundled with the active Xcode development directory (beta or release). Configuring swift-format The Xcode settings let you configure various formatting options including indentation but I prefer to use an external configuration file for swift-format. By default, swift-format looks for a configuration file named .swift-format in the same directory as the files you are formatting. If there isn't one it looks in each successive parent directory. If it doesn't find a configuration file it uses a default configuration. You can dump the default configuration to get started: $ swift format dump-configuration > swift-format Modify the configuration file to meet your own code style: { "fileScopedDeclarationPrivacy" : { "accessLevel" : "private" }, "indentConditionalCompilationBlocks" : true, "indentSwitchCaseLabels" : false, "indentation" : { ... I keep my default configuration file in my base Developer directory: $ mv swift-format ~\Developer\.swift-format When needed, I can override the defaults by placing a modified configuration file in the project-specific root directory. Note: Don't forget to prefix the configuration file with a . Git Commit Hooks Git Hooks are a way to run custom scripts when different Git actions occur. A pre-commit hook runs when you commit changes to a repository. Here's the pre-commit script I'm using to run swift-format: #!/bin/bash GIT=/usr/bin/git GREP=/usr/bin/grep SWIFT=/usr/bin/swift # Staged (cached) added/copied/modified/renamed files FILES=$($GIT diff --cached --name-only --diff-filter=ACMR | $GREP '\.swift$') # Exit ear ## SwiftUI Custom URL Schemes DevFeed: [SwiftUI Custom URL Schemes]() Original publisher: [Read original article]() Author: Keith Harrison Published: 2025-10-27T11:26:47Z Content type: tutorial Language: en Sources: [K. Harrison]() Topics: [SwiftUI](), [WebView](), [iOS](), [WebKit](), [App]() Tags: [async](), [auto-layout](), [configuration](), [how-to](), [ios](), [ios-26](), [objective-c](), [protocol](), [scheme](), [swift](), [swiftui](), [web](), [webview](), [wwdc](), [xcode]() ### AI overview This tutorial explains how to create a custom URL scheme handler for SwiftUI WebViews in iOS 26. It covers implementing URLSchemeHandler, loading local HTML resources from an app bundle, registering the handler in a WebPage configuration, and displaying the page in a WebView. ### Source excerpt Create a custom URL scheme handler for SwiftUI WebViews. Custom URL schemes Apple introduced both WebView and WebPage SwiftUI views in iOS 26. These provide similar WebKit functionality to the UIKit WKWebView APIs. This includes being able to register custom URL schemes to load local resources. Suppose I have an App that loads quotations from the local App bundle. My URL scheme uses the format: quotes://001.html There are a few steps to support a custom URL scheme: Create a custom URL scheme handler that knows how to load the local resources. Register the scheme handler in a WebPage configuration. Have the WebView load and display the web page. Let's look at each of those steps. URLSchemeHandler (iOS 26) The URLSchemeHandler is a protocol with a reply method to return an async sequence of results. The AsyncSequence expects us to either yield a URLResponse and some data or throw an error. struct QuoteSchemeHandler: URLSchemeHandler { static let scheme = "quotes" func reply(for request: URLRequest) -> some AsyncSequence< URLSchemeTaskResult, any Error > { AsyncThrowingStream { continuation in ... } } } The reply method provides us with the URLRequest. I start by extracting the URL and checking it matches our quotes scheme: guard let url = request.url else { continuation.finish(throwing: QuoteError.missingURL) return } guard url.scheme == QuoteSchemeHandler.scheme else { continuation.finish(throwing: QuoteError.invalidScheme) return } To construct the URL response I need the mime type and length of the data. I first extract the filename from the URL, determine the mime type from the file extension, and then load the data: do { let file = try filename(for: url) let mimeType = try mimeType(for: file) let data = try Data(contentsOf: file) I can then build the URLResponse: let response = URLResponse( url: url, mimeType: mimeType, expectedContentLength: data.count, textEncodingName: "utf-8" ) If nothing has gone wrong I then add the response and the data to the AsyncSequenc [Next page]()