Cfbundleversion Must Be Higher Than Previous Version

CFBundleVersion must be higher than previous version

It turns out that I had some problem in my original submission which caused the user-visible version to be "1.0" but the internal bundle version to be "1.2". So I changed my new version to be 1.3 and 1.3 and the submission worked.

Sample Image

My App version is higher than previous but getting Version issue

You see that CFBundleShortVersionString is [1.2] which seems greater than [1.15] when you consider both as decimal values. But, versions are not calculated the same way. You might want to modify your version from [1.2] to [1.20] to make it higher than [1.15].

The value for key CFBundleShortVersionString [3.0.0] in the Info.plist file must contain a higher version than that of the previously approved version

Looks like app store was picking up the version from my package.json file which had a version key.I updated it to 4.0.0 and it worked successfully.Some issue with the expo cli I guess.

bundle is invalid -- CFBundleVersion and CFBundleShortVersionString in Info.plist must contain a higher version -- but they do

Turns out this is a duplicate of CFBundleVersion in the Info.plist Upload Error. I followed the advice in the second answer--deleting the archives--and everything turned out fine.

Can not upload new mac version to app store

I have ran into the same issue in the past. For me, my Mac app was built with Mac Catalyst and am using universal purchase. I had to increase the Build number to be higher than the build number of the last version. "Build" Number, not "Version" number. This is weird that we have to do this, but this probably a mac catalyst bug they will fix at some point. Hope this helps!



Related Topics



Leave a reply



Submit