[Documentation](https://fluxnative.app/docs) / Build for devices

# Versions and build numbers

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

![The Build window's Version field at 1.0.0 and Build number at 1, under the APK and App Bundle choice](https://fluxnative.app/guide-media/versions-and-build-numbers.5e0f4aaf.webp)

Version is what people see; the build number must go up with every store upload.

## The two numbers

|  | Version | Build number |
| --- | --- | --- |
| Example | `1.2.0` | `14` |
| Android | `versionName` | `versionCode` |
| iOS | `CFBundleShortVersionString` | `CFBundleVersion` |
| Customers see it | Yes | No |
| Who sets it | You, in **Build** or `app.json` | FluxNative, counting up |
| Must go up | For each store release | For 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.

## Related

[Native builds overview](https://fluxnative.app/docs/builds-overview) · [Fix a failed build](https://fluxnative.app/docs/build-failures)

Previous: [iOS certificates and profiles](https://fluxnative.app/docs/ios-signing) · Next: [Install and test on a device](https://fluxnative.app/docs/install-on-device)

---

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

Page: https://fluxnative.app/docs/versions-and-build-numbers