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.
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.
With a connected store account, the pipeline uploads iOS builds to TestFlight. Try your changes before submitting a version for store review.
Signing and store uploads require the appropriate Apple developer access. MainPath does not replace membership of the Apple Developer Program.
Connect your store account and assign the correct bundle identifier. It must match the app you have configured.
For macOS, choose the Mac App Store or direct distribution. Developer ID signing and notarization have their own settings.
A successful build does not replace testing your app. Check features, permissions and platform-specific behavior before releasing.
The build machines are part of the automation. They are not an interactive Mac desktop or macOS workspace.
Create a supported app project or ask your agent to check whether your existing code is supported.
Add the appropriate store account, identifiers and signing and distribution settings.
The pipeline creates the build. Try the test version or package on the intended devices.
Start the appropriate manual release job. Store submissions still go through the provider’s review process.
Descriptions, screenshots and release notes stay with the project. Prepared uploads include the content you maintain.
The pipeline builds DMG packages for direct distribution. Enable Developer ID signing and notarization with the appropriate Apple credentials.
Start an app project and configure your Apple targets. MainPath handles pipeline builds; you decide when to test and release.
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.
No. The macOS machines run your project’s build jobs. They are not an interactive desktop or workspace with your own Xcode session.
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.
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.
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.