Yes, the CFBundleVersion will change that “internal version” number. It is like the “version code” on Google Play. It is just a way to indicate what is the newer version.
For release purposes, the important is to set the CFBundleShortVersionString as Rob mentioned.
So, in summary:
iOS Android
CFBundleVersion = Version code
CFBundleShortVersionString = Version name
Hi guys,
According to the engineers, this has been resolved in recent daily builds (I don’t have a specific build number but you can review the release notes to check).
In these builds, “CFBundleShortVersionString” uses the “Version” field in the iOS Build window and a basic formula “CFBundleVersion=yyyy.mm.ddtime” to make it unique for each build (this now being required when uploading to iTunesConnect).
Either field can be overridden by including it in the plist section of the build.settings file, but if you do that, you’ll need to remember to update it every time you do a new submission.
Note that public build users (2393a) must add “CFBundleShortVersionString” to the plist if they plan to submit apps to iTunesConnect.
Hope this clarifies things,
Brent
There’s still a bug when I upload to iTunes Connect.
In the build window I type 1.02 but in iTunes Connect the Bundle Short Version String as 1.2.
Yes, I can verify that. I was using 1.04 and the iTunes was showing 1.4.
Don’t remember if you set both manually inside your build.settings (instead of using the Corona Build Windows) will work or not.
It’s possible that Apple is processing the number and computing a major and a minor number which is why the 04 is turning into a 4.
Rob