Question 131631 in Xcode Question posted in
Whether you're new to Xcode or an experienced developer, our archive has everything you need to know about this integrated development environment (IDE). From basic functionalities to advanced features, our archive covers a wide range of Xcode-related questions and answers. Browse our archive now and find solutions to your Xcode questions, and take your app development skills to the next level

Why does my Xcode archive version number differ from the build version number?

I’ve been working on this React-Native project for many years and with this latest version (305) the build number in the archive is showing as 5, not 305. I’m not sure what I changed. See the general tab setting here in the attached image. Why does this not match?

Image top half: info.plist
Image bottom half: archive window

xcode example image

Tags:

2

Answers


  1. Chosen as BEST ANSWER
    0

    I changed the version to 306 and made another archive and the number was correct. Changed it back to 305 and archived, and it was correct. I guess this was a simple glitch. enter image description here


  2. 0

    The problem is that your version value is incorrect. You are to supply a version string, which is a string (not a number) of the form:

    MAJOR.MINOR

    or

    MAJOR.MINOR.PATCH

    These are not decimals. The major, minor, and patch values are all (string representations of) integers. Thus, for example, "1.34" is much bigger, not smaller, than "1.4" — because 34 is much bigger than 4.

    If you were numbering these versions correct, you would never in a million years have gotten to a major version as big as 305.

    When you submit a new version to TestFlight, you increment the other number, the Build, which is an integer. You typically increment the Version in some way only when you release a new version in the app store.

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search