Appcircle is a mobile CI/CD platform that provides a fully automated environment to build and deploy apps, which also supports fastlane for build automation.
With Appcircle, you can automate your build and signing processes with the flexible workflow structure and you can also use fastlane as a workflow step within the build workflows. To use fastlane, Appcircle expects the presence of a fastfile in your repository.
Creating a Build Profile to Connect Your Repository with a Fastfile
In Appcircle, a build profile contains the build workflows and the configuration of an app per target platform. (i.e. separate for iOS and Android).
- To create your first build profile, go to the "Build Module". (The first item on the left menu) and click on the orange "Add New" button on the top right of the screen.
- In the next screen, enter a name for your build profile and select the target operating system (iOS or Android) and the target platform (Obj-C/Swift, Java/Kotlin, React Native and Flutter projects are supported). If you have two different targets in your project for iOS and Android, you need to create two separate profiles. This allows you to manage separate build workflows for different operating systems.
- Once created, click on the build profile to connect your repository that contains a fastfile. You can connect private and public repositories on GitHub, Bitbucket and other compatible git providers. You can authorize Appcircle to connect to your cloud repository provider account. This will allow you to use auto-build your project with hooks.
- The build configuration has different flows for iOS and Android and the projects are configured on a branch basis. You can have different configurations for different branches and you can build any of your commits (assuming that they are compatible with the current configuration).
- You can use fastlane with the signing configuration defined in the lane or you can configure your build to use Appcircle centralized code signing as an alternative to fastlane match.
Adding fastlane to the Appcircle Build Workflow as a Step
- A workflow in Appcircle is a ladder of steps taken to build your applications. Each step has a different purpose and the workflow can be customized by modifying step parameters and inputs, running custom scripts or re-ordering steps.
- To utilize fastlane in your builds, open the workflow editor and add the "fastlane" step after the "Git Clone" step. If you want to run a specific fastlane command, you can add a "Custom Script" step anywhere after the fastlane step.
- Once added, click on the fastlane step to configure it. Fastlane is easy to use with Appcircle just with two options.
- The "Fastlane Directory" option is used to specify the fastfile path . If you keep your fastfile in its default location, it is automatically used without the need to change this field.
- With the "Fastlane Lane" option, you can specify which lane to use.
- Once everything is set up, press Save to save your step configuration. Then you can configure and run your build just like any other app.
Appcircle also supports building and signing the app independently with the "Build" and "Sign" steps in the workflow. These steps can be used in parallel with fastlane.
Running the Build Workflow
To run the build workflow that includes the fastlane step, you can start a manual build or trigger an automatic build. The full output of the fastlane execution can be viewed in the build log in real-time or after the build.
Deploying the Build Output
You can use fastlane to deploy the built apps to the supported third-party services or you can use the Appcircle Distribute module to share the app with the testers or send it to the public app stores.
For more information, screenshots, and support, please refer to the Appcircle documentation.