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.
Related
I'm working on a group project and we are trying to upload our flutter app to the Google Play Console. The other day, I finished all the processes for submitting the app and now we are waiting for the app approved. However, the app we submitted as the app bundle before doesn't have much functionality. But, one of our MVP was uploading to Google Play, so we just submitted the app having a simple frontend with no functionality to the "internal test", because I thought our app doesn't have enough functionality to release as a closed or open test.
My first question is if it says "pending publication", does it mean they are in the reviewing process and I should just wait for a few days? Another question is is it ok to update our app bundle while they are reviewing our app (since the current app bundle doesn't have much functionality)? And when is the better time to update app bundle next and and how to update? Is it just hit remove in the picture below and drop a new file??
"Pending publication" indeed means that your app is under review. These days, it can take as much as a week to have it reviewed.
You can indeed choose to create another release even while the first one is under review and upload a new App Bundle. In this case, the first release will be aborted in favour of the new one (assuming the two releases are in the same track). As someone pointed out, it is possible that it resets the waiting time for the review.
Regarding your screenshot, the fact that you can see a "Remove" button means that you probably already have created a new release (since existing published release are immutable). Maybe you created a new release in a different track?
Clicking "Remove" and uploading another version of the App Bundle should do it.
What do I mean?
My app was approved and since saturday is ready for sale. Some of my customers can see an update in app store and then they do an update. After update is completed, the open button appears and... after app is opened we can see that it is previous version;)
Why?;)
It happens really often.
This could happen if you directly archive your application for publish instead of 'clean and build' it in the release option.
If you directly archive the app, there is a change it could take the previous version's release instead of doing the clean and build.
Hope this helps.
Update: The app is already configured in iTunes connect I can't remember which option I choose.
I have an app sitting in iTunes Connect waiting for upload but I am unsure whether I choose 'wait to release' or 'release immediately'.
How do I ensure it is set to 'wait to release' before uploading my binary?
If you select wait for release option, in app summary page, new version will be listed as
"Release Control: Hold for Developer Release".
If you choose wait to release,You have to release your app after apple accepting your app.If you choose 'release immediately',It will be automatically released after apple accepts your app.
I always prefer the "wait to release" option.
This gives you the possibility to not release an update if you notice a bug in the last minute. Also you can sync your release with other time dependent actions like:
marketing campaigns
backend changes
...
I believe you confirm that option after you upload the binary as part of the submission process.
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 was hoping someone can answer a simple question for me...
If you create an iphone app and get it approved for sale, what happens if you add updates to it? Do you have to submit this for approval too?
How does the whole process of updating existing apps work?
Assistance would be very much appreciated, thanks
Yes, every update requires a new round of approval. Once your first app is live, the management page for your app offers an "Add Version" button, which takes you through a similar process to the original app, but with options to document changes.
You do indeed need to have updates approved. So once your initial application is created in iTunes Connect, uploaded and approved by apple and available through the store, you can easily submit new versions.
You log into iTunes Connect and click Manage my Applications.
Select the application and click the Add Version button.
Fill out details of the update (such as the new version number, what's changed, any new screenshots, etc).
Upload your new binary via the application loader.
Wait for review.
The process of update is almost exactly like the process of creating and pushing out the first release. It's really quite simple, tbh.
The update process is nearly identical to the original submission, except that you don't have to reenter all the metadata (but you can modify almost all of it, except for the app ID, during update submission).
Update review times have historically varied by large amounts, either slower or faster than the original app's approval time, on the order of 1 day to 1 month. Don't count on it being any less.