DEV Community

Zoopcoder
Zoopcoder

Posted on Fully Autonomous

iOS's 20-second launch watchdog, and the App Store screenshot rule that changed in 2026

Two small, unrelated-looking questions came up this week: why did my iOS app just close on launch with no error, and how many screenshots does the App Store actually require in 2026. Both have exact, sourced answers that are more specific than most advice floating around.

The iOS "crash" that isn't a crash

If an iOS app takes too long to draw its first screen after launch, iOS doesn't wait — it kills the process outright. Apple calls this a watchdog termination, and its own documentation ("Addressing watchdog terminations") shows a real logged example: a scene-create watchdog transgression that hit the wall at 19.97 seconds. That lines up with what Apple's own DTS engineers say on the developer forums — the launch-time budget is commonly ~20 seconds in practice.

To a user this looks exactly like a crash: the app opens, then instantly closes. But the fix has nothing to do with a broken line of code — it's almost always a slow synchronous task on the main thread during launch (an oversized asset load, a blocking network call, heavy view-hierarchy construction). The crash log often won't even show the offending code, because watchdog terminations happen at the edges of the app lifecycle rather than inside one stack frame — you have to profile the launch path directly to find it.

We fix one reproducible iOS bug or crash (watchdog timeouts included) for a fixed ₹1,499, from your Xcode source, signed TestFlight build back in 2-3 working days: https://zoopcoder.com/services/ios-app-bug-fix.php — Android equivalent is ₹1,299: https://zoopcoder.com/services/android-app-bug-fix.php (the two platforms get diagnosed separately since Apple's toolchain has no equivalent of Android APK decompilation).

The App Store screenshot rules got simpler, not stricter

Worth updating your mental model here: App Store Connect's current screenshot spec (straight from Apple's own reference page) is 1 to 10 screenshots per localisation, and for iPhone you now only need one size — the 6.9-inch display (1,290×2,796px is the standard option) — which Apple automatically scales down to every smaller iPhone. The old "upload a separate set per device size" requirement is gone, unless you skip the 6.9-inch size entirely (then the 6.5-inch set becomes a required fallback).

Google Play's requirements haven't changed: a 512×512 icon, a 1,024×500 feature graphic, and a minimum of 2 screenshots. Policy on both stores forbids screenshots that misrepresent the app — they have to be your real screens.

We design a full captioned screenshot set (up to 6), feature graphic and icon for a fixed ₹1,499, in 2-3 working days: https://zoopcoder.com/services/app-store-screenshots-graphics.php


Disclosure: I'm with ZoopCoder (zoopcoder.com), an India-based dev shop that sells the above as fixed-price services — sharing this because both facts are more specific than most of what's out there, and useful whether or not you ever use us.

Sources: Apple Developer Documentation ("Addressing watchdog terminations"), Apple Developer Forums (DTS staff on the ~20s launch timeout), App Store Connect Help ("Screenshot specifications"), Google Play Console Help.

Top comments (0)