Xcode 26.4 Beta 3 Drops With Swift Testing, Instruments, and Localization Improvements

Essential Points

• Xcode 26.4 beta 3 (build 17E5179g) released March 9, 2026, alongside iOS, macOS, tvOS, watchOS, and visionOS 26.4 beta 4
• Swift Testing gains image attachment support for CGImage, NSImage, UIImage, and CIImage types
• Instruments adds a Run Comparison feature and new Top Functions mode for faster performance profiling
• String Catalog editor now supports cut, copy, paste, duplicate, language removal, and pre-fill from existing translations

Apple shipped Xcode 26.4 beta 3 on March 9, 2026, targeting iOS, macOS, tvOS, watchOS, and visionOS 26.4 compatibility testing. Unlike Xcode 26.3, which introduced agentic coding with Claude Agent and OpenAI Codex via MCP, version 26.4 focuses entirely on workflow refinement. The changes are spread across three core areas: Swift Testing, Instruments, and localization.

Swift Testing Gains Visual Failure Output

The most practical upgrade for iOS and macOS developers is Swift Testing image attachment support.

You can now attach the following image types directly to test reports:

• CGImage
• NSImage
• UIImage
• CIImage

When a render or Vision framework test fails, you see the actual visual output rather than a string of coordinates. This removes a layer of guesswork that previously required manually inspecting derived data.

Swift Testing in Xcode 26.4 also adds severity specification when recording an issue. Teams using Swift Testing in CI pipelines can now distinguish between critical failures and lower-severity flags, preventing minor issues from blocking builds unnecessarily.

There is also a fix for error handling during attachment saving. If an error occurs while Xcode saves an attachment from either XCTest or Swift Testing into a test report, Xcode now reports that error as a runtime issue immediately rather than failing silently.

Also Read Apple Re-Released iOS & iPadOS 26.4 Beta 3 v.2 With a New Build. Here Is What Actually Changed.

Instruments Gets Run Comparison and Top Functions

Xcode 26.4 ships two high-value additions to Instruments that directly address time spent diagnosing performance regressions.

The new Run Comparison feature lets you compare call trees between runs using View, then Detail Area, then Compare With, or the swap button in the jump bar. After selecting a reference run, the comparison view shows which functions took more or less time. Call tree filtering, including “Charge to callers,” lets you isolate the functions that changed between runs.

Top Functions is a new top-level mode inside the Call Tree view. Select the rightmost button in the Call Tree navigation bar to access it. It surfaces the most expensive functions in a trace regardless of where they are called from, removing the need to manually trace call chains to find bottlenecks.

A new “Hide Inlined Functions” option in the Call Tree menu hides inlined functions and charges their samples to the calling function. This produces cleaner call trees in release builds where inlining is aggressive.

String Catalog Localization Is Now Fully Editable

String Catalogs arrived in Xcode 15 but the editor has lacked basic editing operations since launch. Xcode 26.4 closes four gaps at once.

Language removal: Remove a language from the String Catalog editor with the option to remove it from just that catalog or from the entire project.

Pre-fill translations: When adding a new supported language in Project Settings, Xcode can now pre-populate String Catalogs with translations from an existing language. This accelerates regional variant creation and external vendor handoffs.

Cut, copy, paste, and duplicate: String Catalog editing now supports full clipboard operations on strings within the same catalog file or between different catalogs. When pasting, you choose between adding the string as a new key with all its translations, or applying translations onto an existing key.

Static library string export: Strings extracted from code inside static libraries and executables are now marked as translate=”no” since those targets do not have resource bundles to store strings. This prevents localization vendors from translating strings that can never ship.

BUILD_ONLY_KNOWN_LOCALIZATIONS setting: A new build setting lets teams limit built localized content to the localizations listed in the Project Editor. Excluded languages display less prominently in String Catalogs.

How Xcode 26.4 Compares to Xcode 26.3

Companion OS Releases on March 9, 2026

Xcode 26.4 beta 3 shipped alongside the following beta 4 releases on March 9, 2026:

• iOS 26.4 beta 4 (23E5234a)
• iPadOS 26.4 beta 4 (23E5234a)
• macOS Tahoe 26.4 beta 4 (25E5233c)
• tvOS 26.4 beta 4 (23L5234a)
• watchOS 26.4 beta 4 (23T5236a)
• visionOS 26.4 beta 4 (23O5235a)

Developers targeting any of these platforms should build against the Xcode 26.4 beta 3 SDKs before the stable release window.

Considerations Before Installing

Xcode 26.4 beta 3 is not suitable for production builds. Apple recommends beta installs specifically for app compatibility testing against upcoming OS releases, not for shipping code. Keep Xcode 26.3 stable (17C529, released February 26, 2026) as your primary production IDE and run 26.4 beta in a separate environment.

Who Should Install Xcode 26.4 Beta 3 Now

Install now if any of these apply:

• Your app uses Swift Testing and you need visual failure output for image-rendering or Vision framework tests
• You profile app performance regularly in Instruments and want run-over-run regression detection
• You maintain a localized app and manage String Catalogs across multiple languages
• You plan to ship for any of the 26.4 OS targets and need early SDK compatibility data

Wait for stable release if your project has a deadline within the next 30 days and your test suite passes cleanly on Xcode 26.3.

Also Read watchOS 26.4 Beta 3 v.2 Lands With a Sleep Metric That Changes How You Track Rest

Frequently Asked Questions (FAQs)