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.
Related
As iTunesConnect has introduced the new feature to expire the build which eventually remove the build from iTunesConnect. After doing that i wanted to upload the new build with same App version and Build version but getting below error
ERROR ITMS-4238: "Redundant Binary Upload. There already exists a binary upload with build version '1.2.8' for train '1.2.0'" at SoftwareAssets/PreReleaseSoftwareAsset
Is it possible with new iTunesConnect?
This is not possible. Suppose you already have version number 1.0 in App Store then new version must be greater than 1.0.
Refer following link for more details: https://developer.apple.com/library/content/technotes/tn2420/_index.html
Version number and build number checklist
Here are some things you can check when submitting a new build to the App Store. Making sure you have your version number and build number set properly will help you by avoiding having your app automatically rejected for having them improperly configured.
For each new version of your app, you need to invent a new version number. This number should be a greater value than the last Version Number that you used. Though you may provide many builds for any particular release of your App, you only need to use one new Version Number for each new release of your App.
You cannot re-use version numbers.
You cannot re-use version numbers.
For every new build you submit, you will need to invent a new build number whose value is greater than the last build number you used (for that same version). For iOS apps, you may re-use build numbers when submitting different versions. For macOS apps, you must chose a new build number for every submission that is unique and has never been used before in any submission you have provided to the App Store (including build numbers used in previous versions of your app).
For iOS apps you can re-use build numbers in different release trains, but you cannot re-use build numbers within the same release train. For macOS apps, you cannot re-use build numbers in any release train.
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..
Perviously the client uploaded same app on iTunes connect and rejected for some reason.
After some modifications I need to upload the binary again.
The previous binary details are,
Now, here are the current info.plist details,
I am using Xcode 4.0
When I tried to validate product from Xcode I got this error,
I tried different different CFBundleVersion in the Info.plist. but still error occurs.
I cleaned project, deleted build, also re-installed Xcode and retried but no use.
Please help me.
So it looks like this needs to be an ever-increasing version number and can't reset when the marketing version number changes. It seems like you could use your VCS revision number here; in my app I display the marketing version number and if the user "clicks" on it it adds the build number (CFBundleVersion) on the end. The primary purpose of this is to keep the version number clean and simple, but also allow QA and beta testers to determine the exact version of the product they're testing. The Subversion revision number would certainly help us track down the build being used, but in this case that'll be a strange version number jump for me (6 -> ~74000).
basically i had to change 1.1f to 1.11 in both itunes connect and in xcode. the f had to be removed from the version number. no alphas allowed !
Reference: Can't Update App with New Version Number
Some time ago we released an app to the AppStore on a client's account. The client preferred a simple version number scheme, so the apps first version number was 1.0. Since it's release, however, there seems to be an unexpected need for minor changes to the content of the app on a regular basis, so a more precise versioning scheme, reflecting content revisions, would be more feasible now.
Is it possible to "refine" the numbering scheme in the course of an update to the app? Instead of upgrading from 1.0 to 1.1, I'd like to go to 1.0.1 now.
Would it be sufficient to just change the version number according to the new needs or will the AppStore accept only new releases if they follow the original scheme?
Thanks!!
You definitely can, especially if you haven't submitted the 1.1 version yet. 1.0.1 > 1.0 so it's ok.
Taken from "Developer Guide" (https://itunesconnect.apple.com/docs/iTunesConnect_DeveloperGuide.pdf)
Version Number:
The version number of the app you are adding. Numbering
should follow typical software versioning conventions (for
example, 1.0 or 1.0.1 or 1.1).
We have recently released version 1.0.0 of our application and have sent out numerous promo codes in the past couple of days. I was just wondering whether they will still be valid for the 1.0.1 update which we have just submitted?
Yes.
Promo codes apply to your app no matter the version (only the version currently available on the store), and no matter the price (even if it's free a code should work.)
Here is the text from the apple promotional website:
Select an application and enter the number of codes you are requesting. You are given 50 codes for each version of an application. They are for non-commercial use and will expire four weeks after they are requested. These codes can only be used in the U.S. iTunes Store.
From this text, it is clear that you can issue brand new codes for new versions of your app. It is not clear whether your codes from 1.0.0 will still be valid for the 1.0.1 version of your app. I would think that they would still be valid, but that's just a guess.