No official release notes exist for Xcode 27 or iOS 27 Beta, as these have not been announced or released as of my knowledge cutoff. This content cannot be accurately translated or verified.
This page has been translated by machine translation. View original
When maintaining iOS apps professionally, this time of year is always nerve-wracking. The beta release notes published alongside WWDC can contain breaking changes that affect the behavior of existing apps.
On June 9, 2026 (Japan time), Xcode 27 Beta and iOS & iPadOS 27 Beta were released alongside WWDC2026. This year is no exception, with several changes that could cause apps to fail to launch or display incorrectly if left unaddressed.
This article summarizes the key changes iOS developers should be aware of, based on official documentation. I'll also be checking the answers against the breaking changes prediction article I wrote back in March.
Release Overview
| Item | Details |
|---|---|
| Bundled Language | Swift 6.4 |
| Supported SDKs | iOS 27 / iPadOS 27 / tvOS 27 / macOS 27 / visionOS 27 |
| System Requirements | macOS Tahoe 26.4 or later |
| Architecture | Apple silicon only (Intel Mac not supported) |
This had long been rumored, but Intel Macs have finally been dropped from the support list.
Checking the Answers on Previously Announced Changes
Back in March, I wrote an article titled "Things to prepare now for breaking changes in iOS 27 / Xcode 27." Several changes had been announced at WWDC25 as "deprecated in the next major update," and I urged early adoption.
At the time, "next major update" referred to iOS 27 / Xcode 27 — let me go through those and see how they turned out.
UIKit Scene-Based Lifecycle Now Mandatory
This is a breaking change with significant impact on existing apps. Apps built with the iOS 27 SDK will fail to launch if they don't use the scene-based lifecycle (UIScene).
The UIKit > Deprecations section of the iOS & iPadOS 27 Beta Release Notes states the following:
Apps built with the latest SDK must adopt the scene-based life cycle or they fail to launch.
It explicitly says "fail to launch." This turned out exactly as announced. Details on the migration are covered later.
Liquid Glass Made Mandatory (UIDesignRequiresCompatibility Disabled)
The official documentation for UIDesignRequiresCompatibility states the following:
The system ignores this key when you build for iOS 27 or later, iPadOS 27 or later, Mac Catalyst 27 or later, macOS 27 or later, or tvOS 27 or later.
In apps built with the iOS 27 SDK, this key is completely ignored. This means that even setting it to YES will no longer let you bypass Liquid Glass — exactly as previewed at WWDC25 with the announcement of "removal in the next major release."
iOS 27 also adds a transparency slider for Liquid Glass (allowing users to adjust the glass effect intensity in steps), making it a "improve while mandating" approach. For developers, the key point is that the escape route is gone.
❌ End of Support for iPhone 11 (A13)
Support for iPhone 11 has been confirmed to continue. Despite enhanced AI features, Apple has indicated a policy of prioritizing compatibility with existing devices, and iOS 27 supports the same devices as iOS 26 (iPhone 11 and later). No cuts this year.
Overall, the result was: "Changes officially announced by Apple (UIScene, Liquid Glass) were largely spot-on, while the rumor-level device cut predictions were wrong."
Headline Features
UIScene Lifecycle Fully Mandatory
This is the biggest topic this time. As of iOS 26, apps could still function with just UIApplicationDelegate, but building with the iOS 27 SDK will cause an assertion crash at launch. The migration guide is TN3187.
Apps that haven't yet added UIApplicationSceneManifest or migrated to SceneDelegate should check this as soon as possible. However, since this only applies when built targeting the new SDK, apps still built against the iOS 26 SDK won't be affected. You'll need to comply before the App Store SDK requirement deadline (predicted to be around April 2027, based on past patterns).
For points to watch out for during migration, refer to "Things to prepare now for breaking changes in iOS 27 / Xcode 27."
TrustInsights Framework (New)
A new security-related framework called TrustInsights has been added. A rough translation of the official description:
Evaluates whether a transaction may involve coercive activity, while preserving privacy.
In short, this is a mechanism that lets the system evaluate whether a user is being forced to perform an action through fraud or threats. The intended users are apps like banking, payments, and crypto wallets, with the use case being to require additional authentication when a high-risk rating is returned.
The evaluation is performed by the system, and raw signals are not passed to the app. We look forward to seeing reports of real-world use cases.
Other Features (Brief Mentions)
AsyncImage: HTTP Cache Support
AsyncImage now respects standard HTTP cache headers. It's also possible to specify URLRequest cachePolicy and configure a custom URLSession via View.asyncImageURLSession(_:). A small but welcome improvement.
TextKit: NSTextTable Now Available in UIKit
NSTextTable and its related types are now available to UIKit clients starting with iOS 27.
SwiftUI: New Document API
The ReadableDocument / WritableDocument protocols have been added. They support asynchronous reading and writing, progress reporting (Subprogress), and direct URL access. For new apps, the new API is recommended over ReferenceFileDocument.
TabView Selection Behavior Change (Breaking)
When built with the iOS 27 SDK, specifying a hidden or disabled tab via selection may cause a crash. Apps that dynamically add or remove tabs, or that use conditional display, should review their selection logic.
In apps built with the iOS 27.0 and iPadOS 27.0 SDKs, a TabView enforces that its selection is set to a visible tab. TabView might crash when its selection is set to a hidden or otherwise unavailable tab. (164516837)
Other Changes (Quick Summary)
Xcode Side
- Interface Builder's
toolchainmode, which enables compilation without a simulator, is now enabled by default. This helps speed up CI environments. - Flaky tests can now be run repeatedly with
swift test --repeat-until fail - Swift Concurrency visualization in Instruments has been greatly enhanced (new Swift Executors instrument added, Task Collection track added)
- The first LLDB
pocommand in projects using bridging headers is now significantly faster - The ld64 linker has been removed, and the
-ld_classicoption has also been discontinued - On Demand Resources has been deprecated. Migrate to Background Assets.
iOS / SDK Side
- Foundation Models now supports image input (Attachment) and Private Cloud Compute (server models), and the
LanguageModelprotocol allows third-party cloud models to be handled through a unified API - A new framework called Core AI has been added for running custom models on-device, and it is also integrated with the Foundation Models API
- TLS 1.2 minimum requirements are now enforced for MDM, profile distribution, software updates, and more. Check your managed environments.
MXMetricManager/MXMetricManagerSubscriberare deprecated, requiring migration to the AsyncStream-basedMetricManager.terminationCategoryhas been added toCrashDiagnostic, andMemoryExceptionDiagnostic(for terminations due to exceeding memory limits) has also been newly added.- A
reorderableAPI has been added that allows drag-to-reorder in views other thanList(such asLazyVStackandLazyVGrid). Also newly supported on watchOS 27.0. - New sample types for menopausal status and postmenopausal bleeding have been added to HealthKit
- Metal 4.1 is now supported
New Frameworks
- Now Playing: Unified playback interface for Lock Screen, Control Center, and CarPlay
MusicUnderstanding: New framework for analyzing music tempo, beat, key, instrument activity, and moreTrustInsights: Helps detect social engineering threats (for security-focused apps)CrashReportExtension: Enables implementation of custom crash reports running out-of-processEvaluations: New framework for evaluating and validating the behavior of AI features
Points of Interest
Privacy Implications of TrustInsights
As mentioned above, this is a compelling feature for banking and payment apps, but what signals the system collects to perform risk assessments is unclear as of beta 1. I'm also curious whether Privacy Manifest entries are required, and whether an Entitlement application is needed. I'd like to keep an eye on this as more information emerges with subsequent betas.
Multimodal Support in Foundation Models
Up until now, Foundation Models only returned text in response to text input, which meant significant functional limitations compared to cloud LLMs. With the addition of the Attachment API that allows images to be used as input, the expressive range of apps looks set to expand dramatically — personally, this is the change I'm most interested in.
Detailed documentation, "Analyzing Images with Multimodal Prompting," has also been provided. I'd like to dive deeper into this once the beta stabilizes.
However, as of beta 1, many Known Issues have been reported, so it's not yet clear how usable it is in practice. I'll be paying close attention to how stability improves as the beta progresses.
Impact of Xcode 27 Becoming Apple Silicon Only
Xcode 27 does not run on Intel Macs. This was announced in advance, but I'm concerned about the impact on CI/CD environments. You'll need to check the update status for build stacks like Bitrise and Xcode Cloud.
In particular, since Bitrise still has some Intel-based stacks remaining, upgrading to Xcode 27 will be paired with a migration to Apple Silicon-only machines — but basically, you should be fine using a dedicated stack like osx-xcode-27.0.x (as of June 11, 2026, only osx-xcode-27.0.x-edge is available).
Potential Crashes in Swift Charts
When the deployment target is below iOS 27.0, if conditions inside a Chart closure may cause runtime crashes. This can be worked around by extracting the content into a function using @ChartContentBuilder. This is easy to overlook, so be careful.
Summary
From the perspective of a developer maintaining iOS apps professionally, the biggest breaking changes this time are the full mandating of the UIScene lifecycle and the disabling of UIDesignRequiresCompatibility. Apps that haven't addressed these will fail to launch or display incorrectly when built with the iOS 27 SDK.
As for the answer-checking results, it turned out that "changes officially announced by Apple were implemented largely as announced, while rumor-level predictions were wrong."
On the features side, I'm personally keeping an eye on TrustInsights, a new security framework. It's a compelling feature for banking and payment apps, and I'd like to write a dedicated article once the API details are available.
As the beta progresses through stages 2 through 4, more information will emerge, and I'll continue following it closely.
Reference Links
- Xcode 27 Release Notes
- iOS & iPadOS 27 Beta Release Notes
- What's New - WWDC2026
- TN3187: Migrating to the UIKit scene-based life cycle
- iOS 27 / Xcode 27 Breaking Changes Preview (Author's Prediction Article)
Job Openings: Classmethod is Hiring iOS Engineers
The Starbucks Digital Technology division is looking for engineers who can develop iOS apps. We'd love to have you join us — sharing and discussing new Xcode and iOS features together in the misc-ios channel!
We're also hiring iOS/Android engineers in other areas. Let's talk about mobile app development together!