Publish an Asset Package

Refresh the app without replacing the app binary

An asset package is a Network-scoped ZIP containing artwork and configuration that an installed app can download. It is not an App Store or Play Store build. Publish a package when the app needs a new set of brand assets or bundled settings.

Every publication creates an immutable revision for one platform and release channel. Existing revisions never change, which gives the app a stable checksum and gives your team a clear release history.

Choose the target

Platform: Choose iOS or Android. Each platform keeps its own revision sequence and latest package.
Release channel: Choose Production for the public app, Staging for release checks, or Development for active development. The app only discovers a package matching the platform and channel it requests.

Understand artwork inheritance

You do not need to upload every image for every revision. Astarium resolves each artwork slot in this order:

The file uploaded for this revision
The Network's static artwork
The Astarium platform default

The package form shows the current inherited source and preview. Upload a file only when this revision should override it. If no inherited source exists, an override is required before publication.

Artwork requirements

App icon: 1024 × 1024 px
Launch artwork: 1440 × 3200 px
Brand logo: 1024 × 1024 px
App background: 1440 × 3200 px

Overrides accept PNG, JPEG, or WebP images up to 10 MB. Uploaded files must match the stated resolution. Keep important details away from the edges of portrait artwork so different screens can crop it comfortably.

Add package configuration only when needed

The optional configuration field accepts a named JSON object. It is merged into the generated config.json for this revision.

{
  "features": {
    "seasonalWelcome": true
  }
}

Use this for settings that belong to the downloaded revision. Live configuration remains authoritative for settings that should change independently. Do not replace reserved schemaVersion, network, or endpoints values, and do not paste a complete live configuration response into the package.

What happens when you publish

Astarium validates the target, JSON, uploaded image types, sizes, and resolutions.
It resolves uploaded overrides and inherited artwork into one complete asset set.
It writes config.json, the files below assets/, and manifest.json into a ZIP.
It records each file's size and SHA-256 checksum in the manifest.
It calculates the ZIP checksum, stores the revision, and verifies the completed archive.
The matching live configuration begins advertising the latest published revision to the app.

If validation fails, no usable revision is published. Correct the highlighted field and publish again.

How the app activates a revision

The app receives the latest revision number, download URL, size, and SHA-256 through live configuration. It downloads the ZIP, verifies the outer checksum and every manifest entry, then activates the revision only after every check passes. ETag support lets an app confirm that its installed package is still current without downloading it again.

Use package history

Package history shows the target, status, size, publication time, and checksum for every revision. Download a revision when you need to inspect exactly what was published. Because revisions are immutable, publish a new revision for every correction. Platform operators can remove a revision when it should no longer remain available; removal is not a rollback and does not create a replacement package.

Before publishing to Production

Confirm the selected Network, platform, and release channel
Preview every inherited image and upload intentional overrides
Check that portrait artwork keeps its focal point safe across screen sizes
Validate additional JSON in Development or Staging
Publish, then confirm the app reports and activates the expected revision