fastlane/docs

Documentation issue: Add Apple App Store Connect API to the Continuous Integration page

rtolar opened this issue ยท 2 comments

The Fastlane docs list various ways that a continuous integration server can authenticate with Apple.

https://docs.fastlane.tools/best-practices/continuous-integration/#authentication-with-apple-services

Issues that I encountered with this documentation:

  1. The recommended approach is to create a dedicated Apple ID without 2FA and without the "account holder" role.
    I don't believe that this is supported by Apple any more.

There is a note here saying "Note: Apple announced that as of February 27th 2019, it is enforcing 2-factor authentication on developer Apple IDs with the "Account Holder" role."

However, as best I can tell, Apple is requiring 2FA for all roles, even if they are not "Account Holder" roles.

I was only able to get this working by creating a dedicated CI/CD login with the "Admin" role, and Apple forced 2FA to be enabled.

  1. There is no mention of the "App Store Connect API" method of authenticating with Apple on "Continuous Integration" page of Fastlane docs.

Yes, there is a separate page that describes the API approach ( https://docs.fastlane.tools/app-store-connect-api/ ), and it looks like a vastly better solution, and one that doesn't require 2FA. However, there's no mention of it all from the Continuous Integration page.

In my case, I've been using the 2FA approach for many months, and dealing with the periodic hassle of builds breaking and requiring manual 2FA re-authentications every few weeks.

I happened across this post in the Apple forums:
https://developer.apple.com/forums/thread/658765

Which then led me to discover the existence of this feature. This should be listed on the Continuous Integration page as the preferred option instead of the 2FA approach.

It seems like you have not included the output of fastlane env

To make it easier for us help you resolve this issue, please update the issue to include the output of fastlane env ๐Ÿ‘

Hi @rtolar !

I transferred your issue to the correct repository ๐Ÿ˜Š

I totally agree with you. I'll try to work on these changes when I free up some time, but otherwise if you (or anyone reading this) feels like picking up this task and open a PR, please by all means! Feel free to tag me to review your changes ๐Ÿค—

Thanks for your input, it's much appreciated @rtolar ! ๐Ÿ™Œ