Files

T

alexandrev-tibco 95a1e3a133 fastlane: lanes submit y status

submit envia a review una build ya subida: la 2.0.1 build 66 ya estaba en
TestFlight, y release habria reconstruido mientras publish nunca envia.
Distribucion automatica (AFTER_APPROVAL) y sin tocar screenshots, que se heredan.

status lista el estado de cada version en App Store Connect. Sirvio para
confirmar que la 2.0.1 quedo en AFTER_APPROVAL y no en MANUAL como la 2.0.
Ojo: asc_api_key devuelve el hash de opciones de fastlane, no un token de
spaceship; hay que construir el token aparte.

Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012Ks8uUcMA9mjypVK7F2Pkt

2026-08-07 11:10:22 +02:00

1.4 KiB

Raw Blame History

fastlane documentation

Installation

Make sure you have the latest version of the Xcode command line tools installed:

xcode-select --install

For fastlane installation instructions, see Installing fastlane

Available Actions

iOS

ios beta

[bundle exec] fastlane ios beta

Push a new beta build to TestFlight

ios status

[bundle exec] fastlane ios status

Show the App Store state of each version (review status, release type)

ios submit

[bundle exec] fastlane ios submit

Submit an already-uploaded build for App Store review (automatic release)

ios refresh_dsyms

[bundle exec] fastlane ios refresh_dsyms

Download processed dSYMs from App Store Connect and send them to Crashlytics

ios publish

[bundle exec] fastlane ios publish

Upload metadata + localized screenshots for an existing TestFlight build (no rebuild, no submit)

ios release

[bundle exec] fastlane ios release

Push a new release build to the App Store

This README.md is auto-generated and will be re-generated every time fastlane is run.

More information about fastlane can be found on fastlane.tools.

The documentation of fastlane can be found on docs.fastlane.tools.

1.4 KiB Raw Blame History