UIKit's Scene Mandate: What Fails to Launch on iOS 27

Apple’s migration documentation states the hardest requirement of the iOS 27 cycle in one sentence: “Beginning in iOS 27, iPadOS 27, Mac Catalyst 27, tvOS 27, and visionOS 27, apps built with the latest SDK must adopt the scene-based life cycle or they fail to launch.”¹ Not deprecated, not warned, not slower: fail to launch. Session 278 says it just as plainly: “UIScene lifecycle is now required when building with the latest SDKs. Without it, your application will no longer launch.”² Every UIKit app still running on the old app-delegate life cycle has until it builds against the iOS 27 SDK to migrate, and the warning phase is already years deep.

The requirement, stated at 2:36 in session 278.

TL;DR

• Apps built with the iOS 27 SDK must use the UIKit scene-based life cycle or they fail to launch, across iOS, iPadOS, Mac Catalyst, tvOS, and visionOS 27.¹ Existing binaries built with older SDKs keep working; the wall is the SDK you build against.
• The escalation was staged: UIKit started logging a migration message back in iOS 18.4, and the message changed in iOS 26. iOS 27 is where the log becomes a launch failure.¹
• You need to migrate if either condition holds: your Info.plist has no UIApplicationSceneManifest key with a configuration, or your app delegate doesn’t implement the scene-configuration method.¹
• The minimal migration is small: a scene manifest entry in the property list, or the delegate method for dynamic configurations. Supporting multiple scenes stays optional.¹
• Xcode 27 ships an app modernization agent skill that converts apps to the scene life cycle, rewrites main-screen and orientation checks, asks clarifying questions on complex tasks, and leaves comments for work it can’t finish in one session.²

A mandate, not a deprecation

The 27 cycle has a pattern of pruning APIs one release after their replacements mature: ImageCreator stops working in iOS 27, and MXMetricManager carries a 27.0 deprecation the same week its replacement shipped. The scene requirement is the most consequential entry in that pattern because it gates the entire app, not a feature. An app that never touches Image Playground loses nothing this fall. An app that ignores the scene life cycle stops launching the day it builds with the new SDK.

The timeline shows how much runway Apple burned before enforcing. Starting in iOS 18.4, iPadOS 18.4, Mac Catalyst 18.4, tvOS 18.4, and visionOS 2.4, UIKit logged a message for apps that hadn’t migrated, and in the 26 releases the message changed.¹ Two releases of warnings, then the floor drops. The conceptual groundwork is even older: the session reaches back to WWDC 2014 for Bruce Nilo’s framing that “a device rotation is only an animated bounds change,” and notes that with resizable iPad windows and resizable iPhone apps, “today this insight is more relevant than ever.”²

One boundary worth stating precisely: the requirement binds apps “built with the latest SDK.”¹ Shipping binaries built against iOS 26 or earlier SDKs keep launching. The moment you rebuild with Xcode 27’s SDKs to pick up anything new, the scene life cycle comes with it.

Do you actually need to migrate?

The documentation gives a two-condition test. Migrate if the UIApplicationSceneManifest key is missing from your information property list (or has no specified configurations), or if your app delegate doesn’t implement the scene-configuration method.¹ Most apps started after 2019 pass already; Xcode’s templates have generated scene-based projects since then. The apps caught by the mandate are the long-lived ones whose AppDelegate still owns the window.

The minimal fix is one of two routes. The static route adds a UIApplicationSceneManifest key with a scene configuration to the property list, reachable through the target’s General settings under “Scene manifest” in Deployment Info.¹ The dynamic route implements the scene-configuration delegate method instead, for apps that customize scenes based on user activities or handle different scene roles; the doc’s example uses the session’s role property to determine which scene to create.¹ Apps that load the root view controller from a storyboard include the storyboard name in the scene manifest, and the system configures the window scene and root view controller automatically.¹

What the mandate does not require is multiple scenes. The doc is explicit that multiple-scene support stays optional and may require restructuring your data model to be scene-specific; it tells you to consider whether the user experience benefits before enabling it.¹ Migrating means moving life-cycle events from the app level to the scene level, where UIApplicationDelegate keeps process-level events and the scene delegate takes UI-specific ones.¹ One detail that trips up configuration: specify UIWindowScene objects rather than plain UIScene objects, and CarPlay scenes use their own template-application scene type.¹

