Skip to content
All documentation

Versions and build numbers

Set the version customers see and the build number every upload needs, both next to the build button in Build.

Updated Oct 11, 2026

The Build window's Version field at 1.0.0 and Build number at 1, under the APK and App Bundle choice
Version is what people see; the build number must go up with every store upload.

The two numbers

VersionBuild number
Example1.2.014
AndroidversionNameversionCode
iOSCFBundleShortVersionStringCFBundleVersion
Customers see itYesNo
Who sets itYou, in Build or app.jsonFluxNative, counting up
Must go upFor each store releaseFor every upload

Steps

  1. Click Build. The version and the next build number sit next to the build button.
  2. For a new release, type a version of one to three numbers, such as 1.3.0.
  3. If the store already has higher build numbers, type a higher one.
  4. Start the build. The version is saved to app.json only once the checks pass.

Or ask the assistant:

Bump the app version to 1.3.0.

Good to know

  • Android and iOS count build numbers separately. A number is never reused, even after a failed build.
  • A number at or below an earlier one is refused before the build starts, as the stores would refuse it.
  • A store says the number was used? Set a higher one in Build and build again.

Native builds overview · Fix a failed build

Did this page help?

Which app will you launch first?

Start with a prompt, images, or Figma. No credit card required.

Start building Explore plans

Taking a little longer than usual…

Loading FluxNative