On this page · 9 sections
Summary. Apple's App Store submitting page says that starting April 2027, iOS and iPadOS apps uploaded to App Store Connect must be built with the iOS and iPadOS 27 SDK or later and target iOS 15 or later; tvOS, visionOS and watchOS apps need their 27 SDKs. The earliest Apple notice we found is dated 9 September 2026, and Apple has not named the day. Any iOS 27 SDK build changes four things: apps without the UIScene life cycle fail to launch, the UIDesignRequiresCompatibility opt-out from Liquid Glass is ignored, UIRequiresFullScreen no longer stops resizing and apps resize on iPhone Duo. Two more sit at submission: App Store Connect rejects iOS 27 SDK uploads with no launch screen, and Apple says submissions from April 2027 need iPhone Duo screenshots. Xcode 27.2 needs an Apple silicon Mac on macOS Tahoe 26.6 or later and only debugs on iOS 17 or later. From 1 November 2026, about 5 months and 10 fortnightly releases remain. Ship the UIScene migration in December from your current Xcode 26 toolchain, then move to Xcode 27.2, and March stays free for screenshots and fixes.
About this article. For iOS engineering leads, release managers and agencies planning the App Store move to the iOS 27 SDK. We checked each requirement against Apple's developer news, submitting page, technotes, release notes and App Store Connect help on 1 November 2026. Apple can name the exact April date or add detail later, so re-check before your final release. No vendor paid for inclusion. Researched with AI assistance and reviewed by our editorial team.
What Apple has published, and where
The dated requirement is spread across several Apple pages.
| Date | Apple source | What it adds |
|---|---|---|
| 9 September 2026 | Developer news: App Store submissions now open | The April 2027 floor for iOS, iPadOS, tvOS, visionOS and watchOS SDKs |
| 5 October 2026 | Developer news: Prepare and submit your apps for iPhone Duo | iPhone Duo screenshots for any app or game submitted from April 2027 |
| Live on 1 November 2026 | Submitting to the App Store | Repeats the floor and adds a minimum target of iOS 15 |
| Live on 1 November 2026 | Screenshot specifications | Screenshot sizes, and a narrower wording: any app using the iOS 27.1 SDK or later |
| Live on 1 November 2026 | Upcoming Requirements | No April 2027 entry yet; the newest entries are the iOS 13 minimum target (since 9 September 2026) and the Xcode 26 floor (since 28 April 2026) |
Two points follow. First, the rule applies to uploads. Nothing in it pulls live apps; it bites the next time you upload a new app or an update. Apple's separate outdated-apps policy can still flag apps with no update in three years and almost no downloads, and gives them 90 days to update. Because TestFlight builds also arrive through App Store Connect, plan as if beta builds are covered too.
Second, macOS apps are not on the April 2027 list, though Apple's September notice says macOS 27 will be Apple silicon only.
A correction for regular readers: our Liquid Glass migration guide, last updated on 27 July 2026, called April 2027 a myth because the Apple pages we checked then carried no such date. Apple published the SDK floor on 9 September. That article's design guidance still applies; its deadline section does not.
Which day in April?
Apple says April 2027 and nothing more. Its history points late in the month: the Xcode 14.1 floor began on 25 April 2023, the Xcode 15 floor on 29 April 2024, the Xcode 16 floor on 24 April 2025 and the Xcode 26 floor on 28 April 2026.
The announcement has a pattern too. Apple previewed the last floor as April 2026 on 9 September 2025, then named 28 April on 3 February 2026, 84 days ahead. The 2025 date appeared in a notice of 21 February 2025, 62 days ahead. If that repeats, the exact day arrives around February 2027. That is our inference.
We would still plan for 1 April. A deadline treated as the 28th leaves no room if Apple picks an earlier day.
The toolchain you need
Apple's SDK and system requirements table sets the limits below, as of 1 November 2026. The last column is our reading of the April floor.
| Xcode | Runs on | iOS SDK | iOS deployment targets | Debugging and simulators | Meets the April 2027 floor? |
|---|---|---|---|---|---|
| Xcode 27, 27.1 and 27.2 | macOS Tahoe 26.6 or later | iOS 27, 27.1 and 27.2 | iOS 15 to 27 | iOS 17 or later | Yes |
| Xcode 26.6 | macOS Tahoe 26.2 to 26.x | iOS 26.5 | iOS 15 to 26.5 | iOS 15 or later | No |
Xcode 27.2 shipped on 29 October 2026, and App Store Connect has taken uploads from it since 30 October. Xcode 27 only installs and runs on Apple silicon Macs, so Intel build machines cannot make the move.
The iOS 15 line forces a change only for apps still targeting iOS 13 or 14, which today's floor allows. The harder problem is testing. Xcode 27 cannot debug on iOS 15 or 16 devices or simulate those releases, and its Instruments also needs iOS 17 or later. You have three options:
- Keep a Mac on macOS Tahoe 26.6, which runs both Xcode 26.6 and Xcode 27, and debug older devices with Xcode 26.6. The table lists no macOS 27 support for Xcode 26.6, so do not upgrade that Mac. Those debug builds use the iOS 26.5 SDK, not the SDK you will ship.
- Install the real Xcode 27 build on older devices. The TestFlight app's App Store listing requires iOS 16 or later, so iOS 15 devices need a registered-device build.
- Decide from your own analytics that iOS 15 and 16 users no longer justify the test cost, and raise the floor to iOS 17.
Six changes that come with the iOS 27 SDK
The first four arrive in any build that uses the iOS 27 SDK, whatever the date. The last two are checks at upload or submission.
| Change | When it applies | If you ignore it | Fix |
|---|---|---|---|
| UIScene life cycle required | Any build with the latest SDK | The app fails to launch | Add a scene manifest and scene delegate |
| Liquid Glass opt-out ignored | Building for iOS 27 or later | The old look goes; custom chrome can clash | Remove UIDesignRequiresCompatibility and audit custom UI |
| UIRequiresFullScreen no longer opts out | iOS 27 SDK or later with the key set to YES | Discrete resizing; fixed layouts can break | Support resizing, then remove the key |
| iPhone Duo resizing | iOS 27 SDK, fully with the iOS 27.1 SDK or later | Stretched, clipped or misplaced content | Stop sizing from UIScreen.main, orientation or idiom |
| Launch screen required | Any upload built with the iOS 27 SDK or later | App Store Connect rejects the upload | Add one of the four launch screen keys |
| iPhone Duo screenshots | Submissions from April 2027 | Apple says submissions need them | Upload them in App Store Connect |
One consequence shapes the plan below. You cannot take the first four one at a time: your first Xcode 27 upload carries all of them, plus the launch screen check.
UIScene: the change that stops apps launching
Since iOS 18.4, UIKit has logged that apps without the UIScene life cycle would one day hit an assert, and in iOS 26 the message said adoption would soon be required. The iOS 27 release notes and Apple's transition guide now state the outcome: apps built with the latest SDK must adopt the scene-based life cycle or they fail to launch.
Apple's technote lists two signs that an app must migrate: the Info.plist has no UIApplicationSceneManifest key or the key has no configurations, or the app delegate does not implement application(_:configurationForConnecting:options:). Supporting multiple windows is optional, and Apple suggests weighing it separately because it may mean restructuring your data model. The minimum is a manifest:
<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>
Add a scene delegate that creates the window with UIWindow(windowScene:) in scene(_:willConnectTo:options:). If your root view controller comes from a storyboard, name it in the manifest with UISceneStoryboardFile instead.
The manifest is the quick part. Once an app adopts scenes, UIKit stops calling the app delegate's active, background and foreground methods, even if you keep them. The time goes into moving that code and URL handling into scene callbacks, and into finding every use of a global window. Push notification taps, cold-launch deep links and third-party SDKs that assume UIApplication.shared.keyWindow are likely places for regressions.
The scene APIs date from iOS 13, so you can adopt them while still building with Xcode 26.6 and prove the migration in production before the new SDK changes anything else. Cross-platform apps depend on their framework's iOS embedding; our Flutter UIScene guide covers the App Store 2.1(a) rejection pattern, and our iOS 27 API changes checklist lists the UIKit calls to replace.
Liquid Glass: the opt-out key stops working
Apple's reference page for UIDesignRequiresCompatibility says the key is temporary, and that YES runs the app in a compatibility mode that looks like an app built against earlier SDKs. It adds that the system ignores the key when you build for iOS 27, iPadOS 27, Mac Catalyst 27, macOS 27 or tvOS 27 or later. From April 2027, every iOS upload is in that group.
Standard components pick up the current design automatically. Apple's adoption guide points the work at custom backgrounds in navigation elements and tab bars, and at testing custom elements under settings that reduce transparency or motion. We would add hard-coded opacity and Increase Contrast to that audit. Remove the key so nobody assumes it still protects you.
Resizing: UIRequiresFullScreen and iPhone Duo
Before iOS 27, UIRequiresFullScreen configured iPad apps only. Starting in iOS 27 and iPadOS 27, it no longer opts your app out of resizing on either platform. When you build with the iOS 27 SDK or later and the key is YES, the system resizes your scene discretely: the scene keeps its size while someone drags the window, then changes size in one step when they finish. The exception is an app that also sets UIRequiresFullScreenIgnoredStartingWithVersion to 27 or earlier. The system then ignores UIRequiresFullScreen from that version on, and Apple says to use this key only after you have updated the app.
To support resizable scenes, TN3192 asks for a launch screen, support for all interface orientations and no UIRequiresFullScreen key. Apple's partial replacements are UISceneSizeRestrictions for a preferred minimum size and prefersInterfaceOrientationLocked for temporary orientation locks.
iPhone Duo, on sale since 23 October 2026, adds a second resizing path. Apple's preparation page shows three tiers:
| Built with | Behaviour on iPhone Duo |
|---|---|
| iOS 26 SDK or earlier | Runs centred on the open inner display with empty space around it; on the outer display it sits left of the status bar and camera |
| iOS 27 SDK | Resizes to fill most of the inner display, still avoiding the status bar on the right edge |
| iOS 27.1 SDK or later | Uses the full display, with toolbars and tab bars running vertically below the status bar |
Anyone uploading with Xcode 27.1 or later is in the third row, so make sure content adapts to vertical bars first. The original Xcode 27 meets the floor and stops at the second row, but we would treat that as a stopgap.
Apple lists the patterns to fix: replace UIScreen.main.bounds with view or window bounds, re-read sizes in layoutSubviews or viewDidLayoutSubviews, take scale from the trait collection, create windows with UIWindow(windowScene:), stop choosing layouts by orientation or userInterfaceIdiom, stop treating regular width as iPad, remove hard-coded device sizes, and check full-bleed media set to aspect fill.
Apple also ships an Xcode skill, which it says finds most issues but not all. Ask the coding assistant to get my app ready for iPhone Duo, or export it for another agent with xcrun agent skills export. Test with the resizable simulator in Device Hub, iPhone Mirroring on macOS 27, and the iPhone Duo simulator in Xcode 27.1, which Apple calls the best way to test the full experience. Our iPhone Duo readiness checklist goes deeper on layout; it predates the 5 October notice, so go by the dates here.
App Store Connect: launch screen and iPhone Duo screenshots
When you upload an app built with the iOS 27 SDK or later, App Store Connect checks the Info.plist for at least one of UILaunchStoryboardName, UILaunchStoryboards, UILaunchScreen or UILaunchScreens. If none is present, it rejects the upload with error ITMS-90870. So the check already applies to any team building with Xcode 27; it does not wait for April.
Apple's 5 October notice says that from April 2027 any app or game submitted must include iPhone Duo screenshots. Its screenshot help page words this more narrowly, as any app using the iOS 27.1 SDK or later, and lists the sizes: 1398 x 2034 or 2034 x 1398 pixels for the outer display, and 2007 x 2853 or 2853 x 2007 pixels for the inner display. It does not say whether one display is enough, so prepare both.
Submitting early earns a product page badge saying the app is optimised for iPhone Duo, and the App Store Connect preview tool shows how assets look on the device. Separately, apps with social media capabilities must indicate them in App Store Connect; our age rating guide covers those questions.
The checklist
The order keeps the UIScene release apart from your first Xcode 27 upload.
November and December 2026
- List every app, extension and target you ship, with its Xcode version, SDK and deployment target.
- Search each Info.plist for
UIApplicationSceneManifest,UIDesignRequiresCompatibility,UIRequiresFullScreenand the four launch screen keys.
- Decide from analytics whether iOS 15 and 16 stay supported.
- Move build Macs and CI images to Apple silicon and macOS Tahoe 26.6 or later, and install Xcode 27.2 alongside your current Xcode.
- Add a launch screen if missing.
- Ship the UIScene life cycle in a December release built with Xcode 26.6, so real users exercise it on its own.
January 2027
- Start Xcode 27.2 builds, in TestFlight only.
- Remove
UIDesignRequiresCompatibilityand audit custom chrome in light, dark, Reduce Transparency and Increase Contrast.
- Remove
UIRequiresFullScreen, or addUIRequiresFullScreenIgnoredStartingWithVersionif older releases still need it, and test resizing on iPad and iPhone.
- Run Apple's iPhone Duo skill and fix
UIScreen.main, orientation and idiom checks.
February 2027
- Test on the iPhone Duo simulator, the resizable simulator and iPhone Mirroring, plus physical devices on iOS 17 or later.
- Cover iOS 15 and 16, if still supported, using the options above.
- Update third-party SDKs and your cross-platform framework to versions that support the iOS 27 SDK and scenes.
- Ship your first production release built with Xcode 27.2.
- Check Apple's developer news and Upcoming Requirements page weekly for the exact April date.
March 2027
- Upload iPhone Duo screenshots for both displays and check the product page in the preview tool.
- Make Xcode 27 the CI default and rehearse a hotfix on it, because after the cut-off an urgent fix can only be built with the 27 SDK.
A worked timeline: one team, ten releases
Take a team that ships every two weeks. From 2 November 2026 to 1 April 2027 is 150 days, and 150 / 14 = 10.7, which is 10 full releases.
| Releases | Window | Work shipped |
|---|---|---|
| 1 and 2 | November | Inventory, toolchain, launch screen, iOS 15 and 16 decision |
| 3 and 4 | December | UIScene in production, still built with Xcode 26.6 |
| 5 and 6 | January | Xcode 27.2 test builds for Liquid Glass and full-screen fixes; production stays on Xcode 26.6 |
| 7 and 8 | February | iPhone Duo fixes, device testing and the first production build from Xcode 27.2 |
| 9 and 10 | March | Screenshots, CI switch, hotfix rehearsal and buffer |
If a release slips, the buffer in March absorbs it. Starting in February removes that buffer.
A note for teams in India and multi-client agencies
Apple's wording has no regional carve-out, so a Gurugram or Bengaluru team faces the same date as its US, UK or EU client. Agencies should run the inventory across the whole portfolio in November, because a dormant app that needs one urgent update in May will need the full UIScene, resizing and screenshot work first.
How eCorpIT can help
eCorpIT is a Gurugram-based technology organisation, founded in 2021, assessed at CMMI Level 5 and MSME certified, with senior-led engineering teams working across AWS, Microsoft and Google platforms. Our iOS and Swift app development practice takes apps through the iOS 27 SDK move as a fixed-scope project, from portfolio inventory and UIScene migration to iPhone Duo layouts, screenshots and the CI switch. Talk to us at /contact-us/.
Last updated: 1 November 2026.
