Skip to content

Codemagic

Codemagic runs mobile build and release steps on hosted machines.

Visit Codemagic

What work can Codemagic repeat for you?

Connect the code project and define which steps the hosted machine should run. A build workflow can check that the app can be packaged. A later workflow can sign a build and send it to a testing destination.

Signing uses credentials tied to your app so the platform can identify who prepared the build. Set up the store account and signing separately from the first build check.

What counts toward the Codemagic bill?

Codemagic documents 500 free macOS M2 build minutes each month for personal accounts. Team pay-as-you-go builds are charged per machine minute, and paid machines and additional parallel builds can affect the bill.

Check the machine type and who owns the account before estimating a monthly cost.

What should your team keep outside Codemagic?

Keep the app source and build instructions, such as codemagic.yaml, in a repository your team controls. Save release files you need because hosted artifact retention varies by plan. Keep signing credentials under your team’s control.

Where should an automated build stop on a first trial?

Sketch a fictional app and a build-only workflow with no accounts or connections.

  1. Choose the starting state
    Write down the pretend code version and the file the build should produce.
  2. Write the expected result
    Draw a check for build success and an arrow to the saved file.
  3. Name the stop point
    Leave publishing out of the first workflow. If the build fails, stop before signing or distribution.