Skip to main content
Technology & EngineeringCicd Patterns30 lines

Verify a Mobile Build with Codemagic CI

Design a Codemagic workflow that tests and signs a specific variant, then verifies the resulting artifact before an authorized distribution step.

Quick Summary8 lines
Locate the repository's existing CI entry point and check for a Codemagic workflow in `codemagic.yaml`. Record the app target, branch policy, platform and variant, package ID, expected version source, and build machine requirements. Pin the applicable SDK and dependency versions. Build a debug or unsigned fixture first if that path can prove dependency and test configuration before involving protected signing.

## Key Points

- [Codemagic YAML setup](https://docs.codemagic.io/yaml-basic-configuration/yaml-getting-started/)
- [Codemagic first signed build](https://docs.codemagic.io/yaml-quick-start/first-signed-build/)
skilldb get cicd-patterns-skills/codemagic-mobile-ciFull skill: 30 lines
Paste into your CLAUDE.md or agent config

Verify a Mobile Build with Codemagic CI

Define a build-only workflow first

Locate the repository's existing CI entry point and check for a Codemagic workflow in codemagic.yaml. Record the app target, branch policy, platform and variant, package ID, expected version source, and build machine requirements. Pin the applicable SDK and dependency versions. Build a debug or unsigned fixture first if that path can prove dependency and test configuration before involving protected signing.

Write steps in an order that makes failures informative. Check the working directory, tool versions, and lockfile handling. Resolve dependencies using the project's supported command. Run focused tests before building. Use explicit output paths so an old artifact from a different variant cannot match a broad glob. Decide which logs and files are useful on failure, and filter credential values from them.

Keep signing scoped to the release path

Use a protected signing group or the documented signing integration for the authorized staging configuration. Verify that the workflow can access that group only from permitted branches or builds. Check which upload key, signing certificate, provisioning profile, package or bundle identifier, and distribution account correspond to the target. Separate development builds and store submission steps so an ordinary test run cannot submit an artifact.

Check the variables and identity required for the selected platform before requesting the expensive build. A missing credential should produce a useful named prerequisite without echoing values. Keep signing files out of printed environment output and general artifacts. Separate changes to signing from changes to tests or app logic so a failure can be isolated and rolled back.

Inspect the output that would be distributed

Record artifact identity from the completed build rather than from the filename. Check the platform package identifier, version and build number, and signing identity through appropriate platform tooling. Retain a checksum and the source commit with the resulting artifact. For Apple targets, verify entitlement and provisioning consistency where applicable. For Android, distinguish APK and App Bundle distribution expectations.

Repeat a build from the same revision or compare a controlled rerun. Record the authorized test installation or validation channel and any unavailable device or publishing checks. Exercise a failed unit test and a missing signing group in staging. Verify no distribution step runs on either failure. An eventual submission should use the exact inspected artifact under the project's existing approval process.

References

Install this skill directly: skilldb add cicd-patterns-skills

Get CLI access →