Create a Build

Create a Build

A build turns a tagged commit of your project into a native app binary — an IPA for iOS or an APK/AAB for Android and Huawei — signed and ready to ship to the stores. This page walks through triggering a new build and following it through the pipeline.

Before You Start

A build needs a few things in place first:

• A project. The app you want to build must already exist. See Create Project.
• Signing credentials for the platform and build target you are building. Upload the iOS distribution certificate and provisioning profiles, or the Android/Huawei keystore, before your first build — see Credentials. The full certificate and profile walkthrough lives in Deploy Project.
• A git tag pushed to the project's managed repository. Every build is created from an existing tag; if the tag cannot be found in the repository, the build is rejected.
• Correct configuration. Make sure akinon.json (package name, bundle identifier, version, app name, icon, splash screen) is up to date before building.

Starting a New Build

Open the project and click the + New Build button in the top-right of the project header. This opens the Build dialog ("Create Build For").

The button is unavailable while a project is inactive.

Build Options

Fill in the create-build form:

• Build Target — the environment the build runs against: Production or Staging.
• OS — the target platform: iOS, Android, or Huawei.
• Project name — shown for reference; this field is read-only.
• Tag — the git tag to build from. This must match a tag that already exists in the project's repository.
• Description — optional notes about the build (up to 1000 characters). These appear later on the build's detail page.

Click Create to start the build.

If signing or store credentials for the selected platform and target are missing or expired, App Maker stops and shows a missing credentials dialog with a Go to credentials button that takes you straight to the Credentials page for that platform and target.

What Happens Next

Once created, the build appears in the project's Builds list and moves through these statuses:

• Pending — queued, waiting for a build agent.
• Deploying — the pipeline is running.
• Success / Failed — the final outcome.

You can cancel a build while it is still Pending or Deploying.

Only one active build (Pending or Deploying) is allowed per platform and build target at a time. Wait for the current build to finish — or cancel it — before starting another for the same OS and target.

The Builds list refreshes on its own while a build is in progress. Open a build to follow its timeline, stages, and logs, and to download its artifacts on the Build Detail page.

After a Successful Build

When a build succeeds you can download its artifacts (IPA, APK/AAB, and debug symbols) from Build Detail, then send it to the stores:

➡️ Distribute to Stores — TestFlight and App Store releases on iOS, Google Play tracks on Android.

Once a build's store status is successful, it also becomes eligible for over-the-air CodePush updates, letting you ship JavaScript-only fixes without a new store submission.

Related Pages

• Build Detail — timeline, stages, logs, and artifact downloads.
• Distribute to Stores — release a successful build to the app stores.
• CodePush — ship JS-only updates over the air.
• Deploy Project — credential prerequisites for building.
• Credentials — manage signing and store credentials per target.