I am trying to submit new version built to app store. Previously I got a submission and set it to manual release. The review is successful. But I chose to cancel the release. But now I am trying to submit new version but there is no option for iOS (as shown in picture).
You rejected 1.0. You can't create a new version. Just submit an updated build for 1.0 and release that.
You must upload a new binary.
regards.
You can only have one version open.
You could, however, change the build (remove the old one first) and change the version number in the General App Information section.
Related
I created a new app version, but this one got rejected by the App Store review team. To fix the issue some more effort has to be put in, but the company doesn't want to do that in this hotfix release. Now I should cancel this version all together for the App Store only.
How do I do skip this version?
The "submit for review" button is available, but I want to abort the submission. Should I remove the build as described here and then I can remove the version somehow? Or should I overwrite the version number and submit a new build with the new version as proposed here?
I removed the build (for submission) from the App Store page and updated all descriptions/screenshots including the displayed version number.
Afterwards, I submitted a new build with the updated version number. This worked like a charm! The old (rejected) version never existed :-)
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!
This is our first iOS application on the Apple Store and v1.0 has been approved and Ready For Sales.
Now we are updating with new build v1.1 with fixes so anyone knows if current build (v1.0) is still available for testers/users while new build (v1.1) is being reviewed?
Cheers,
H
Your current version is available until you release the new version to the store for sale. You can check the "automatically release new versions" checkbox and as soon as the review passes it will release.
Yes, v1.0 is still available. There is an option to hold the build until you want it to release. Else until the new build gets updated in all apple servers, your users will still see the v1.0. Normally it takes sometime, for all the users to receive the latest version depending on their location.
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