Your app for AppleBuilt on macOS

You develop your app with AI. MainPath provides the macOS machines for pipeline builds, with signing and a clear path to test versions, stores or a direct download.

Packages for your configured platforms – Apple builds run on macOS

The next version of your iOS appTry it on devices first

With a connected store account, the pipeline uploads iOS builds to TestFlight. Try your changes before submitting a version for store review.

  • The iOS build runs on MainPath’s macOS machines
  • Apple credentials and signing are configured for the project
  • You start the manual release step after checking the build
How app publishing works

Before your first Apple buildPrepare the essentials

  • Your Apple team

    Signing and store uploads require the appropriate Apple developer access. MainPath does not replace membership of the Apple Developer Program.

  • Credentials and identifiers

    Connect your store account and assign the correct bundle identifier. It must match the app you have configured.

  • Choose your distribution route

    For macOS, choose the Mac App Store or direct distribution. Developer ID signing and notarization have their own settings.

  • Test on real devices

    A successful build does not replace testing your app. Check features, permissions and platform-specific behavior before releasing.

Development and buildsTwo tasks, one project

Your development environment

  • You edit the code yourself or with your AI agent.
  • Local iOS and macOS development follows the requirements of your tools and Apple.
  • You check whether the change works for your users.

The pipeline’s macOS machines

  • Prepared jobs build and sign your configured Apple targets.
  • Status, results and logs belong to the project’s pipeline run.
  • Uploads and release jobs use your connected credentials and configuration.

The build machines are part of the automation. They are not an interactive Mac desktop or macOS workspace.

From commit to Apple releaseYou approve the next step

  1. Prepare the project

    Create a supported app project or ask your agent to check whether your existing code is supported.

  2. Connect Apple credentials

    Add the appropriate store account, identifiers and signing and distribution settings.

  3. Build and test

    The pipeline creates the build. Try the test version or package on the intended devices.

  4. Approve distribution

    Start the appropriate manual release job. Store submissions still go through the provider’s review process.

Publishing belongs to the projectWith content and packages together

Keep store content together

Descriptions, screenshots and release notes stay with the project. Prepared uploads include the content you maintain.

Distribute your macOS app as a download

The pipeline builds DMG packages for direct distribution. Enable Developer ID signing and notarization with the appropriate Apple credentials.

Your next Apple updateWith a prepared build process

Start an app project and configure your Apple targets. MainPath handles pipeline builds; you decide when to test and release.

Questions about macOS build machines

Do I need my own Mac for the pipeline?

Not for pipeline builds. MainPath provides macOS build machines. Your local development environment is separate; local Apple development still follows the requirements of your tools and Apple.

Do I get a Mac desktop for interactive work?

No. The macOS machines run your project’s build jobs. They are not an interactive desktop or workspace with your own Xcode session.

Can I distribute macOS apps outside the store?

Yes. The pipeline builds DMG packages for direct distribution. With the appropriate Apple credentials and Developer ID option enabled, they are signed and notarized. Without that setup, the packages are unsigned.

Desktop publishing in detail

Is my app public immediately after upload?

No. Test distribution, manual release and store review are separate steps. You need your own developer accounts and complete app information. The relevant store decides whether to approve the submission.

Can I edit the generated pipeline myself?

Generated files such as .gitlab-ci.yml are maintained by MainPath and must remain unchanged. Use the documented configuration options and custom files; discuss additional automation with support.

Pipelines and releases

Thank you for your request

We have received your request and will get back to you as soon as possible.

Would you like to talk to us directly?

Choose a time here for an introductory call with Robin.

Open the calendar in a new tab