Error ITMS-90062: The value for key CFBundleShortVersionString must contain a higher version than that of the previously approved version

Question

I am trying to update my app for the first time and ran into this issue. I searched a lot but none of the solutions worked for me.

App Store

Answer 1

I'm having a similar issue today. I uploaded a new build a couple days ago with no issues. I found someone who posted a similar issue here: https://discussions.apple.com/thread/7297092. They were able to resolve it by changing the Info.plist values in their sub-projects, however, I tried doing that, and I still ran into the same issue.

I cannot find any information on why this is occurring or when this started, but I know that I uploaded a prerelease build to TestFlight with all of the same projects 5 days ago.

I currently increment my prerelease builds this:

1.10 (1) -> CFBundleVersionShortString (CFBundleVersion) 1.10 (2) ...

I was up to 1.10 (7), which I deployed 5 days ago. Now, I can't get anything to work 1.10 (8), 1.10 (9), 1.10 (1.10), etc. They all say "CFBundleShortVersionString [1.0] must be greater than previously approved version [1.3]"

1.3 is correct as the previous version available in the store, but clearly, 1.0 as the Bundle version is not.

Answer 2

You must always increase the version number when uploading updates, so change it from 1.0 to 1.1.

Answer 3

What worked for me is to change it from 1.0 (.6) to 1.1 (.0) It's not really a new "Version" but incremental improvements and corrections. One thought is that when an app is accepted into the iTunes store then next upload must be to a higher VERSION.

Answer 4

I think it was some issue on Apple's side. It resolved itself automatically after few hours.

Answer 5

TL;DR: If you have an app version that was approved for the official app store, you cannot upload a build with the same version to TestFlight. You have to remove the app from official app store submission, or increase your TestFlight version #.

I figured out why this happened to me.

• I have an app in the app store with version 2010.

• I have been running an external beta test with version 2020, and build numbers in the range of 400-410

• In order to discover if my app would get rejected in the app store once I'm ready to actually release it in a few weeks, I submitted version 2020, build 407 for official app store review. I expected it to be rejected for various reasons. It was approved! However, i'm not ready to release it since I still have more fixes I want to implement. So, I let it sit there, waiting for me to do something with it.

• Then, I wanted to upload a newer build for my External beta, still version 2020, build 410, and I received this error.

• Thanks to user462990's answer, I realized that the error could be due to the fact that I have version 2020 currently approved and waiting to be launched into the official app store, so iTC didn't allow me to submit the same build # for a TestFlight external beta.

So, I selected "cancel this release" of the official approved version, and Viola! I can now upload a build with the same build #.

Answer 6

I ran into this issue when going from version 1.141 to version 1.15. Apple does not treat the version as a decimal number - they treat it as multiple integers separated by periods. Thus in my case Apple considered 1.141 to be Major version 1, Minor version 141 and then my new version was Major version 1, Minor version 15. Since 141 > 15 it fails.

Two options to deal with this:

1. Use Apple's interpretation of version numbers, so you always increment the minor version by 1: 1.1, 1.2, ... 1.9, 1.10, 1.11.
2. If you wish to use "hundreds" or "thousands" places (I do, as I try to encode the scope of the build in the precision - I use the thousands place for minor bug fix releases), then always pad them out with zeros: 1.10, 1.11, 1.20, 1.30

So in my case I went from 1.141 to 1.150 and I was able to upload.