ASC CLI chases Fastlane parity with match
Rudrank Riyam is steering App Store Connect CLI toward local feature parity with Fastlane, especially its match code-signing workflow. Testing is still underway, making this a promising preview rather than a finished replacement.
The strategic bet is compelling: replace Fastlane’s Ruby-heavy mobile release stack with a focused, scriptable CLI without forcing teams to redesign their workflows.
- –Match-style certificate and provisioning-profile synchronization is the hardest parity target because it combines Apple portal access, encryption, shared storage, and keychain management.
- –App Store Connect CLI already covers builds, TestFlight, submissions, screenshots, metadata, analytics, and signing from the terminal or CI.
- –A credible Fastlane alternative could reduce dependency friction for teams standardizing on Go-based tooling and agent-driven workflows.
- –Production adoption will depend on proving multi-target signing, credential rotation, CI behavior, and failure recovery—not just matching command names.
- –Until the testing is complete, teams should treat the new release as an evaluation candidate and retain Fastlane as a fallback.
DISCOVERED
2h ago
2026-08-31
PUBLISHED
3h ago
2026-08-31
RELEVANCE
AUTHOR
rudrank