I've been googling this question, but haven't been able to find an answer.
I know that you are able to upload an app, get it approved, and then set a release date.
But I was wondering if the same thing can be done for an existing app?
Thanks in advance :)
You can't peg an update to a specified date, but you can "hold for developer release" on the update. That means that once it's approved, Apple won't publish the update until you go into iTunes Connect and manually press a button to release it.
No, when you remove an app from sale, you have to put it back manually, there's no way to specify a date to make this happen automatically. See the iTunes Connect FAQ for more info.
I have noticed that resetting the release date to the future after the application has been released will take it back out of the store and release it again. Im not sure how apple will look upon this if the application has already been released and is live. Mine was new and I had to keep pushing off the release date because the services were not reliably functional.
Related
I know this is a long shot but do you know if there is a chance put the app to AppStore im something like "preparing mode"? I mean it would be there, users could find it but instead of Download button there would be "in 7 days" or something.
The reason for that is that we're under extreme pressure from client to launch the app tomorrow and there's no chance how to make it in usual way (we're still testing the build and working on bug fixes).
Thanks a lot :)
Kuba
You can't do this, or even release any app which says Demo app.
The best you can do is to release it at the store with those features which are ready to be released. Work on known bugs as new features which you can include in next release. If you want to release it for Closed user group "TestFlight" of "iTunes Connect" can help you.
You can set the release date through iTunes connect as well, but that will not show your app to users until that is released.
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 want to check everything is OK before it released.
You can only do it when you are uploading the app for App Store. Otherwise if it is in review then you can't do anything with the binary uploaded.
You could always try to contact them and ask them to change this (through the "Contact Us" link at the bottom of the iTunes Connect home page). But they might take time to respond and they might say no, so this is probably not a good idea. The only way you can be sure is to reject your binary and then submit it again and choose the option you want.
You will need to reject the binary, modify the release date to some date far off in the future and resubmit unfortunately. Once the app is approved you can set the release date and release it. I don't think you are going to be able to download the app once it is approved unless it is available on the store though, so you will still need to test from you current local build anyway.
If I push an app update to the app store, but choose "I will release new version" when submitting. If my update is rejected for some reason, is the current version already approved going to be taken out of the store?
Anyone had experience with this?
I've got no experience with this exact situation, but I have submitted updates and then invalidated them myself. The original is unaffected until the new version is approved - if it gets rejected, they would just expect you to send a corrected version instead.
The only reason I could see Apple pulling the original would be if they discovered something pretty nasty in the update and decided to check the original as well in case they'd missed it, but that is total speculation.
I have one app where an update was rejected over a year ago. I haven't resubmitted the update yet and the original is still selling in the app store.
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.