In iOS, what's the difference between:
Bundle versions string, short AND Bundle version?
What to update when building a new release and when ?
Bundle version is the internal version number of your app.
Short version string is the publically visible version of your app.
So for example, if you iterate your version number every time you do an internal build for your beta testers (or whatever), your bundle version might be 2.0.0.12345b7, but you don't want the public to see that, so you set your short version string to 2.0.
Short version string seems to be optional, so if you leave it blank then the bundle version is what people will see (i.e. that's what will be displayed on the App Store).
If you don't have a short version string, then the same rules apply to your bundle ID (basically the public app version has this restriction and the private app version doesn't).
There's a more detailed answer here:
What's the difference between "version number" in itunes connect, "bundle version", "bundle version string" in xcode?
http://developer.apple.com/library/mac/#documentation/CoreFoundation/Conceptual/CFBundles/BundleTypes/BundleTypes.html
From docs..
Bundle version is the one that must be in the info .plist and that's the one you should update every new version..Bundle versions string, short is not must but is given although i didn't understood its use..
Related
We have not been able to publish our first update to our iPhone app on the app store.
The validate step after build always fails with:
"This bundle is invalid. The bundle identifier cannot be changed from the previous version. If you want to change your bundle identifier you will need to create a new application in itunes connect."
We have only one Apple account with only one app. We have not changed the bundle id in the plist file ever since we released earlier in the summer (it was different before we released though). it is "com.company.product" (with our real company name and real product name all in lowercase). We only increased the version number from 1.0 to 1.10 (after seeing articles here with problems going to 1.1)
The iTunes connect is expecting 1.10 and the same bundle id. Spent 2 days Googling but can't find anything useful and tried different versions and bundle ids etc but nothing was good.
Please help!
(I have also sent an itunes connect question on this to Apple but no response so far)
I got this error before, I'm not sure however if you have done the same thing I did:
In versions 1.0, 1.1 and 1.2 of my app, it only supported iPhone. I then got an iPad of my own for testing. In version 1.3 of my app, I updated it to support iPhone and iPad. It wouldn't upload, giving me this error. Turns out if you want a universal app, it has to be universal from the start, you cant decide in version 1.4 or whatever that you want to add iPad compatibility.
Is there a chance of app getting rejected if the iPhone app update is submitted with wrong version number? For instance i had given the version number 1.6 instead of 1.5. The app which exists in app store is of version 1.4. Will my app update get rejected?
The version number just has to agree with the version number you specify in your Info.plist. Apple does not care about he numeric value, so nothing to worry about.
It doesn't matter. Apple doesn't have a version number naming scheme. As long as your app-version matches the version given in your itunes its not an issue. Also any error related to incorrect versions are reported during submission itself.
So naming scheme is totally dependent on the developer.
No it doesn`t matter.
i have submitted an app with version number 1.3 instead of 1.2 and it was approved.
so don`t worry..
I have client with an app in the app store that was at version 4.05 and they accidentally submitted a new build as version 5.06 when they meant to submit it as 4.06. They aren't ready yet for a full version number increase. Long story.
Is it possible to submit the next version as 4.06 to get it back on track? Or is not allowed to upload a lower version to iTunes Connect?
Yes. The version numbers only need be distinct.
From the Developer Guide:
A Version Number The unique version
number of the app. Keep the following
in mind:
Use typical software versioning conventions (for example, “1.0 or
1.0.1 or
1.1”).
Do not include words such as “build” , “version” or “beta” in your version
number. This will appear next to your
application icon on the app product
page.
i have been trying to uplaod an application to apple store for 2 days now..first they said the provisioning profile was not right due to which i had to make a new one and upload it again now after that problem was solved while uploading the new binary it said the version was same with the previous minor version(1.0 - which someone else uploaded in my company)..then i changed the version to 1.1 by changing it in target > info > properties..then i cleaned all targets quite the xcode,restarted the xcode and build the project again..it succeeded and now wen i uploaded it it still says the same error
version same with the previous minor version
is there any other way of changing the version number though in my info.plist file it is showing version:1.1??
i am all new to iphone and the person who created the application is not here and i dont have any CFbundleversion in my info.plist which some people suggested me to update??
Alternately you can change CFBundleShortVersion string in app-info.plist file and increment it. I have faced the same problem earlier. This property is not present by default and needs to be added.
Bundle versions string, short is the parameter name
Change your version from 1.1 to 1.1.1 or 1.2 For each new binary, your version number should increase. How to increase version numbers will depends on your versioning system.
When I am installing new application on iphone, this current application get override on the last application,so we can not maintain the previous application.
Please help to solve this installation problem.
If you change the app identifier in info.plist you can have a different version on the phone at the same time...
However, do you really want to do that? Most apps migrate by loading a new version, but then updating the old database or preferences to work with the new version of the application. Just because your application is replaced does not mean the data the user created is replaced.
If you change the Product Name in the build settings, that directly affects the name of the .app bundle. You can have two copies of the same app, as long as theyhave different names - this can be helpful for testing a new version while preserving the old, stable version.
As Kendall says, you probably want to use the same name for newer released versions of the same application.