ERROR ITMS-90478: Invalid Version, problems when upload package of iOS development:

created at 09-03-2021 views: 43

error message

I received such an email after uploading the ipa package of iOS

error email

error message

ERROR ITMS-90478: "Invalid Version. The build with the version “2.20.170928” can’t be imported because a later version has been closed for new build submissions. Choose a different version number."

ERROR ITMS-90062: "This bundle is invalid. The value for key CFBundleShortVersionString [2.0] in the Info.plist file must contain a higher version than that of the previously approved version [2.20.170928]."

Note the specification for version identification:

Invalid or Non-Increasing CFBundleShortVersionString - The value specified in 
the bundle's Info.plist file for the key CFBundleShortVersionString must be 
a string consisting of at most three dot-separated components, where each 
component is composed only of the digits 0 through 9. For example,any of 
the following are syntactically valid values for 
CFBundleShortVersionString: "1.0", "4.2.1", "3.46", "1.112.0"; whereas the 
following are all syntactically invalid: "1.4.0.0.0.0.5", "GX5", "3.4.2b6", 
"2.6GM", "1.0 (Gold)", "-3.6". Additionally, each updated version of the same 
application must have a CFBundleShortVersionString that increases relative 
to that of the previous version that was actually made available for sale 
on the iTunes Store. For example, if a previously-available version had a 
CFBundleShortVersionString of "1.4", then any of the following would be 
acceptable as the next update: "1.4.1", "1.4.332", "1.5"; but all of the 
following (though syntactically valid) would be unacceptable: "1.4", "1.3", 
"1.3.9", "0.9". For more information about the CFBundleShortVersionString key 
and the Info.plist file, see Apple's Runtime Configuration Guidelines at 
http://developer.apple.com/library/ios/documentation/MacOSX/Conceptual/BPRuntimeConfig/index.html

Solutions and knowledge points:

  1. The version number must be standardized
  2. The version number is CFBundleShortVersionString, which is also the external version number on ITC, and the build version number is CFBundleVersion, which is also the build version number on ITC.
  3. Each version and build are larger than the corresponding ones on ITC this time.
  4. The Version each time is larger than the latest build on ITC
  5. Compared with 1.20 and 1.3.2, 1.20 is greater. This is because 20 is greater than 3, and ‘.’ should not be regarded as a decimal point. This is just a separator.

For the above screenshot error, I can set the current version and bulid version number to 2.30 or 3.0, or other.

Then I went to the TestFlight in the App Store Connect to check it. There was a 1.30 version, so I knew the problem. I don’t know when this 1.30 was made. It should be 1.3.0 accidentally written as 1.30, which caused the high version. So later on 1.3.2 and 1.3.4, they couldn't be submitted.

created at:09-03-2021
edited at: 09-03-2021: