fastlane and Azure DevOps - Apple App Store CI extensionBy Akila Iroshan
In this brief article, we will go through the authentication options available in Azure DevOps - Apple App Store CI extension.
fastlane is a tool for mobile developers to automate deployments and releases for their iOS and Android apps. It can handle tasks like generating screenshots, dealing with provisioning profiles/code signing, and releasing applications. Following fastlane documentation, deployment/release scripts can be automated for mobile projects and save valuable time!
Additionally, fastlane has support for CI integrations such as CircleCI, Jenkings, Travis CI, Azure DevOps, etc.
Azure DevOps “Apple App Store” CI extension
Apple App Store is such extension which is using fastlane, available in Azure DevOps to configure iOS deployment/release workflows. With this extension, you will be able to configure tasks, such as TestFlight release, App Store release, App Store Promote, etc in Azure DevOps.
To use Apple App Store extension tasks, you need to create Apple App Store Service Connection in Azure DevOps to connect with Apple App Store Connect.
From early 2021 Apple made it required to have two-factor(2FA) for Apple IDs. This affected iOS CI automation pipeline since during releases it required manual intervention if you configured the Apple App Store service connection in the usual way. Hence, in this article, we are looking for a recommended way of authenticating with Apple App Store Connect by fastlane.
Authenticating with Apple App Store Connect
There are 4 ways to connect to Apple services in fastlane documentation, but there are two Apple App Store Service Connection.
- Basic Authentication
Apple ID credential is used in this method. Since 2FA is enabled for AppleIDs, in this method, we have update fastlane Session from time to time when it is expired. ☹
- Token Based Authentication
This is the recommended method by fastlane. Here App Store Connect API key is used for authentication. However, it does not support all the fastlane features yet. Check out App Store Connect API documentation.
To Configure the Apple App Store service connection with this method first you need to generate the App Store Connect API key and use key ID, Issuer ID, and Key Content in Apple App Store service connection wizard.
Generate App Store Connect API key
- Log in to App Store Connect from a user with Account Holder permission
- Select Users and Access
- Select the API Keys tab
- Click Request access/Generate API Key
- Enter a name for the key. The name is for your reference
- Under Access, select the role “App Manager” for the key
- Click Generate.
Apple App Store Service Connection wizard
You can grab all three necessary information from the UI.
You can grab all three necessary information here.
- Issue ID
- Key ID
- Click “Download API Key” to download your API key. (Note: The download link appears only if the private key has not yet been downloaded. Apple does not keep a copy of the private key. You can download it only once.)
Enter above information in Apple App Store service connection wizard. Key content needs to be converted to base64 format when adding it to the wizard.
Then you can work on the rest of the iOS CI configuration with this service connection!