Invalid Pre-Release Train. The train version '3.0' is closed for new build submissions

Question

LHealy OP

Created Feb ’16

Replies 5

Boosts 2

Views 39k

Participants 9

Hi,

We published an update to an existing app and it went through the review process and status changed to ready for sale, so it was then available for download in the store. The Version was 3.0 and the build was 2.0.26.

The development team realised there was an issue with the build and once they fixed the issue, they incremented the build to 2.0.27 and left the version at 3.0

We received the following errors when we tried to upload the new build.

"Invalid Pre-Release Train. The train version '3.0' is closed for new build submissions"

"This bundle is invalid. The value for key CFBundleShortVersionString [3.0] in the Info.plist file must contain a higher version than that of the previously approved version [3.0]"

I tried to check Apple documentation and this is a good resource

https:/

However it does not clarify if it is possible to increment only the build and use the same version number as the version which is currently "Ready for Sale" in the store. Or is it a requirement to increment the version number in this scenario.

Can this be clarified please?

Thanks,

Linda

Boost

Answer 1

bob133 OP

Feb ’16

Because version 3.0 is already available for sale (and thus "finished") , you can't release another 3.0, even if the build number has changed. Remember that most users care about the version number, not the build number. So you'll need to change your version number to 3.0.1 to communicate the change.

5

Answer 2

KMT OP

Feb ’16

Your very next upload should always have an incremented (CFBundleShortVersionString) version number such as 3.1, 4.0, etc.

2

Answer 3

regulr OP

Apr ’21

Getting the same issue with test flight...and it's really odd that this applies there. We want to release new builds under a single given version until it's considered stable.

2

Answer 4

Happo74 OP

Jan ’22

Honestly i find this behaviour as many others completely non-sense.... But since we have to comply.... You have to tell to yourself the mantra "this is the best way to proceed" lool.

3

Answer 5

Phootios OP

Nov ’22

I think you can upload as many builds as you want to a version, until you publish it. Then the next build should be to a new version.

1