wkkim
March 22, 2018, 10:23am
1
this is a origin values related with bundle version in Info.plist file.
<key>CFBundleShortVersionString</key>
<string>1.0</string>
<key>CFBundleVersion</key>
<string>10</string>
I did export an achived app with Xcode on local mac.
<dict>
<key>bundle-identifier</key>
<string>com.knowre.ios.testingci.qa</string>
**<key>bundle-version</key>**
**<string>1.0</string>**
<key>kind</key>
<string>software</string>
<key>title</key>
<string>TestingCI</string>
</dict>
but when deploy an Xcode archive to Amazon S3 using bitrise.io , bundle-version’s value is different with above.
<dict>
<key>bundle-identifier</key>
<string>com.knowre.ios.testingci.qa</string>
**<key>bundle-version</key>**
**<string>10</string>**
<key>kind</key>
<string>software</string>
<key>title</key>
<string>TestingCI</string>
</dict>
actually, we need this version information, 1.0(CFBundleShortVersionString).bitrise.io , steps-xcode-archive?
Hi @standwally ,
Which step you’re referring to here? Could you please link the related build?
wkkim
March 23, 2018, 1:02am
3
Thanks @standwally !
Can you please enable Support Access on the Settings tab of the app? It’d help a lot with debugging!
Checked the build, and it seems the 10 value is the Build Number, which is actually called the bundle-version. The 1.0 you’re referring to is CFBundleShortVersionString, which is the user facing version.
Ahh, ok, I see you already mentioned this.
I did export an achived app with Xcode on local mac.
and plist information is below.
please check the bundle-version’s value.
Can you please list the steps you did, to get the info.plist with bundle-version 1.0 instead of 10?
One more info / note: this install Info.plist is generated by the amazon-s3-deploy step, not the Xcode Archive step.
bundle-version is read from the .ipa, from the CFBundleVersion param included in the IPA: https://github.com/bitrise-io/steps-amazon-s3-deploy/blob/706427b2927d9a8dffdfe341e086ae4f67041803/gen_plist.sh#L31
wkkim
March 27, 2018, 2:31am
9
These are achiving steps using Xcode.
wkkim
March 27, 2018, 7:51am
10
And additionally, we need a both CFBundleShortVersionString and CFBundleVersion.
Could you add these things on steps-amazon-s3-deploy?
https://github.com/bitrise-io/steps-amazon-s3-deploy/blob/706427b2927d9a8dffdfe341e086ae4f67041803/gen_plist.sh#L31
Got it, thanks for the report!
We’ll schedule a check on the step, to see whether it follows the related official Apple guidelines.
Feel free to send a PR into the step if you have some time! Note: you can also use your own fork of any step, via the git:: reference: https://devcenter.bitrise.io/bitrise-cli/steps/#special-step-sources
If you’d have any questions just let us know!
wkkim
March 29, 2018, 2:20am
12
Thank you.
Eventually, in the long run we will use a bitrise.io not bitrise CLI.
So, we send a pull request for adding CFBundleShortVersionString info.https://github.com/bitrise-io/steps-amazon-s3-deploy/pull/21
Please review.
1 Like
Thanks, we’ll review it ASAP! Might take some time as we’ll dig into the related docs, the step wasn’t updated for a long time now, an update might be due now git:: ref method (https://devcenter.bitrise.io/bitrise-cli/steps/#special-step-sources ), and of course we’re happy to answer any questions
wkkim
March 30, 2018, 6:11am
14
Thank you.
We looked for another way to deal with CFBundleShortVersionString info.
1 Like
Glad to hear you found a solution - we’ll try to review the PR too as soon as possible
Hey @standwally !
The new version of the step is out now, not with the exact changes you’ve made because bundle-sort-version is not an official field of Apple in the manifest.plist.
However you were right and we used version in bundle-version field instead of the short version field. It is fixed by now
1 Like
Thanks @tamaspapik ! Could you please link the related Apple docs?
It is not an Apple docs BTW, this was my main reference:
Xcode also generates plist matching to the scheme above.
1 Like
In the meantime you can use your own version if it’s important, via the 
