BestPaid guides · iOS · App Store

App Store from April 2027: Xcode 27, the iOS 27 SDK, iOS 15 and UIScene

From April 2027, App Store Connect accepts iOS and iPadOS apps only if built with the iOS 27 SDK or later (Xcode 27 or later) and targeting iOS 15 or later. Those builds must use UIKit's scene life cycle or they fail to launch. Below: the rules in force, moving an AppDelegate-only app to UIScene, and what Flutter, React Native, Unity, .NET MAUI and Xamarin apps need.

Sources: Apple's Upcoming requirements and Submitting pages, news posts of September 9 and October 5, 2026, screenshot specifications, Transitioning to the UIKit scene-based life cycle, TN3187, Xcode 27 and iOS 27 release notes, reference pages on connection options, launch options, quick actions, notification delegates, state restoration, scene state and UIDesignRequiresCompatibility, and its iPhone Duo guide; Flutter's UIScene adoption guide; the React Native 0.88 and Expo SDK 58 release posts; Unity's UIScene announcement and 2022.3.72f1 release notes; Microsoft's .NET MAUI and Xcode 27 post and Xamarin support policy. Checked on November 21, 2026. This page is our own summary; follow the vendor's documentation for every detail.

What applies now and what changes in April 2027

WhenRule
Since April 28, 2026Built with Xcode 26 or later and an SDK for iOS 26, iPadOS 26, tvOS 26, visionOS 26 or watchOS 26.
Since September 9, 2026iOS and iPadOS apps target iOS 13 or later.
Starting April 2027 (no day given yet)iOS and iPadOS apps built with the iOS and iPadOS 27 SDK or later and targeting iOS 15 or later; tvOS, visionOS and watchOS apps built with their 27 SDKs or later.
Starting April 2027iPhone Duo screenshots. Apple's October 5 post says submitted apps and games need them; the screenshot specifications tie the rule to apps using the iOS 27.1 SDK or later. Outer display 1398×2034 or 2034×1398 pixels, inner display 2007×2853 or 2853×2007.

Xcode 27 includes the iOS 27 SDK, needs macOS Tahoe 26.6 or later and runs only on Apple silicon Macs, so Intel build agents and old CI images have to go. Xcode 27.1 adds iPhone Duo support.

Several changes come with the SDK, not the date: iOS 27 SDK builds must adopt the scene-based life cycle and must include a launch screen (Info.plist needs UILaunchStoryboardName, UILaunchStoryboards, UILaunchScreen or UILaunchScreens, or the App Store rejects the build), and the system ignores UIDesignRequiresCompatibility, the key that kept an app's look from earlier SDKs. The live binary is unaffected, and Xcode 26 builds are accepted until April, so urgent fixes can still ship.

Moving an AppDelegate-only app to UIScene

Apple's test: migrate if Info.plist has no UIApplicationSceneManifest with a configuration, or the app delegate doesn't implement application(_:configurationForConnecting:options:). Multiple windows stay optional. On iOS 26, UIKit already warns such apps: UIScene lifecycle will soon be required.

1. Add the scene manifest to Info.plist:

<key>UIApplicationSceneManifest</key>
<dict>
    <key>UIApplicationSupportsMultipleScenes</key>
    <false/>
    <key>UISceneConfigurations</key>
    <dict>
        <key>UIWindowSceneSessionRoleApplication</key>
        <array>
            <dict>
                <key>UISceneConfigurationName</key>
                <string>Default Configuration</string>
                <key>UISceneDelegateClassName</key>
                <string>$(PRODUCT_MODULE_NAME).SceneDelegate</string>
            </dict>
        </array>
    </dict>
</dict>

2. Create the window in a scene delegate and remove it from application(_:didFinishLaunchingWithOptions:). Storyboard apps instead add UISceneStoryboardFile, and UIKit builds the window.

import UIKit

class SceneDelegate: UIResponder, UIWindowSceneDelegate {
    var window: UIWindow?

    func scene(_ scene: UIScene, willConnectTo session: UISceneSession,
               options connectionOptions: UIScene.ConnectionOptions) {
        guard let windowScene = scene as? UIWindowScene else { return }
        let window = UIWindow(windowScene: windowScene) // was UIWindow(frame: UIScreen.main.bounds)
        window.rootViewController = RootViewController()
        window.makeKeyAndVisible()
        self.window = window

        // Cold start: launchOptions is nil now
        if let url = connectionOptions.urlContexts.first?.url { DeepLinks.open(url) }
        if let activity = connectionOptions.userActivities.first { DeepLinks.handle(activity) }
    }

    // Warm start, was application(_:open:options:)
    func scene(_ scene: UIScene, openURLContexts URLContexts: Set<UIOpenURLContext>) {
        if let url = URLContexts.first?.url { DeepLinks.open(url) }
    }
}

3. Move the callbacks. UIKit stops calling the app delegate's activation, background, URL, user-activity and quick-action methods, even if they stay implemented.

AppDelegateReplacement
applicationDidBecomeActive(_:) and the other three state callbackssceneDidBecomeActive(_:), sceneWillResignActive(_:), sceneDidEnterBackground(_:), sceneWillEnterForeground(_:); for app-wide state, UIApplication notifications such as willEnterForegroundNotification
launchOptions, now nilconnectionOptions.urlContexts, userActivities, shortcutItem, notificationResponse
application(_:open:options:)scene(_:openURLContexts:)
application(_:continue:restorationHandler:) (universal links, Handoff)scene(_:continue:)
application(_:performActionFor:completionHandler:) (quick actions)windowScene(_:performActionFor:completionHandler:)
State restorationPer scene: return an NSUserActivity from stateRestorationActivity(for:) and read session.stateRestorationActivity on connect (it can be nil while the device is still locked)

4. Keep process-level work in the app delegate: SDK setup, push registration (application(_:didRegisterForRemoteNotificationsWithDeviceToken:)) and the UNUserNotificationCenter delegate, which Apple says must be set before launch finishes.

5. Stop reading the screen. Apple's iPhone Duo guide: size from view.bounds or window.bounds, not UIScreen.main; don't pick layouts by orientation or idiom; get the screen from view.window?.windowScene?.screen. Find the window through the scene, not the app delegate. Apple's iOS 27 release notes add that in apps built with the iOS 27 SDK, the system no longer offers the non-interactive external-display scene on its own: to show custom content on an external display, register a UISceneAccessory.externalNonInteractive accessory with the view controller's registerSceneAccessory(_:).

Flutter, React Native, Unity, .NET MAUI and Xamarin

Order of work

  1. Inventory: framework version, Xcode and CI image, deployment target, AppDelegate methods in use, and SDKs that hook the app delegate (push, links, sign-in, analytics).
  2. Get an Apple silicon Mac with macOS Tahoe 26.6 or later and the Xcode 27 release your framework supports (.NET workloads pin an Xcode version).
  3. Upgrade the framework, then plugins and SDKs, and raise the deployment target to iOS 15.
  4. Adopt UIScene, then fix layouts in Device Hub's resizable simulator and the iPhone Duo simulator.
  5. Test cold and warm starts: custom URLs, universal links, push taps, quick actions, sign-in redirects, state restoration, background and foreground.
  6. Make the iPhone Duo screenshots, ship a TestFlight build and submit before April 2027.
App still launching from AppDelegate? We update native, Unity, Flutter, React Native and Xamarin apps to the current App Store and Google Play rules at a fixed price. You keep your signing keys. It starts with a $290 check and a fixed quote within 2 business days.
See the app update offer