Automatic build number is always set to 1

[mostafaAbdelazim]

If you are looking for help, please confirm the following...

• I confirm I have searched the Docs, Codemagic Sample Projects, and GitHub Discussions.
• I confirm the software versions on my local computer match the ones in CI environment (e.g. Xcode version, Gradle version). See here
• I confirm I am able to do a fresh clone of the repository and build the project on my local computer.

Which mobile framework are you using?

Flutter (Dart)

Steps to reproduce

Add this script to prebuild script

scripts:
- name: Get the latest build number
script: |
LATEST_BUILD_NUMBER=$(app-store-connect get-latest-testflight-build-number $APP_APPLE_ID)
cd ./ios
xcrun agvtool new-version -all $(($LATEST_BUILD_NUMBER + 1))

Expected results

i would expect the new build number to be LATEST_BUILD_NUMBER + 1

Actual results

Found build number 4 from TestFlight version 1.0.2
Setting version of project Runner to:
1.

Also setting CFBundleVersion key (assuming it exists)

Updating CFBundleVersion in Info.plist(s)...

Updated CFBundleVersion in "Runner.xcodeproj/../Runner/Info.plist" to 1

Build id (optional)

65717eecbe7b02f1e859a4e3

[dtrdic]

Hey @mostafaAbdelazim, you need to add the logic inside build arguments and not in the pre-build script, something like this
--build-number=$(($(app-store-connect get-latest-testflight-build-number "$APP_ID") + 1))

you can also use a built-in variables like PROJECT_BUILD_NUMBER or BUILD_NUMBER

--build-name=1.2.$PROJECT_BUILD_NUMBER --build-number=$(($PROJECT_BUILD_NUMBER + 1))

The PROJECT_BUILD_NUMBER variable is a built-in environment variable that represents the current build number of your project.
It is automatically incremented with each new build of your app.
image

Also make sure that Info.plist file has the following string along with their key values

<key>CFBundleShortVersionString</key>
<string>$(FLUTTER_BUILD_NAME)</string>
<key>CFBundleVersion</key>
<string>$(FLUTTER_BUILD_NUMBER)</string>

[mostafaAbdelazim]

Working with PROJECT_BUILD_NUMBER seems to be enough for the task, Thank you @dtrdic,
Is the official docs outdated ? I followed this section with the pre-build script

[dtrdic]

awesome @mostafaAbdelazim, i'm glad the issue has been resolved!
No, it's still valid, but for the yaml configuration, I agree we should clarify a little bit better in the docs, I'll make sure to update it accordingly..Cheers