I have an iPhone app that's been approved but has a release date around 7 days from now. I want to add some very minor bug fixes so I'm going to submit a new binary.
If I submit the update, does that affect my ability to release the original version on its scheduled date, e.g. if the update was still in review at that stage?
Thanks.
Your current version which has been approved will be released as scheduled regardless of if you submit an update for review. For your pending update, just add a new version with the version number bumped up and submit the binary as normal
Yes. If you need to change the binary, or in your case, reject the approved release, you will need to resubmit your binary and start the review process all over. You won't need to change any information with your meta information, but rejecting the binary effectively loses your place in line and you will have to start over. Your only option would be to wait until the app releases, then ship an update as soon as you are live.
Related
As the question says, I am wondering whether UPDATED apps are automatically released onto the app store once they are approved?
My update is finished and has been tested, and as it takes a few days to approve I would like to submit it for approval now. In the meantime I need to change update a few things on my server, however I do not want the app update to go live until I have finished my server stuff.
Will the app go live immediately or do I get to choose the release date (after approval of course)?
Many thanks
You have an option to
choose the release date
release immediately on approval
once approved wait until I release it, (wait for you to click the release button so you can make server changes) aka Version Release Control.
This can all be done from iTunes Connect when submitting your application. However, if you select the option to "release when i'm ready" that application approval is only valid for that build. If you upload a new build, it must be re-approved.
I've just got an app in the app store and realised theres a spelling mistake on the first view! As the app is intended for an upcoming event occuring in 3 days I am nervous about uploading an update. If I upload new binary to iTunes Connect will that mean my previous version will not be available on the app store? Also, will I need to have Apple approve my latest version prior to releasing it?
Any advice would be awesome, thanks!
When you push a new update it has to be reviews but will likely take more than 3 days to do so. While it is waiting to be reviewed your current version will be live.
Don't worry, your previous version won't be affected. Just upload the new one, but know that it's gonna take more than 3 days (pretty much always 7, if you submit during work hours). You can file for an expedited review, but even that can sometimes take more than 3 days.
And you don't need to remove the old version to put in the new one. You just submit the new one. You can determine whether you want it to automatically become available on the app store as soon as it's approved, or give it a specific release date.
Just know this: If your update has issues and you're forced to remove it AFTER it has become available on the app store, then you can't just revert back to the old version. You have to resubmit the old version and wait a week for that to get reviewed again.
I have version 1.0.0 of an app approved but not yet live; the release date is two weeks out. I also have some enhancements queued up as v1.0.1 but not submitted for review yet. The most important thing is that the app goes live on the scheduled date (synchronized to a marketing plan, external partner requirements, etc.) but if possible I would like to have my v1.0.1 available for the initial release.
If I submit my 1.0.1 version for review will it risk my ability to put the existing approved version live on time?
I see two risks:
v1.0.1 is still in review, can I edit the release date (if necessary) and have v1.0.0 go live
v1.0.1 is rejected for some reason, is v1.0.0 still available to go live?
UPDATE:
Our live date was pushed out due to business issues and we had plenty of time to get the update through review but in any case this is what we did:
set the release date to the appropriate date
submit the new version for review with version release control so it wouldn't go live until we pushed it after review
During the whole review process we were still able to edit the release date for the original version so I believe that it would have gone live if needed while the update was under review.
Here's something you can try. I have done this for quite a few apps long back (about an 9 months back, not sure if things have changed)
Release the existing app and then immediately take it out of sale from all countries (you can do this on iTunes connect).
So technically you have your app on sale, and you'll be able to upload a new binary as an update.
If the update/1.0.1 gets approved in time, release it. If not approved, enable the 1.0.0 app for sale in the countries you want to sell.
I hope this helps!
The release date is two weeks out. I suggest you update the app. The process takes only around a week, even if it is rejected. You will be able to release v.1.0.0.
I just got my app approved....but realised there is a bug that will need a small fix. I do not want to release this app with the bug.
I am unsure how to get this fixed. If I submit another binary it will go through the review process again. I will also need to put a new version (1.1).
If I still have to submit a new version, can I directly release the new version (1.1) and completely ignore version 1.0?
Thanks in advance for advise..
pm
You would have to reject your binary for 1.0 and resubmit either a 1.0 or greater binary.
You can set the release date of an approved app into the future and then submit an update. If the update is approved, pull the release date back. The current version need never be visible in the App store.
If you put in your comments field that this is a critical bug fix, then there is a possibility (but no guarantee) that the review period may be a few days shorter.
You don't need to change version. You can keep version 1.0 and change build 1.1. Then Submit app for review process.
If your application has been approved, then it's available in the appStore.
The only solution for you to fix this bug is to send a new version of your application with unfortunately the Apple review process. (We just got the same issue)
From here, 1.0 will be ignored for new downloaders and those who have installed it would have to update the app.
I have an app on appstore.
I uploaded a new version and it was published. But, just after that I realized an important bug in my app. Since the approvement process takes a long time, I want to downgrade to the previous version until the fixed version is approved by Apple.
Are there any way for that?
Thanks
The only way to downgrade is to resubmit the previous version with a new version number, or a new fixed version, and wait until it is approved. If you put a note in the Demo Account section saying this is a rollback or a critical bug fix, there are reports that Apple may perhaps expedite the review. If the bug is bad enough to create very unhappy customers, you can warn customers not to download it in your update notes, and/or you can set the availability date of the current broken version into the future, until your fix is accepted.
Unfortunately not, Apple doesn't provide a means of rolling back to previous versions. If you have the source code, you could always just increment the version number and upload the old version again.
like the other answers have said - unfortunately, Apple does not provide a way to rollback once you've released the app.
The way many major apps deal with this is by instrumenting their app ahead of time with feature flags (https://martinfowler.com/articles/feature-toggles.html): ways to enable/disable features and codepaths from the server.
Granted that implementing feature flags requires foresight and planning (it's unlikely you'll capture every codepath). Fwiw, I started my current company (https://screenplay.dev) out of this frustration; you can read much more on this approach here: itunesconnect App - Revert to previous version :)