Re: iOS App Store Version vs Info.plist version?
Re: iOS App Store Version vs Info.plist version?
- Subject: Re: iOS App Store Version vs Info.plist version?
- From: Rick Mann <email@hidden>
- Date: Thu, 09 Apr 2015 16:28:37 -0700
> On Apr 9, 2015, at 16:11 , Quincey Morris <email@hidden> wrote:
>
> On Apr 9, 2015, at 15:53 , Rick Mann <email@hidden> wrote:
>>
>>> On Apr 9, 2015, at 15:52 , Mike Abdullah <email@hidden> wrote:
>>>
>>>
>>>> On 9 Apr 2015, at 23:41, Rick Mann <email@hidden> wrote:
>>>>
>>>>
>>>>> On Apr 9, 2015, at 15:30 , Mike Abdullah <email@hidden> wrote:
>>>>>
>>>>>
>>>>>> On 9 Apr 2015, at 23:28, Rick Mann <email@hidden> wrote:
>>>>>>
>>>>>>
>>>>>>> On Apr 9, 2015, at 15:26 , Mike Abdullah <email@hidden> wrote:
>>>>>>>
>>>>>>>
>>>>>>>> On 9 Apr 2015, at 23:02, Rick Mann <email@hidden> wrote:
>>>>>>>>
>>>>>>>> When submitting to the App Store, one can specify the "Store Version" as a field in iTunesConnect. If the build I associate with that new app version has a different version in the Info.plist, what will the user see when they either examine the IPA or if the app displays its own version string? Does the App Store re-write the Info.plist to show the "Store Version" number?
>>>>>>>
>>>>>>> Can you actually associate such a build? My understanding is Apple will only let you pick builds that match up version number-wise.
>>>>>>
>>>>>> Which is what I've seen suggested online. So, then, what is the point of having an editable version field in the App Store metadata UI?
>>>>>
>>>>> I figure so you can change your mind and up the version number mid-submission. e.g. you started off submitting version 1.2.1, but now 1.3 is ready to go, so decide to submit that instead.
>>>>
>>>> But if the bundle submitted must match, why not just pull from the submitted bundle?
>>>
>>> I don’t understand what you’re asking here. Does it even matter? :-)
>>
>> It's extra work that's prone to error. Apple makes me type in a version number when I create a new app version, but if I have to ensure that the bundle I upload matches that, then there's absolutely no point in making it something I can edit.
>
> I’m not sure I understand exactly what you’re referring to, either.
>
> You can have iTunes Connect records for *multiple* versions of your app at one time, and you can upload to any of those versions (subject to status restrictions, of course). The bundle version of the app you’re uploading will determine which iTunes Connect app record it gets uploaded to. Doesn’t seem redundant to me.
>
If the CFBundleShortVersionString in the bundle you upload has to match the number you specify in iTunesConnect, then there is no benefit nor point to having to redundantly specify the version number in iTunesConnect. Once you select an uploaded build to attach for submission, it can get the version number from that.
Unless what was said earlier, that the versions have to match, is not true. In that case, what's the utility in specifying one version in the iTunesConnect record and another in the uploaded build? I'm talking about the CFBundleShortVersionString. Apple seems to accept that string staying the same while the CFBundleVersion increments.
So, what's the point in redundantly entering the version string? I don't understand what you're saying, but I don't see how one can have multiple versions of a version.
--
Rick Mann
email@hidden
_______________________________________________
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