Two Apple pages that both describe the April 2027 iPhone Duo screenshot requirement do not agree on who it applies to. The developer news post says, "Starting April 2027, any apps or games submitted will need to include screenshots for iPhone Duo," while the App Store Connect screenshot specifications page says, "Starting in April 2027, screenshots will be required for any app using the iOS 27.1 SDK or later."
Both sentences are published by Apple on developer.apple.com. Neither page carries a correction, a link to the other, or a note explaining the difference. Apple has not clarified which scope applies.
That leaves one practical question for anyone shipping after March 2027: if your next submission uses an older SDK, do you need Duo screenshots or not? The two pages differ, and the difference is not cosmetic: one scopes the requirement to the act of submitting, the other to the SDK the build uses.
What each page actually says
The news post describes the badge first: "When you submit iPhone Duo screenshots in App Store Connect, your App Store product page will display a badge to let people know your app is optimized for iPhone Duo." Then it gives the deadline in one sentence, with no SDK condition attached: "Starting April 2027, any apps or games submitted will need to include screenshots for iPhone Duo."
The screenshot specifications page is a reference table. For iPhone Duo it lists four image sizes: 1398 × 2034 and 2034 × 1398 for the outer display, and 2007 × 2853 and 2853 × 2007 for the inner display. In the notes for that row it says: "Starting in April 2027, screenshots will be required for any app using the iOS 27.1 SDK or later." It repeats the badge sentence, but not the "any apps or games submitted" sentence.
The third relevant page, Apple's "Prepare your app for iPhone Duo," explains rendering, not submission: the iOS 26 SDK centers the app with empty space, the iOS 27 SDK fills most of the inner display but avoids the right-edge status bar, and the iOS 27.1 SDK or later uses the full display with vertical toolbars. It does not say when screenshots become mandatory, so it cannot settle the scope question.
Why the gap matters
The two rules form a small matrix:
- Submitting after April 2027 with the iOS 27.1 SDK or later: both pages require Duo screenshots.
- Submitting after April 2027 with an older SDK: the news post requires them; the specifications page does not.
- Submitting before April 2027: neither page requires them, although you can add them and get the badge.
The disputed cell is the second one, and it is not rare. Plenty of teams stay on an older SDK for a release cycle, or ship a maintenance update without moving Xcode. Those teams need a decision now, because screenshot capture has to be scheduled with design and QA.
It is tempting to pick the interpretation that saves work. The cost of the two mistakes is asymmetric. If you add screenshots and the narrow reading is correct, you have spent one capture session and possibly gained a badge. If you skip them and the broad reading is correct, you have a submission problem at the worst possible time, with no documented appeal path that says "the other page told me I could."
Who to ask, and what to ask
Ask Apple in writing for an operational answer, not an interpretation. Use three channels together; they reach different owners:
- App Store Connect Help → Contact Us, routed to App Review or submission support. This channel can tell you what the review system will enforce.
- The feedback control on each documentation page. The issue is a documentation inconsistency; the fix is an edit to one or both pages.
- Apple Developer Forums, in App Store Connect or App Review. A public thread creates a record, and Apple staff sometimes answer. Treat a reply as information, not a policy commitment.
Keep it binary. Asking "which page is right?" invites a non-answer; this is harder to deflect:
Two Apple pages describe the April 2027 iPhone Duo screenshot requirement with different scopes. The developer news post says "any apps or games submitted"; the App Store Connect screenshot specifications page says "any app using the iOS 27.1 SDK or later."
Please confirm, for submissions on or after 1 April 2027:
(a) Is a submission built with the iOS 26 SDK, without Duo screenshots, accepted, warned, or rejected?
(b) Does the answer differ for a new app and for an update to an existing app?
(c) If a build uses the iOS 27.1 SDK but does not adopt Duo-specific APIs, are Duo screenshots still required?
(d) Which page should we treat as authoritative until both are updated?A written answer and a documentation update would resolve this for our release planning.
Ask for the answer in the case, not on a call, so you can attach it to the ticket. If the first reply is generic, reply once with the two quotations and the four questions.
Five actions that are correct under either reading
These are the moves that do not depend on which page wins.
Add the four Duo screenshots now, without changing your SDK: 1398 × 2034 and 2034 × 1398 for the outer display, 2007 × 2853 and 2853 × 2007 for the inner. Under the broad reading this is the requirement; under the narrow reading it is optional, and submitting the set is what triggers the badge. One set satisfies both.
Do not upgrade to the iOS 27.1 SDK just for this deadline. Staying on your current SDK leaves the narrow reading satisfied, and the broad reading is covered by the set you just added. If you already planned a 27.1 upgrade, put the screenshots in the same release; the upgrade makes the requirement apply under both readings.
Capture from the Duo simulator in Xcode 27.1's Device Hub, not from a resized iPhone mockup. Check the inner display at the regular-by-regular size class and do not rely on orientation. Capture what the shipping SDK actually renders; do not draw an aspirational layout the build does not produce.
Run a dry run in App Store Connect today. Open the screenshot upload UI for your current build and record whether the Duo slots are marked required or optional. Save a dated screenshot with the build number. This is first-party evidence of enforcement, and it may answer the question before Apple does.
Put one dated line in the release checklist: for every submission on or after 1 April 2027, confirm the four Duo images are attached and record the SDK used. That is correct under both readings and gives you a record if review behaves differently from either page.
What to do when the answer arrives
If Apple says the broad scope applies, the screenshots are already in place; add the requirement to your submission template for every app, including maintenance updates. If Apple says the narrow scope applies, keep the screenshots anyway; they are accepted, trigger the badge, and cost little. If Apple updates one page but not the other, keep the written answer with the release ticket and cite the date.
If April arrives with no answer, ship with the screenshots. You will not be the developer who discovers the enforcement rule in production.
The useful conclusion is not that one page is wrong: two official pages describe different scopes, Apple has not clarified which scope applies, and the cheapest safe path is to satisfy the broader one while you wait for a written answer.
A checklist for handling submission requirements is here: https://hhfa008.github.io/personal/app-store-rescue.html
Top comments (0)