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.
Related
So I applied for an expedited review on the 8th of december and it was approved, processed and ready for sale on the 9th of December.
I have version 2.0.1 on my phone, and the version 2.0.2 is not showing up as an "Update" in app store. When going to app store it will show me the date I upgraded to 2.0.1 and shows that is the newest one.
If i then click on the cell to show more info, it takes me to my page listing 2.0.2 and all the correct details.
If I search my app on the store, it shows correct info 2.0.1, it is just everyone who already has my app, is not being promoted to update.
It has been 6 days, and Ive contacted ItunesConnect support, they tell me everything is fine on their end and if I have users who are having problems, to instruct them to call Store Support. So I told them its all 50,000 users who are having the issue, and they instructed me to inform 50,000 people to contact Store support.
So at this point Im all out of ideas.
iTunes connect called me back after a few hours, they had spoken to Store support and there is an active bug they are trying to fix. They said this is a not a wide spread issue, but it is affecting many Devs.
They told me to sit and wait.
Edit
They never were able to fix it, after 7 days of error, I uploaded a new build, submitted for review, once approved, it kick started the process again, and was pushed correctly to the iTunes Servers.
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 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.
I have an iPhone application in the App Store. I submitted 1.1 to the app store a few days ago, and selected to "Hold for Developer Release." I found out that there is a very serious bug in the approved version. I need to pull this binary.
From what I can tell, Apple doesn't support this. I have sent them an email, but there's another bug in the current version that needs to be fixed also, so time is of the essence.
I've heard that you can release the update in some random country (where I would have no sales) and then release the next (fixed) update in all countries. If I only release 1.1 in, say, Luxembourg, is the old version (1.0) pulled from the other stores? Are the chart ratings reset? I'm relatively high in the charts, and I don't want to lose the momentum the app currently has.
Until Apple supports rejecting approved binaries, I'm looking for the quickest alternative.
Craig. Let me answer some of your questions. First, if you release an update, regardless of what country it is released in, it will replace the old binary for every country. Thus, if you only select Luxembourg, you are not only releasing the update to all countries, but also removing the app entirely from every app store except Luxembourg.
Second, it would appear that even Apple has no say over the iTunes Connect website in terms of altering the process for one person. I believe you should be able to reject an approved update, I don't see why they would want to disallow this. However, since they do not right now, it's best to forget about it.
You basically have 2 options. One, you can release this new version to the world, which keeps your standing in the App Store and warn users of the bug and promise them a fix. At that point, you can appeal to the Review Board for an expidited review, which they may not give you. Remember, if you release the update, I would upload another update immediately after.
You're not going to avoid your problem but there are things you can do to minimize the impact of your mistake.
Second, you can remove the App from Sale, accept the new update, and upload a new one for review, and put the app back up for sale again once approved. The problem here is that you will most likely lose your store ranking and the app will be unavailable for about a week. Not what I would do. I would go with the first solution.
From my experience, customers are ok if you need to issue a fix and they're fairly understanding. Make sure you tell them exactly what's going on in the app description AND the "What's New" section. Make sure they see it. They'll be ok with a few days of inconvenience in return for your honesty and reassurance that the issue has been fixed in a near-future update.
Hope this helps.
Cheers!
You can reject an app that is on "Hold for developer release". You need to click "Binary Details", and there you should find the reject button.
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.