Hi!
I have a similar issue and have been testing it quite thoroughly.
Here are my findings.
What I’ve verified:
- The affected App Store version is iOS 1.0, locale Swedish.
- The app version is still in PREPARE_FOR_SUBMISSION.
- I tested the required iPad 13" screenshot with Apple-supported sizes including 2064 × 2752 and 2048 × 2732.
- I also tested required iPhone screenshots with Apple-supported Dynamic Island sizes, including 1179 × 2556, 1206 × 2622, and a large-profile 1290 × 2796 screenshot.
- I removed/re-added the screenshots, logged out/in, tried Media Manager directly, and re-created the review submission state.
I then inspected App Store Connect’s own backend responses in DevTools.
The interesting part is that the screenshot placements are actually being created and reported as ACTIVE by App Store Connect:
- IPAD_13_PROFILE → ACTIVE
- IPHONE_DYNAMIC_ISLAND_MEDIUM_PROFILE → ACTIVE
- IPHONE_DYNAMIC_ISLAND_LARGE_PROFILE → ACTIVE
The 1290 × 2796 large iPhone screenshot is also reported by the backend with the correct width/height and is attached to IPHONE_DYNAMIC_ISLAND_LARGE_PROFILE.
However, when I click Add for Review, App Store Connect still returns:
STATE_ERROR.SCREENSHOT_REQUIRED.IPHONE_DYNAMIC_ISLAND
with:
A screenshot for one of the following types is required but was not provided: IPHONE_DYNAMIC_ISLAND_LARGE_PROFILE, IPHONE_FACE_ID_LARGE_PROFILE, IPHONE_DYNAMIC_ISLAND_MEDIUM_PROFILE
This is despite both medium and large Dynamic Island placements being present and ACTIVE.
Earlier, the same thing happened for iPad 13": the UI and placement API both showed the iPad screenshot present, while the review validator still returned STATE_ERROR.SCREENSHOT_REQUIRED.IPAD_13_PROFILE.
Media Manager also shows some faded “Using Existing Assets” entries for older optional device sizes, but those sections say 0 of 10 App Screenshots and cannot be removed directly. The older legacy appScreenshotSets still exist in the backend, while the newer Asset Library placements are also present.
So at this point it looks more like an App Store Connect backend consistency/validation issue than an image-format issue.
I’m planning to report this to Developer Support with the exact version/localization IDs and the failing 409 response.