build number

Question

Created Sep ’17

Replies 3

Boosts 0

Views 12k

Participants 4

What are guidelines for numbering the build number? Should it just start with 0 and increment by one each time I archive a project for distribution?

Answered by KMT in 259465022

Your choice, just don't change the scheme once you commit.

If you start with 0.0, don't change later to 0.0.0, as an example.

Typically, tho major updates get a full digit up (1.0 to 2.0) and minor get a point change (1.0 to 1.1).

Users typically like it simple, so....don't burden them with long strings they need to ponder when doing housekeeping, reporting, etc.

I use 1.0, 1.1, 2.0, etc., but I don't bump/bump/bump when randomly archiving during testing, only when I'm headed for the store/distribution.

And finally, note there is a version number, build number and short build string, where some are used for the store and some are internal for the dev, team etc.

Be sure to also see TN2420: https://developer.apple.com/library/content/technotes/tn2420/_index.html

Boost

Answer 1

KMT OP

Sep ’17

Accepted Answer

Your choice, just don't change the scheme once you commit.

If you start with 0.0, don't change later to 0.0.0, as an example.

Typically, tho major updates get a full digit up (1.0 to 2.0) and minor get a point change (1.0 to 1.1).

Users typically like it simple, so....don't burden them with long strings they need to ponder when doing housekeeping, reporting, etc.

I use 1.0, 1.1, 2.0, etc., but I don't bump/bump/bump when randomly archiving during testing, only when I'm headed for the store/distribution.

And finally, note there is a version number, build number and short build string, where some are used for the store and some are internal for the dev, team etc.

Be sure to also see TN2420: https://developer.apple.com/library/content/technotes/tn2420/_index.html

1

Answer 2

u8nc OP

Sep ’17

If you're starting out, think like you've done 1000 apps and wished you had a system in distinguishing where each is at

I genarally make the version number that the customer sees with the Xcode major version is was prepared.

For the build number i choose the minimum deployment target.

Verion: ( 4.8 ) is my fouth iteration i did on Xcode 8

Build: ( 9.1.n) where 'n' was the build submitted to iTunes Connect, was for iOS 9.1 and above

The 'n' has to be altered every time you resbumit after rejecting your own binary or if Apple reject

It's a common technique in the Linux community, and you can do what you want. Diff'rent Strokes for Diff'rent Folks.

0

Answer 3

sykste OP

Jan ’22

Most of these responses are referring to Version numbering and not Build Numbers. VV.RR.PP VV = Version, RR = Release with version, PP = Patch or Fix within release.

Build numbers are often used to track builds of software independent of release, and it is important that Apple and other software distributors not INTERFERE with these numbering schemes, as many organizations track all platforms of revisions. These build numbers are also connected to Certifications. For example an FDA Validation may be connected to a particular build number. Also EMV certifications are connected to build numbers.

0