fastlane 2.241.1 Rolls Back produce API Key Support

On warm white, an orange return arrow loops back toward an earlier node on a dark blue software route. Two blue abstract image canvases, landscape and portrait, overlap at right. The blue MacDigest binocular mark sits at upper left.

A maintenance update in fastlane 2.241.1: rolling back a produce API-key-support change and adding screenshot-size recognition. Original conceptual illustration: MacDigest.

fastlane 2.241.1, published October 15, rolls back recently introduced App Store Connect API-key support in produce after maintainers reported two regressions. The patch also adds iPhone Duo screenshot sizes to deliver. For developers running release automation on a Mac or CI runner, the immediate check is how their produce steps authenticate.

What the rollback changes

The merged rollback reverses PR #30158, which added API-key support for create, enable_services and disable_services. It removes produce’s api_key and api_key_path options and its shared token-authentication helper. The tagged app-creation login and service lookup code again call Spaceship.login and select_team, restoring the username-based session path.

One regression report describes capability changes failing in 2.241.0 with an HTTP 409 error because a required capabilities relationship was missing. A separate proposed fix describes a crash when an action’s configuration lacked the new API-key options. That proposal was closed without merging; 2.241.1 ships the rollback.

Review the affected automation

If a lane adopted the new produce options in 2.241.0, review its configuration against the 2.241.1 options list before the next run. Check that the affected step can use the existing session-based authentication flow and select the intended developer team.

API-key options remain in the same release’s pilot and deliver code. Keep the review focused on the produce steps that changed; this patch does not remove API-key support throughout fastlane.

MacDigest has not tested the release against a live Apple account. Source review establishes what changed, but it does not confirm that a particular production lane will succeed.

Duo screenshot sizes arrive

The deliver update adds iPhone Duo screenshots at 1398 × 2034 pixels for the outer display and 2007 × 2853 for the inner display in portrait orientation. It also accepts the reversed dimensions for landscape images.

Apple’s screenshot specifications list the same dimensions and say Duo screenshots become required beginning April 2027 for apps built with the iOS 27.1 SDK or later. Teams preparing those submissions should check their screenshot assets alongside their build SDK. The new size support helps the upload workflow; the requirement’s SDK condition still matters.

Leave a Reply

Your email address will not be published. Required fields are marked *