• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: iOS App Store Version vs Info.plist version?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: iOS App Store Version vs Info.plist version?


  • Subject: Re: iOS App Store Version vs Info.plist version?
  • From: Graham Cox <email@hidden>
  • Date: Fri, 10 Apr 2015 10:25:51 +1000

> On 10 Apr 2015, at 9:28 am, Rick Mann <email@hidden> wrote:
>
> but I don't see how one can have multiple versions of a version


Rick, we had an issue related to this recently. I’m not sure if it helps you, but it seems to me that you have two “kinds” of version numbers - there’s a public-facing one, which is what your users think of as your version number, and then there’s an internal number which is used by you as a developer, and by iTunesConnect, to identify the binary.

Say you want to release a new version of an app - it’s going to be version 1.5. That’s the public facing number, the one you have prepared all your release material about, etc. You submit to the app store, but then discover a last minute problem and need to upload a new version, so you pull the submission. You can’t or don’t want to change it being released as “1.5”, but iTunes and you need to know that it’s different. So you bump or otherwise modify the build number. In fact, you *MUST* modify this number or iTC will refuse to allow you to upload a new binary to replace your previous submission - it used to permit this, overwriting the old version, but now it doesn’t - it has to be able to see a new, uniquely identifiable binary. Once you’ve uploaded something to iTC as a submission, even if you later pull that submission, it remains “known” to iTC, so you must bump the build number to upload a fresh version. In the iTC interface, you can see all the uploaded binaries and pick the one that you end up submitting for review/release. This is all part of the new, enhanced, much harder to use iTunesConnect that was rolled out a few months ago.

Build numbers end up as the CFBundleVersion, but the public facing version number end up as the CFBundleShortVersionString. We think of it as developer version number (i.e the “true” version number) and the marketing version number. The Finder’s Get Info panel only displays the marketing number, but in fact it’s the other one that’s more important really.

—Graham



_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


References: 
 >iOS App Store Version vs Info.plist version? (From: Rick Mann <email@hidden>)
 >Re: iOS App Store Version vs Info.plist version? (From: Mike Abdullah <email@hidden>)
 >Re: iOS App Store Version vs Info.plist version? (From: Rick Mann <email@hidden>)
 >Re: iOS App Store Version vs Info.plist version? (From: Mike Abdullah <email@hidden>)
 >Re: iOS App Store Version vs Info.plist version? (From: Rick Mann <email@hidden>)
 >Re: iOS App Store Version vs Info.plist version? (From: Mike Abdullah <email@hidden>)
 >Re: iOS App Store Version vs Info.plist version? (From: Rick Mann <email@hidden>)
 >Re: iOS App Store Version vs Info.plist version? (From: Quincey Morris <email@hidden>)
 >Re: iOS App Store Version vs Info.plist version? (From: Rick Mann <email@hidden>)

  • Prev by Date: Re: iOS App Store Version vs Info.plist version?
  • Next by Date: Re: Proper switching and casing.
  • Previous by thread: Re: iOS App Store Version vs Info.plist version?
  • Next by thread: No NSProgress notes
  • Index(es):
    • Date
    • Thread