Mohamed Boudra f4a4e0c25c fix(ios-release): submit each iOS build to its own App Store version ...

The submit_review fastlane lane identified the just-uploaded build by
CFBundleVersion alone. In this project the production iOS profile resets
the build number per marketing version, so every release sits at build 2
and Spaceship::ConnectAPI::Build.all returns the whole TestFlight history.
The .find call picked an arbitrary match, which is how 0.1.76's binary got
attached to the 0.1.75 App Store version slot and submitted for review
under the wrong label.

The release workflow now forwards app_version and app_build_version from
the build_ios outputs into the fastlane step as env vars, and the Fastfile
filters builds by marketing version plus build number to pin the exact
binary. The standalone resubmit workflow takes the same identifiers as
optional workflow_dispatch inputs; with both unset it falls back to "most
recently uploaded iOS build" so manual reruns still work.

Pinning fastlane in the Gemfile to lock the Spaceship behavior this lane
depends on.

2026-05-16 16:46:10 +07:00

..

Appfile

Auto-submit iOS builds for App Store review via fastlane

2026-04-23 21:36:35 +07:00

Fastfile

fix(ios-release): submit each iOS build to its own App Store version

2026-05-16 16:46:10 +07:00