# Update a published app

> Prepare another release while preserving your app identity, signing, accounts and existing store listing.

Canonical: https://www.rnblocks.dev/docs/publishing/updates
Updated: 2026-10-01

An update belongs to the existing app. Keep its account, identifiers and signing relationship, then prepare and test the new version.

## Keep the existing identity

Section: https://www.rnblocks.dev/docs/publishing/updates#identity

Tell the publishing agent this is an update before preparing the release. Do not accept a new app identifier just to get around a build or connection error.

- Use the same iOS bundle identifier and Android package name.
- Use the Apple team and Play account that own the app, unless you are deliberately completing a provider-supported transfer.
- Check the existing Expo project and release connections.
- Preserve the signing setup needed to update the installed app.

- [Release identity](https://www.rnblocks.dev/docs/publishing/release-settings)

## Prepare the next version

Section: https://www.rnblocks.dev/docs/publishing/updates#version

1. **Save and preview the changes** — Make the change in Studio, then check the affected flows in native preview. Consider existing users and saved data, not only a fresh install.

2. **Set the version and build numbers** — In Release settings, set the next App version and appropriate iOS build number. Increase Android version code beyond previously uploaded versions. Save the settings.

3. **Update the listing where needed** — Write Release notes in Store details. Replace screenshots that no longer reflect the app. Update privacy information if the app’s data handling changed.

4. **Build and test again** — Prepare a fresh reviewed build for the intended destination. Test both installation and the experience of an existing user where possible.

- [Android versioning](https://developer.android.com/studio/publish/versioning)

## Submit the new version

Section: https://www.rnblocks.dev/docs/publishing/updates#release

In App Store Connect, create the next version under the existing app and associate the intended processed build. Existing metadata can be carried forward, but review it for this release.

In Play Console, create the release in the intended track using the existing app. Verify its version code and review the rollout choices. Follow the store’s review and release process again.

- [Create a new Apple app version](https://developer.apple.com/help/app-store-connect/update-your-app/create-a-new-version/)
- [Publish your app on Google Play](https://support.google.com/googleplay/android-developer/answer/9859751?hl=en)

## A Studio change does not update installed copies

Section: https://www.rnblocks.dev/docs/publishing/updates#saved

Saving a change in Studio or downloading a package does not replace the app already installed by customers. This guide covers a new store build and release.

After release, install the store-delivered version and verify the changed journey. Keep track of the released version when investigating reports from users.


## Continue

- [Testing](https://www.rnblocks.dev/docs/publishing/testing)
- [Submit and review](https://www.rnblocks.dev/docs/publishing/submit-and-review)
- [Privacy and support](https://www.rnblocks.dev/docs/publishing/privacy-and-support)

## Official references

- [Create a new Apple app version](https://developer.apple.com/help/app-store-connect/update-your-app/create-a-new-version/)
- [Android versioning](https://developer.android.com/studio/publish/versioning)
- [Publish your app on Google Play](https://support.google.com/googleplay/android-developer/answer/9859751?hl=en)