Why now: everything resizes

The mandate lands in the same release that makes resizability universal, and session 278 presents them as one story. In iOS and macOS 27, iPhone Mirroring windows on the Mac resize freely, and an iPhone-only app running on iPad becomes “fully resizable like any other iPad app.”² The scene life cycle is, in the session’s words, “the basis for any adaptive app”: the prerequisite for everything else the session asks you to fix.²

The fix list is a purge of screen-centric assumptions. References to the main screen return incorrect information once your scene lives on a different display, so the session says to access the screen dynamically through the window’s window scene, or better, remove screen references entirely: screen scale becomes the trait collection’s displayScale, and screen bounds become the window scene’s effective geometry or simply the size of the surrounding view.² Automatic trait tracking softens the migration: the system tracks which trait properties are read inside layout and drawing methods like layoutSubviews and calls them again when a tracked trait changes.²

Two long-standing signals lose their layout meaning outright. The user-interface idiom “is no longer meaningful for any kind of layout decision,” because an iPhone app on iPad runs fully resizable while still reporting the phone idiom; and supported interface orientation becomes a preference the system ignores in resizable environments, with iPhone Mirroring always reporting portrait regardless of the window’s aspect ratio.² The replacement for both is size classes. Games get an accommodation instead of an exemption: UIRequiresFullscreen is honored on iPhone in resizable environments starting in iOS 27, but its behavior changes to discrete resizing, transitioning the scene to a matching screen configuration on each resize so the game renders at full quality in the available space.²

Testing the whole matrix got cheaper in the same cycle: Device Hub and Xcode Previews gain an “enter resize mode” that drags device edges freely, with the session advising real-device checks on iPhone Mirroring and iPad afterward.²

The migration has an agent skill

The session closes by acknowledging the size of the ask and pointing at Xcode 27’s answer: a new app modernization skill with “a deep understanding of the adaptivity tasks” the session outlines.² Asked to make an app more adaptable, the agent converts main-screen calls to trait-collection or scene-bounds checks with invalidation logic where needed, replaces interface-orientation checks with size classes, and “will even convert your app to use scene lifecycle.”² For complex tasks it asks clarifying questions, and for work too large for one session it leaves comments marking what remains.²

The distribution story matches the rest of Apple’s skills push this WWDC: xcrun agent skills export produces markdown files you can import into other tools, the same mechanism covered in Xcode 27’s agent skills export.² A migration enforced by the SDK, paired with a skill that performs the migration, is the clearest expression yet of how Apple expects breaking changes to be absorbed in the agent era: the platform raises the floor, and the tooling carries you over it.

FAQ

Will my existing app stop working on iOS 27?

Not from this requirement alone. The mandate applies to apps “built with the latest SDK.”¹ Binaries already shipped with older SDKs keep launching on iOS 27. The failure occurs when you rebuild against the iOS 27 SDK without the scene-based life cycle in place.

How do I know if my app is affected?

Check two things.¹ If your Info.plist lacks a UIApplicationSceneManifest key with a configuration, and your app delegate doesn’t implement the scene-configuration method, you’re on the app-delegate life cycle and the app fails to launch when built with the iOS 27 SDK. UIKit has logged a migration message for affected apps since iOS 18.4.¹

Does this force me to support multiple windows?

No. Multiple-scene support stays optional, and Apple’s documentation advises weighing whether your user experience benefits before enabling it, since it may require making your data model scene-specific.¹ The mandate only requires the scene-based life cycle itself: life-cycle events handled per scene rather than globally.

Can an agent do the migration?

Xcode 27 ships an app modernization skill that the session says can convert an app to the scene life cycle, rewrite main-screen references, and replace orientation checks with size classes, asking clarifying questions where the change is ambiguous and leaving comments for unfinished work.² It exports to other tools via xcrun agent skills export.² Treat its output like any agent-written migration: review the diff, especially around state restoration and window setup.

The mandate completes a theme this cycle: Apple enforcing migrations at the 27 boundary rather than suggesting them, after ImageCreator’s discontinuation showed the same staged escalation on a smaller surface. The agent-skill answer connects to the broader skills arc in Xcode 27 Ships Agent Skills You Can Export Anywhere. The full series hub is the Apple Ecosystem Series.

References