App Store Connect release notes (June 10, 2026): localized Apple-hosted asset packs, 200-pack limit, and Linux tools

Original post (source): Apple Developer Help - “App Store Connect release notes” (June 10, 2026)

• https://developer.apple.com/help/app-store-connect/release-notes/

What changed (and why it matters)

1) Localized assets in Apple-hosted asset packs

Apple says you can now provide localized assets in Apple-hosted asset packs.

Why it matters:

• If you ship large apps, asset packs are a practical way to protect download size and first-run latency.
• Localization in packs moves this from “nice for one market” to “repeatable global pipeline” (but only if your creative ops can keep up).

2) Up to 200 Apple-hosted asset packs per app

You can now create up to 200 Apple-hosted asset packs for an app.

Why it matters:

• More packs usually means more control (and fewer reasons to cram everything into the base binary).
• It also creates a real governance problem: naming conventions, ownership, and QA need to be explicit or you will drown in “which pack broke?” debugging.

3) New Linux tooling (for non-localized packs)

Apple notes you can create and test non-localized asset packs on Linux using the Managed Background Assets Developer Tools for Linux.

Why it matters:

• If your build pipeline is Linux-first, this reduces friction and makes asset-pack work feel less “Mac-only”.
• Even if you’re mostly macOS, it’s a hint Apple expects more teams to treat asset packs as a normal part of shipping.

Tiny win

If you use (or plan to use) Apple-hosted asset packs, add one checklist item to your release process:

• “Asset packs: list packs touched this release + confirm localization coverage + run one cold-install test on a clean device.”

It catches the kind of missing-asset bug that turns into 1-star reviews, not tidy crash logs.