[jkmassel]

Generates the Jetpack App Store screenshots from the app: the UI tests from #26119 take them against the fixtures, in every App Store language, on iPhone, iPad and iPhone Duo, and a compositor frames them below a headline fitted to each language.

Stacked on #26119. The screenshots below were taken from this branch rebased onto trunk, which has the iPhone Duo fixes (#26207–#26212) that #26119's base doesn't.

Summary

• bundle exec fastlane jetpack_screenshots builds the app with the fixtures and runs the new AppStoreScreenshots UI test once per device and language, saving the raw screenshots. Devices: iPhone 18 Pro Max (6.9"), iPad Pro 13-inch (M5) and iPhone Duo (outer and inner displays).
• bundle exec fastlane create_jetpack_promo_screenshots composes them with Scripts/app-store-screenshots/compose.swift: a title screen, then each screenshot in a device frame below its headline. update_jetpack_metadata_on_app_store_connect with_screenshots:true uploads them, as before.
• Headlines are fitted to each language: as large as they fit in two lines, one size for the whole set, balanced lines, Japanese and Chinese broken only between phrases, and a serif that ships with macOS for each script.
• bundle exec fastlane trigger_jetpack_screenshots does the same on CI: .buildkite/app-store-screenshots.yml builds once on the Xcode 27.1 image, runs a job per device and language (51, in a matrix step per device, since a matrix makes at most 50) at a low priority, so they only use Mac agents nothing else is waiting for, and composes whatever was taken into downloadable artifacts.
• On-screen content is translated too, for languages with a fastlane/appstoreres/jetpack_screenshot_content/<locale>.json: the lane writes translated copies of the fixture files and the app loads them over the originals. The fixtures the UI tests assert on don't change.
• The fixtures can serve images (WireMock's bodyFileName) and take an overlay. The new images are the screens' header images and photos, and generated placeholder avatars.
• The headlines are new GlotPress strings: a feature name ("Stats.") and the rest ("Your metrics, wherever you are."), so every language gets its bold lead without translators keeping markup.
• Removed: the old Jetpack screenshot layout (jetpack_screenshots.json), its assets and strings, and Scripts/fix-screenshots.rb. The WordPress app's screenshots are unchanged.

docs/app-store-screenshots.md covers all of it.

What a reviewer will want to know

The iPhone Duo needs Xcode 27.1. An app built with an older SDK runs letterboxed on its outer display, so the lane stops if the selected Xcode, or a build it would reuse, is older. App Store Connect takes both Duo displays in one set (APP_IPHONE_DUO), which deliver uploads from fastlane 2.241.1, hence the Gemfile bump.

The simulator only models the Duo's outer display. For the inner one, the lane moves the app to a 669×951 pt resizable display with xcrun devicectl device appResize, as unfolding does. XCUITest can't tap there, so the test asks the lane for each inner screenshot through a file and waits. On the Duo the test relaunches the app before each screen, since not every screen lays itself out for the outer display again after unfolding.

The test finds its way by identifiers and the fixtures' content, never the app's text, since it runs in every language. That needed one app change: an accessibility identifier on the Reader post's back button.

Nothing runs on PRs. The test is skipped unless the lane gives it somewhere to save screenshots, and the screenshot pipeline only runs when it's started. A full local run (17 languages × 3 devices) takes about three hours; on CI it's 51 jobs that can run side by side.

The translations are temporary. Every App Store language has headlines and on-screen content that Claude translated, not translators, so the screenshots can be generated in all 17 now. They're placeholders until both go through the translation pipeline: the headlines are replaced the first time download_jetpack_promo_strings runs after GlotPress has them, and the on-screen content has no pipeline yet. The headline English is the current App Store copy.

Screenshots

Taken on this branch rebased onto trunk. Each image is one language and device side by side, as create_jetpack_promo_screenshots writes them to fastlane/jetpack_screenshots_overview. The Japanese and German headlines are stand-ins.

English

Japanese and German, with translated content

Not in this PR

• Putting the headlines and on-screen content through the translation pipeline, to replace the temporary translations.
• A manifest for choosing screens, appearance and theme without editing code.
• Fixing the app retrying a failed image request over 1,000 times, which the image fixtures sidestep here.

Test plan

• swift test -Xswiftc -DUI_TEST_HTTP_FIXTURES --filter HTTPFixturesTests: 58 tests passed, including the new body file and overlay tests.
• ruby fastlane/lanes/screenshot_content_helper_test.rb: 10 runs, 0 failures. All fastlane/lanes/*_test.rb pass, and RuboCop reports no offenses in fastlane and the Gemfile.
• SwiftLint passes on the changed Swift files, which are stable under swift format.
• On this branch rebased onto trunk, with Xcode 27.1: jetpack_screenshots passed on all three devices in English and Japanese, and with translated content in Japanese and German on iPhone and iPad.
• On this branch as pushed, with Xcode 27.1: jetpack_screenshots passed on all three devices in English and Japanese. iPad in English first failed once, tapping a Reader card while the list replaced it; after the fix in the last commit it passed, as did iPhone in English and Japanese.
• The temporary translations are valid for all 16 languages: each language's content generates its fixture overlay with every notification's names and titles in place, and every headline fits within two lines (three for the title) on the iPhone, iPad and both iPhone Duo layouts, with no warnings from the compositor.
• .buildkite/app-store-screenshots.yml passes Buildkite's schema validation, and trigger_jetpack_screenshots is registered.
• Run the screenshot pipeline on CI. Not done yet: it starts 51 Mac jobs, and whether devicectl appResize works on a CI VM, for the iPhone Duo's inner display, is still unknown.
• Upload the screenshots to App Store Connect. Not done: it publishes to the live listing.

[dangermattic]

	1 Warning
⚠️	This PR is larger than 500 lines of changes. Please consider splitting it into smaller PRs for easier and faster reviews.

	1 Message
📖	This PR is still a Draft: some checks will be skipped.

Generated by 🚫 Danger

[wpmobilebot]

📲 You can test the changes from this Pull Request in WordPress by scanning the QR code below to install the corresponding build.

	App Name	WordPress
	Configuration	Release-Alpha
	Build Number	35790
	Version	PR #26339
	Bundle ID	org.wordpress.alpha
	Commit	d93fc1e
	Installation URL	5ni6r8lmpe690

Automatticians: You can use our internal self-serve MC tool to give yourself access to those builds if needed.

[wpmobilebot]

📲 You can test the changes from this Pull Request in Jetpack by scanning the QR code below to install the corresponding build.

	App Name	Jetpack
	Configuration	Release-Alpha
	Build Number	35790
	Version	PR #26339
	Bundle ID	com.jetpack.alpha
	Commit	d93fc1e
	Installation URL	023gigrggpffg

Automatticians: You can use our internal self-serve MC tool to give yourself access to those builds if needed.

[wpmobilebot]

🤖 Build Failure Analysis

This build has failures. Claude has analyzed them - check the build annotations for details.