Build number flag on iOS is wrong

[hard dagger]

I am trying to work with CICD pipeline using fastlane. For Android I am using version code, however for iOS I am struggling to get build numbers to work properly.
The only thing available is the option --build-number as far as I can see and that appends to the app version instead of being it's own number.
Testflight and other common tooling seem to expect that this is a simple integer whereas tauri seems to unexpectedly append this:
--build-number <BUILD_NUMBER> Build number to append to the app version => 0.1.0.<BUILD> vs just <BUILD>.
Used as follows: npm run tauri ios build -- --build-number #{build_number} --export-method release-testing

Is there any way for me to still easily define my own build number? In a CICD environment?
Cheers!

[arctic granite]

there aren't any hard requirements on how the build number works so the --build-number behavior isn't "wrong" and i've seen it being used in app store publishing at work.
If not set it used to default to a timestamp in older versions for example.

Since 2.5.0 tauri also has a bundle.iOS.bundleVersion config that directly sets the respective plist value. No idea why the reference docs don't show that, seems like the doc update logic is broken. It's mentioned in the guide though https://v2.tauri.app/distribute/app-store/#build-and-upload

[hard dagger]

That's exactly what I needed and also works similarly to android so that's a welcome change.
I'll be updating from 2.4 to 2.5 today then and testing it out, much thanks for the quick answer!

there aren't any hard requirements on how the build number works so the --build-number behavior isn't "wrong" and i've seen it being used in app store publishing at work.
If not set it used to default to a timestamp in older versions for example.
For sure, you can put anything you want, but a lot of tooling does "expect" it to be an integer (which can then be incremented). For example firebase will show 0.1.0 (0.1.0.1) instead on android it will show 0.1.0 (1). Some tools will try to increment a string and fail but as long as I can set it manually, I am happy.
I believe the apple documentation hints at incrementing as well.

[hard dagger]

Documentation mentions ios but it seems to be iOS, made a PR for docs https://github.com/tauri-apps/tauri-docs/pull/3296

[hard dagger]

I'll be updating from 2.4 to 2.5 today then and testing it out, much thanks for the quick answer!
@arctic granite seems updating broke iOS simulator support: https://discord.com/channels/616186924390023171/1374656770668236860

[arctic granite]

well, feel free to open an issue if you think the behavior should change in an upcoming major. I for one don't care either way (and also won't work on it).