Files

Anatoliy f6f9764811 fix(ios): derive TestFlight build number from App Store Connect

The beta lane took the build number from pubspec (FLUTTER_BUILD_NUMBER).
Re-running CI on the same commit re-submitted an already-taken build
number and failed with 409 ENTITY_ERROR.ATTRIBUTE.INVALID.DUPLICATE
(run 2045: build 157 was already on TestFlight).

Now the lane queries the latest TestFlight build for the current
marketing version (falling back to the pubspec value when nothing was
uploaded yet) and uploads latest + 1, so retries can never collide.

2026-10-28 11:10:22 +03:00

.env.default

feat(fastlane): complete

2025-05-12 12:31:35 +03:00

Appfile

feat(fastlane): add fastlane

2025-05-12 12:04:51 +03:00

Fastfile

fix(ios): derive TestFlight build number from App Store Connect

2026-10-28 11:10:22 +03:00

README.md

feat(fastlane): complete

2025-05-12 12:31:35 +03:00

report.xml

fix: testflight

2025-07-28 13:58:48 +03:00

README.md

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

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.