---
title: "Release updates"
description: "Ship a new version without disrupting the app already in the store."
---
An App Store update is a new reviewed version of the existing app. Keep the same app record and bundle identifier, choose a higher version, test the migration path, and explain what changed.

### 1. Prepare the update

Finish the changes and test both a fresh install and an upgrade from the current public version. Protect existing accounts, saved data, subscriptions, and database migrations.

### 2. Start a new version in Superapp

Open the existing project's publishing flow. Superapp keeps the App Store Connect app identity and guides you to a higher marketing version when the previous one is locked.

### 3. Build and test the exact candidate

Upload the build, wait for processing, and install it from TestFlight. Recheck sign-in, purchases, notifications, stored data, and the feature changed by this release.

### 4. Update the product page

Add required What's New notes, replace screenshots when the interface changed, and update privacy answers, support content, pricing, or review notes when necessary.

### 5. Submit and choose release timing

Send the new version to review, then choose the appropriate App Store Connect release option: manual, automatic, or phased when available for the release.

## Write useful release notes

Describe changes people can recognize. “You can now edit saved workouts and sync them to Apple Watch” is more useful than “bug fixes and improvements.” Keep internal implementation details out of customer-facing notes.

## After release

-   Confirm the version appears in the intended storefronts.
-   Install it from the public App Store and complete a smoke test.
-   Monitor crashes, sign-in failures, purchase errors, and support messages.
-   Keep the previous release notes and build reference for incident investigation.
-   Prepare a focused follow-up rather than changing several unrelated systems at once.

:::tip
Apple notes that an approved version can take time to appear across all selected storefronts. A short delay after approval does not necessarily mean publishing failed.
:::