Managed Mobile Builds

StationOps can build signed Android and iOS application artifacts without creating runtime infrastructure for the service. Android builds produce an AAB for Google Play, while iOS builds produce an IPA for App Store Connect or another selected distribution method.

---

Before You Start

You need:

• A saved service in an active project. Mobile setup is available after the service and its infrastructure configuration have been saved.
• Project administrator access to change source, signing, and publishing settings.
• A public repository URL, or an existing read-only Git connection for a private repository.
• Signing material for each platform you intend to build.

---

Create a Mobile Service

1. Open the project in Architect and create or edit a service.
2. Set the service target to Mobile.
3. Select Android, iOS, or both platforms.
4. Configure the source repository and branch.
5. Save the service and its infrastructure configuration.
6. Open Mobile build and publishing readiness on the saved service.

The readiness panel tracks source onboarding, signing, and publishing separately. Complete the required setup for each selected platform before starting a managed build.

---

Configure Android

Signing

Upload one supported keystore file:

• .jks
• .keystore
• .p12

Enter its key alias, store password, and key password. Confirm that you have retained a recoverable backup before submitting the signing configuration.

Google Play Publishing

To publish successful Android builds automatically:

1. Upload a Google Play service-account JSON credential.
2. Select the release track: Internal, Alpha, Beta, or Production.
3. Save the publishing configuration.

When publishing is configured, a successful build uploads the generated AAB to the selected Google Play track.

---

Configure iOS

Signing

Provide all of the following:

• A .p12 signing certificate and its password, if the certificate uses one.
• One or more .mobileprovision provisioning profiles.
• The application's bundle identifier.
• A distribution method: App Store Connect, Ad Hoc, Development, or Enterprise.

Make sure the certificate, provisioning profile, bundle identifier, and distribution method belong to the same Apple application setup.

App Store Connect Publishing

To upload successful iOS builds, provide an App Store Connect .p8 API private key, its key ID, and its issuer ID. StationOps uploads the generated IPA for App Store Connect processing; Apple review and release remain separate steps in App Store Connect.

---

Run and Monitor a Build

Return to the service package area after the readiness checks pass and trigger a build. From the build record you can monitor progress, cancel an active build, and download available artifacts.

If a build is not ready to start, open the readiness panel and resolve the source, signing, or publishing item shown there.

---

Related Guides