CFBundleVersion must be higher than previous version

Question

I\'m submitting an update to one of my apps. I\'ve done this dozens of times with the many different apps I\'ve developed, but this one is failing for some weird reason. I a

Answer 1

For me the problem occurred simply because previous build was already reviewed by Apple but I did not release it. After I rejected the old build, I was able to upload the new one. Versions numbers were just fine. So yeah... Check your App Store Connect before uploading new build

Answer 2

This can be caused for another reason entirely.

I had an active TestFlight beta running. Build 2020, version 407

I submitted an app for official App Store review. Build 2020, version 435, and it was approved. It is just sitting there, waiting for me to push it live into the App Store.

Without adding a complicated side story, what I wanted to do is to give my TestFlight beta users an updated version to preview the official App Store version for a few days, before making the App Store version live. Why, you ask? Because they were getting free features, there were about to cost money once the app would go live.

So, I submitted Build 2020, version 436, to TestFlight, and it was rejected.

It was rejected because I have an approved official App-Store candidate with the same build number

Solution: Change the build number of your TestFlight version. I submitted Build 20200 (I added an extra zero) version 436 to TestFlight, and it was approved. Don't worry, you can still push this build to the same TestFlight beta group, as long as you're still using the same BundleID.

Answer 3

One of the reason could be next situation: You sent to AppStore version 1.0 with build number 50. You decided to give it to TestFlight users for test. And simultaneously decided to send this version for review to AppStore. Users starts testing it and all fine. Some time later AppStore approves it, and its not releases( it has developer peinding status). After u made some changes and want to give your Testflight users new release. You decide to increase build number to 51 and keep version number at 1.0. You will get that error which you described in your question in this case. You have to increase App version too.

Answer 4

Here is how I fixed the problem (and I'm guessing this is the issue with a lot of people):

1) Click on the general tab of your projects settings (which can be accessed by clicking on your project name which is at the top of all the code files).

2) Make sure the build field matches what you put in your plist for the "Bundle Version" key.

This was the problem for me, for whatever reason they were out of sync. I think when you change Bundler Version key it's supposed to sync up (and vice versa). But it didn't happen for whatever reason - might be a bug.