Update a published app
Prepare another release while preserving your app identity, signing, accounts and existing store listing.
An update belongs to the existing app. Keep its account, identifiers and signing relationship, then prepare and test the new version.
On this page
Keep the existing 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.
Prepare the next version
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.
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.
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.
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.
Submit the new version
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.
A Studio change does not update installed copies
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.