Skip to content

After publication

A new visual, a new page, a fix: your app evolves, and each important change goes through a new version.

What it is for

Sending a new version of your app to the stores and following its progress.

Where to find it

In the manager, open Publication, section Build a version.

The "Build a version" section of the manager, with the list of prepared versions

The "Build a version" section of the manager, with the list of prepared versions. The layout may change between versions.

Build a version

  1. Check the prerequisites displayed under each platform (identifier entered, publishing files uploaded).
  2. Choose the platform, enter the version (for example 1.2.0) and, optionally, the build number.
  3. Start the build.

The version is prepared then uploaded to TestFlight (iPhone and iPad) and to the internal testing track (Android). It is never published automatically to the public: you approve going live in the store's console.

Follow the versions

The Versions list shows the date, platform, number and status: queued, being prepared, prepared, sent to the store, failed or cancelled. A queued or in-progress version can be cancelled.

Good to know

  • Only one version at a time per platform.
  • Up to 10 versions per month for your company; a failed version is not counted.
  • Build number: it is calculated automatically (the previous one plus one). For an app already published, give the first version a number higher than that of the store's latest version.
  • Changes to the theme, menu or pages in the manager do not wait for a new version: the app picks them up the next time it starts.

Update by our team

Prefer not to deal with it? From the service's page, the manager can order an update service carried out by our team.