Manage signing in the project
Apple credentials and Android signing are available to the pipeline. For an Android app already published on Google Play, import its original upload key.
You build new features with AI. MainPath prepares the path to iOS and Android builds – with tests, signing and a test version before you approve the next release.
The prepared pipeline follows your code. You decide which version goes to the store.
Tests and checks run against your code. If a job fails, use its log with your AI agent to work through the change.
The pipeline produces the builds. iOS is built on MainPath’s macOS machines; connected store accounts and signing credentials are part of the setup.
With linked store accounts, test versions go to TestFlight and the internal Play track. Check the app’s flows there before publishing.
After testing, start the manual release step. Store submission follows this process; the respective store decides on any required approval.
Apple credentials and Android signing are available to the pipeline. For an Android app already published on Google Play, import its original upload key.
Descriptions, screenshots and release notes for each language stay with the project. The pipeline uploads the content you have prepared.
For configured Flutter desktop targets, the pipeline builds the appropriate installers. Check which platforms your code and plugins support in your project.
Your Flutter app and backend can live in the same MainPath project. The interface and API grow from a shared project foundation, with the appropriate build and deployment steps for each component.
You provide Apple and Google accounts with the appropriate API access and connect them to the project.
Bundle ID, package name and signing must match the app. An existing Google Play app needs its original upload key.
One Flutter codebase does not replace device testing. Check permissions, native plugins and platform-specific features too.
Generated pipeline and environment files stay unchanged. Put your own values in documented custom files or MainPath configuration.
Start a Flutter project or let your agent check whether your existing app can be imported. Then keep building on the same project foundation.
Not for pipeline builds. MainPath provides macOS build machines. This is separate from your local development environment; local iOS development still follows Flutter and Apple’s requirements.
Yes, if the project is supported. Your AI agent checks the existing code and guides the import. For an app already in the stores, the existing identifiers and signing credentials must match.
No. With linked store accounts, the publishing flow first distributes builds to TestFlight and internal Play tests. You start the store release manually. Review and approval by the respective store remain separate.
No. Your Flutter app’s supported platforms and native features depend on your code, plugins and their configuration. MainPath prepares build and release flows for the targets configured in your project.
For configured desktop targets, the pipeline can build macOS, Windows and Linux packages. Signing, notarization and store access depend on the target platform and distribution route.