Fastlane
Fastlane is a part of the automation tool for the development and release process of the project. By converting to Fastlane.swift, we can now write our configuration using Xcode in Swift - the language we know and love from the world of iOS development. This document will mention some crucial parts of the pipeline.
The lane buildAndTest helps build and test the application with the configuration of the test scheme and test target defined in the Constant.swift file.
Example:
$ bundle exec fastlane buildAndTest
After running this lane successfully, it will generate the code coverage report.
See more:
As the developer team has many developers, it is recommended to synchronize the certificates and profiles across the team during the development process.
The fastlane match is here for sharing one code signing identity across the development team to simplify the codesigning setup and prevent code signing issues.
To synchronize the machine with the certificates and profiles, which are stored in a match repository, please use the following lanes:
syncDevelopmentCodeSigning |
syncAdHocStagingCodeSigning |
syncAdHocProductionCodeSigning |
syncAppStoreCodeSigning |
|---|---|---|---|
| Synchronize the Development match signing for the Staging build. | Synchronize the Ad Hoc match signing for the Staging build. | Synchronize the Ad Hoc match signing for the Production build. | Synchronize the App Store match signing for the Production build. |
Example:
$ bundle exec fastlane syncDevelopmentCodeSigning
$ bundle exec fastlane syncAdHocStagingCodeSigning
$ bundle exec fastlane syncAdHocProductionCodeSigning
$ bundle exec fastlane syncAppStoreCodeSigning
To register a new device and synchronize the new device across the development team, use the lane registerNewDevice and provide the device UDID along with the device name:
Example:
$ bundle exec fastlane registerNewDevice
To build and upload the application to distribution platforms, like Firebase or App Store Connect, please use these lanes:
buildStagingAndUploadToFirebase |
buildProductionAndUploadToFirebase |
buildAndUploadToAppStore |
buildAndUploadToTestFlight |
|---|---|---|---|
| To upload the Staging build and Staging dSYM file to Firebase. | To upload the Production build and Production dSYM file to Firebase. | To upload the Production build to App Store. | To upload the Production build to TestFlight. |
Example:
$ bundle exec fastlane buildStagingAndUploadToFirebase
$ bundle exec fastlane buildProductionAndUploadToFirebase
$ bundle exec fastlane buildAndUploadToAppStore
$ bundle exec fastlane buildAndUploadToTestFlight
See more:
Define the essential information to synchronize the certificates and profiles across the development team.
See more:
Contains the key/value pairs of constants used during the development and release process.
Contains the key/value pairs of environment variables used during the development and release process.
Build.swift helps build and sign the application. There are two main functions:
adHoc |
appStore |
|---|---|
Build and sign the application with the adHoc distribution and the environment parameter (staging or production) |
Build and sign the application with the appStore distribution. |
See more:
Distribution.swift is in charge of distributing the build to the distribution platforms, such as Firebase, App Store Connect, and Testflight.
See more:
The responsibility of Match is to synchronize the teams' certificates and profiles during the development process.
See more:
Technically, the debug Symbol file (dSYM file) is used to de-obfuscate stack traces from crashes on the production app. The dSYM files store the debug symbols for the application. Then services (like Crashlytics) use the dSYM files to replace the symbols in the crash reports with the originating locations in the source code. Hence, the crash reports will be more readable and understandable.
The Symbol helps process and upload dSYM file to Firebase. There is only one primary function:
uploadToCrashlytics |
|---|
Directly upload the built dSYM file to Crashlytics with the environment parameter (staging or production). |
It is recommended to use this function when the build configuration is Release Staging or Release Production. |
| See more: Debug Symbol File |
The Test helps build and test the application.
The Version manages the application's build number and version number.