TestFlight Version Numbers – Understanding and Management

appleiosversioning

If I update an iOS app as a result of tester feedback during TestFlight, should I be updating the "marketing" version number, or just the build number?

My current (initial) version number is X.Y.Z where Z is currently 0 and X.Y are out of my control (because they relate to the version of the upstream non-iOS product that my port is based upon). My preference is to keep the .Z part for "public" releases and use the build number to indicate releases in between.

What I don't know is whether doing so affects the way that Apple handle the app.

Does it make a difference if those updates are just bug fixes, or feature enhancements?

Best Answer

Every release to customers should have a new version number. Every release to testers should have a new build number. Customers will think something is wrong if version numbers are missing, so a sequence of version numbers could be for example 1.3.0, 1.3.1, 1.3.2, 1.4.0 etc.

Related Topic