Our app was uploaded to our AppStore connect account with incorrect version. Supposedly the app should have a version 1001.200211, but we incorrectly entered 1010.200211 which is too large.
The first number in our version 1001 indicates the iteration number the release happen, the expected next version would be 1002 or 1003 but since we already entered 1010.200211 the next release versions no longer valid and will not be accepted!
Is there a way to update the build version after it has been uploaded in our AppStore connect account?
There is currently no way to change the build version of an app. You may be able to contact Apple Support to help you with this by deleting that binary but there's no way to do this yourself.
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.
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.
Here is my scenario:
We recently created a iTunes app record for our new app which is not yet available to public. So, by default iTunes shows an app(1.0) with status as 'Prepare for Submission'. (I assume we can change this default version number from v1.0 to v1.0.0 on the app record. but for clarity I am leaving it as default in my below explanation)
Now, I uploaded my first build with v1.0.0(0) to TestFlight and after 4 revisions/build uploads, I made the build v1.0.0(4) available for external testers. Now we got few bugs from the external testers and fixed them. Since we did the bug fixes, I want to change the version to v1.0.1(0) in TestFlight. Below are my questions struggling to find an answer for:
1) Since the app is not yet released and the default app record version is still v1.0, can I still upload a new version i.e. v1.0.1(0) on TestFlight ?
a) If I can do the above point(1), will it go through the beta review process again (or) will it simply process and appears on iTunes ?
b) If I can do the above point(1), lets say after 2 revisions again like when version is at v1.0.3(0), can I finally push this build to the AppStore as my first release....I mean will it override the default version v1.0 to v1.0.3 ?
2) If I cannot achieve the above point(1), then what would be the other approach?
Please suggest me how to proceed...
First, yes you can submit your new version (1.0.1) but it will still have to pass through the apple process to get approved for external test.
If I can do the above point(1), lets say after 2 revisions again like when version is at v1.0.3(0), can I finally push this build to the AppStore as my first release....I mean will it override the default version v1.0 to v1.0.3 ?
Yes, when you publish your app, you can specify the version displayed in the store so you can display v1.0!
Every time you want to make a new build available to your external tester, Apple need to approve it!
I had submitted an version 2.0 of my app for review recently.
It got rejected by apple for a valid reason.
I made the changes and tried to upload a new binary with the same version say 2.0
But it wont upload it via Xcode saying an binary with version 2.0 already exists.
I couldn't find any way to remove the 2.0 rejected build from the Pre-Release tab.
I tried this
reject this binary in new itunes connect UI .
But this did not help either
Thanks in advance.
Cheers.
You don't need to increase the version number. But increasing the build number should allow you to submit.
Note that this is in the "new" iTunes Connect. The idea being that you can have multiple versions being tested by different groups of people. The unused builds are removed when they expire (note that there's a date attached).
Try increasing the version number and build number then submit the binary
Each time I attempt to publish an update to an app I receive this automated email response moments later:
We have discovered one or more issues with your recent delivery for "App Name".
Your delivery was successful, but you may wish to correct the following issues in your next delivery:
Version Mismatch - Neither CFBundleVersion ['9.1'] nor CFBundleShortVersionString ['9.1'] in the Info.plist match the version of the app set in iTunes Connect ['2.41'].
I understand why the message is being generated but I would like to resolve the issue without having to compromise the version # by making it higher than it actually is.
Being the first app I had ever developed, I was pretty clueless when it came time to publish the app and in frustration of the process I mistakenly defined the version number to some extreme value because I was, at the time, getting stuck with another error that was preventing me from completely the process .. the other error which I've since forgotten exactly, was related to the version number being incorrect. So I finally thru my hands in the air, set the version number to 8 and was able to complete the process.
Since then, I'm still pretty clueless but I've learned a thing or two, and the current version of the app is 2.41. When I prepare an update on iTunes Connect I set the version to 2.41. But if I define 2.41 in CFBundleVersion or CFBundleShortVersionString, Xcode outright refuses to upload the binary and demands a version greater than the previous version which has now surmounted to 9.1.
Obviously, any users of the app would be quite confused if the version jumped from 2.41 to 9.1 overnight.
It was you who defined the new version as 2.41 in iTunes connect. Any new version should be higher than the last one. So the straightforward solution is removing the 2.41 version from iTunes Connect and add a new 9.1 version. Then iTunes Connect and your binary will be in accordance and you will be able to upload the new version.