3.2.1

Updated description, to clarify expected private key format:

https://URL/TO/AuthKey_[KEY_ID].p8 or file:///PATH/TO/AuthKey_[KEY_ID].p8

3.2.0

Export APP_STORE_CONNECT_API_KEY_PATH, PILOT_API_KEY_PATH, PILOT_USERNAME, and PILOT_PASSWORD to support Apple service authentication via Bitrise Apple Service connection for more Fastlane tools.

Thanks @knox and @danielsinclairtill for the contribution!

3.1.0

Added support for app-specific password provided by Apple ID connection configured on Bitrise. app-password is no longer needed to be provided as a Step input, in case Apple ID connection is set up and it contains app-specific password.

3.0.1

Fixed an issue that prevented logging in with accounts that have not enabled 2FA yet.
Example error:

Need to acknowledge to Apple's Apple ID and Privacy statement. Please manually log into https://appleid.apple.com (or https://appstoreconnect.apple.com) to acknowledge the statement.

3.0.0

Added support to use (API key) connection. There are two types of Apple Developer connection you can enable on Bitrise: one is based on an API key of the App Store Connect API, the other is with an Apple ID (session-based). API Key will now be used by default if there is a connection configured for the given app. Using an API key will disable prechecking in-app purchases when using the deliver action, as that is not available through the API.

For Apple ID, now we are also passing the username/password/app-specific password in addition to the session (FASTLANE_SESSION) as they are required by the Fastlane deliver action.

If a valid connection or authentication-related inputs are found, Fastlane Apple authentication-related environment variables that are already set may be overridden. To prevent this set Bitrise Apple Developer Connection (connection) input to off and leave authentication-related inputs empty. The affected Environment Variables include DELIVER_USERNAME, DELIVER_PASSWORD, FASTLANE_SESSION, FASTLANE_APPLE_APPLICATION_SPECIFIC_PASSWORD, DELIVER_API_KEY_PATH and PRECHECK_INCLUDE_IN_APP_PURCHASES.

Added the Bitrise Apple Developer Connection (connection) input. The default behavior is the following: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication. Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.
Available options:
- automatic: Use any enabled Apple Developer connection, either based on Apple ID authentication or API key authentication. Step inputs are only used as a fallback. API key authentication has priority over Apple ID authentication in both cases.
- api_key: Use the Apple Developer connection based on API key authentication. Authentication-related Step inputs are ignored.
- apple_id: Use the Apple Developer connection based on Apple ID authentication and Application-specific password Step input. Other authentication-related Step inputs are ignored.
- off: Do not use any Apple Developer Connection. Only authentication-related Step inputs are considered.

Migration guide

• In case your build did not use or require any kind of Apple authentication: no action needed
• To migrate to the API key-based authentication from Apple ID-based authentication:
  • Create a new key with the correct role (App Manager/Admin may be needed for the deliver action): https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api
  • Set the Bitrise Apple Developer Connection (connection) input to api_key to use connection or to off to use Step inputs.
  • Set up an Apple Developer connection or configure API Key: URL and API Key: Issuer ID inputs.
  • Remove any set Fastlane authentication Environment Variables: FASTLANE_USER, FASTLANE_PASSWORD or other as they are no longer needed.
• If you used the Apple Developer connection with Apple ID based authentication (the only one available before 3.0.0 release), and wish to continue doing so:
  • If no API key-based connection is set up, no action is needed. To make sure that the app-specific password is set up, continue with the next steps.
  • Select apple_idfor the Bitrise Apple Developer Connection (connection) input.
  • Set the Apple ID: Application-specific password input as it is not yet available from the connection.
  • Remove any authentication-related Environment Variables: FASTLANE_USER (DELIVER_USERNAME), FASTLANE_PASSWORD (DELIVER_PASSWORD) as they are no longer needed. Please check that the Apple Developer connection contains valid credentials.
• To continue using API-key or Apple ID-based authentication that was set using Environment Variables, Fastlane CLI attributes or actions, (without using the available inputs or Apple Developer connection) set Bitrise Apple Developer Connection (connection) input to off and leave authentication-related inputs empty.

2.7.4

Fixes the issue of setting FASTLANE_SESSION env var for the Fastlane command.

2.7.3

Update broken and invalid links in the step.yml.

2.7.2

Pull new version of devportalservice package:

• Validate Apple Developer Connection (expiry).
• Expose FASTLANE_SESSION only for the fastlane command.

2.7.1

Updated description.

2.7.0

Step now can handle new bundler version lock files, gems.locked.