Use these procedures as task-oriented reference. They describe public capabilities and verification steps, not private implementation. UI labels can vary by version.
Prepare source captures by device and locale; use sample accounts.
List target locales, device slots and required image order.
Confirm each source capture is in the intended language and matches the staged device.
Inspect headlines for line breaks, clipping, right-to-left reading order and contrast.
Export and inspect full-resolution files, including the narrowest layout and longest text.
After upload, check the actual app/version/locale slots and image order in App Store Connect.
Every intended matrix cell contains the right images in the correct order.
If a layout does not adapt cleanly, adjust that variant rather than accepting clipped text. Uploaded assets still require review; upload completion is not approval.
Keep the previous approved set as a reference.
Identify which feature and source screens changed.
Replace captures that no longer show the shipped behavior.
Review the headline against the new capture and remove outdated promises.
Recheck related localized variants and device layouts.
Export a clearly named revision and verify the destination before replacing assets.
The marketing image describes a visible feature in the current app.
Do not fix an outdated interface with a headline alone. Preserve clean original captures for future revisions.
Record app/version, device/OS, selected mode, input conditions and the smallest failing step. Distinguish expected behavior from the observed result. Use synthetic examples and omit credentials or private records.
Documentation index · Capabilities and limits · Support and sources