I want to change version of app.
Right now 1.0 version is live and I uploaded build to TestFlight with new version 2.0
but not submitted to App Store .
But I want to submit 1.2 version in place of 2.0 so it is possible to upload 1.2 version to store?
When I am trying to upload new build with version 1.2, getting error like
App Store Connect Operation Error
ERROR ITMS-90062: "This bundle is invalid. The value for key CFBundleShortVersionString [1.2] in the Info.plist file must contain a higher version than that of the previously approved version [2.0]. Please find more information about CFBundleShortVersionString at https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleshortversionstring"
I know new build version should be higher than old version but any possibility then le me know.
Please help me out if it is possible
Thanks
If you want to change the version that gets displayed to the end user, you can always change that directly in App Store Connect. The "display version" is independent from version code attached to each build.
Once you have a higher version used for your builds there is no way to "decrease it" again.
Related
I am trying to upload a new release from my iOS app to App Store Connect, but I am getting always an error message while uploading the binary.
Here you have the error message:
I have created the new release version in App Store Connect, as always:
And as far as I know there is not version "9" anywhere.
Here you have a screenshot from the app identity panel from Xcode.
What am I doing wrong. I am not doing anything not done before to upload a new release from the app.
You need to update the version number and build number before uploading to app store.
-Version number you should increment when your previous version is live and ready for sale.
-Build number you have to increment when previous build is failed after uploading.
-Every time you have to give new build id increment by one. e.g Your version is 2. so can have build : 2.0,2.1,2.2 and so on.
For your case version 2.1 is closed for previous release either you can use 2.2 or 3.0. and for build you can use 61.
When trying to upload the latest greatest app version of our app to App Store Connect we are getting the following error: This bundle is invalid. The value for key CFBundleShortVersionString [2.1.0] in the Info.plist file must contain a higher version than that of the previously approved version [1565960106]. I understand that you cannot upload version 1.0 after 2.0, but in our case we're not planning to make our version higher than 1565960106. How can we get rid of this strange high number?
Side note: the store version is 2.0, there is indeed a faulty version where the build number was used as version number and that one was approved for external testers, but never released to the store.
I have a problem with fastlane when I publish on TestFlight a new bundle that uses the usual version (ex: 1.0.2):
Error This bundle is invalid. the value for key
CFBundleShortVersionString (1.0.2) in the Info.plist file must contain
a higher version than that of the previously approved version [1.0.2]
It seems like I need to publish a new version, but I want to publish a new build instead, keeping the same version ... how is that possible?
Edit Response:
ok, I understand ... although unlike Android, I don't see the usefulness of blocking a new build if there is the same approved version ... but thank you all!
There is no way to upload new build of the previously approved version. So in this situation you should have to create new version in iTunes Connect and then and then you can able to upload new build in Testflight.
Few cases arise:
If you want to keep same version, remove current app from app store and publish your current version.
Now there is already app with same version so you cannot allow to do this, either increase the version or go with point 1, how ever be careful with this point. You need to analyse cases, because it is already on appstore.
You can upload the same version to TestFlight with increased build number. Eg: 1.0.2(1) and 1.0.2(2) Simply increase the build version from Project settings.
What I'm trying to do is upload an app as version 2.0.1 for the end users. I however get this error message:
ERROR ITMS-90478: "Invalid Version. The build with the version “2.7”
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.1] in the Info.plist file must contain
a higher version than that of the previously approved version [2.7]."
The is in the appstore now under version 1.4.3 and I'm trying to upload 2.0.1:
The iOS builds for 1.4.3 went up to 2.7 already though, is this going to be a problem if I want to be named 2.0.1 in the store?
This is what I've filled in for version and buildnumber right now:
I had the same experience. I made a build version higher than the previous loaded version.
You don't need to worry about the build number. Make your version as 2.7.1. It will eliminate both the errors. It worked for me.
Try the following.
Rest the build version to 1.0 and than try to upload.
I've been trying to submit an app update with version 1.7.1 to the appstore.
When I do so I get this error on validation
This bundle is invalid. The key CFBundleShortVersionString in the Info.plist file must contain a higher version than that of the previously uploaded version.
While deleting my failed attempts in the organizer I noticed that the 1.7 update was submitted as version 17!
Bingo!
So the question is this.
Is there a way to fix this? Or am I stuck using versions greater than 17 now?
Now you should use version greater than 17. You shouldn't contact Apple for that issue.