Understand version versus build number, set EAS to auto-increment builds, and stop App Store Connect and Google Play rejecting your uploads.
Apple won't take my new build, says the version must be higher. Fix it
How it works
- Read the upload error: Vovy reads the failed submit log and explains it: Apple and Google refuse any build number they have seen before.
- Explain version vs build: A card shows the difference: version is what users see, like 1.2.0. The build number is an internal counter that must always go up.
- Turn on remote versioning: Vovy sets appVersionSource to remote and autoIncrement to true in eas.json, so EAS tracks and bumps the build number for you.
- Sync with the stores: Vovy runs eas build:version:set to start above the highest number already in App Store Connect and Google Play.
- Rebuild and resubmit: Vovy builds and submits again. Uploading to the stores is publishing, so it asks, then confirms the new build appears.
What you provide
- Your Expo project
- Access to App Store Connect or Play Console
What you get
- A fixed upload
- Auto-incrementing build numbers
- A clear rule for version numbers
FAQ
Do I have to change the version users see?
Not for every build. Bump the version when you release something new. The build number bumps every upload.
Is the Android versionCode the same thing?
Yes, versionCode is Android's build number and must also go up with every upload.
Will this reset my TestFlight testers?
No. Testers just see the newer build appear in TestFlight.
Related tasks
All tasks