My first iOS app is currently at the "Waiting for Review" stage on iTunes Connect.
Now, we are working on some bug fixes and I need to upload a new build, however, I would like to release the app as soon as possible.
My question is after an app is accepted, how long approximately does it take for Apple to review a new build / version for an app ?
Also see http://appreviewtimes.com to get an idea of current waiting times, based on developers self-reporting on Twitter.
Same as always, 7 to 10 days. Except when you ask for an expedited review, but then you should have a really good reason (and a really popular app ;-).
Any time you change your binary you go back to the end of the review line. The time varies depending on how busy the review team is.
The bulk of the time seems to be in "waiting for review." The actual review process seems to be pretty quick, assuming they don't need more info from you to make their decision.
The process of getting fixes to a rejected build seems to be faster than the original review process.
I would suggest planning on an app review taking 10 days. It might take less time, but that seems to be fairly typical.
94% of all iOS app updates are reviewed within 5 business days at the moment.
You can always check https://developer.apple.com/support/app-store to get the latest info on that.
Related
I am planning to build a prototype iOS application over the course of the next few months--let's say until October 1st--that will need frequent updates for iteration and user testing. After the application is approved for Testflight for the first time, I understand that it will be online for 90 days. I need closer to 140 days.
Firstly, what is the best way to update a build without triggering a few review? My understanding is that updates would not require a review and would take 1-2 hours to become visible, but I'm not sure what process is necessary for this, and what the limitations are. Do I need to update the version number and upload in a specific spot? How do I make sure users can download the new build? Should I delete the old one?
Secondly, how do I extend the time limit beyond the 90 days?
The answers might be related.
My question is similar to this old one, but no-one answered it.
You can make "test builds" available immediately via TestFlight for Internal Testers only.
If you're trying to get it to "outside" testers, then updates will have to go through Apple review.
From experience -- if you include enough information in the Reviewer Notes field, and you are only doing incremental changes, reviews can get done very quickly.
Note that if you are "updating" a test build with a whole new section to your app, yeah, the reviewer will likely put it through its paces.
Side note: I've also found it never hurts to begin your Reviewer Notes with something like "Hi Reviewer!! Hope you're having a great day! This is a minor update for our testers, fixing a couple layout issues, typos, etc."
For your other questions... just update the version number and archive / upload it as normal. It should automatically replace the current TestFlight version (for your testers to download).
I might not be the first one to ask this question but mine is slightly different from this and this
I uploaded a build for testflight review and it got approved. But now I have an improved version. I am aware that I can upload this updated version to itunesconnect.
The question is -
How long it may take to get approval for my latest build?
In case the latest build is still waiting for review, can I still continue testing (external testers) with my already approved version?
How long it may take to get approval for my latest build?
It will be approved immediately.
Once a Beta build is approved for testing, successive builds get approved immediately. In fact, at my firm, after submitting a build to the App Store, we just bump the build version & submit the app for Beta Testing to avoid Beta Review time to delay our testing.
All our Beta builds after the initial one have been approved immediately.
In case the latest build is still waiting for review, can I still continue testing (external testers) with my already approved version?
Yes, but doesn't matters coz of above^
Answer to question 1 :
It depends, how long did it take for your last build ? Did you change a lot of code ? It may vary between 2 to 10 days (approximately).
Answer to question 2 :
Of course you can, when you will want to test your lastest build, you will be asked to remove from testing the current build. This is implemented in a way that you can be waiting for review on your lastest build but still test a recent build of your application.
If you have any other question about TestFlight/Release feel free to ask but keep in mind that a lot of similar questions had already been asked/answered.
Hope it helped.
We submitted for review. We got approved. I found a bug that's pretty destructive to our leaderboards. We have a low time leaderboard and the time is submitted for each character and then a total. For some reason, the check was disabled and the total is submitted each time. So of course, we are going to get super low numbers (1/7th of the total) on the board. I know we can prune some of the top number and issue an update. That's all I can think to do.
I know we can patch but users aren't obligated to update.
What would you recommend? Should we patch and wait to launch?
So I'm guessing what your question is now, but first off, I have a question: is the app already visible and downloadable for users?
If not, cancel the process, fix the bug and re-upload the app for AppStore-approval.
If it is, then just fix the bug asap and upload the new binary.
Currently an update to my iPhone application has been in review for over 10 days!!!
In that period of time I've been able to work out a few bugs and even add some small new features to my application. I know that it is possible to reject your binary, but I would rather go a head a publish my application then send apple a better version 1.1.1...
So basically my question would be if I rejected my apps binary and submitted one right after would my app get pushed to the bottom of the review pile or would I keep my spot in line (since I've already been waiting for 10 days)?
No, rejecting a binary and immediately resubmitting a new one will not maintain your place in line: you would be knocked back to the start of the queue. I base this on my own experience, having rejected and resubmitted binaries a few times in the past.
Now, you might be thinking: "OK, what about the expedited review process?"
I can share some experience with that: With my latest app, I was in the same position you were in but I decided to go ahead and release 1.0 and then submit 1.0.1 soon afterwards. When 1.0 was approved and released, Apple chose it for the "New & Noteworthy" section. All of a sudden the app was getting a lot of exposure—and complaints about a bug that I had fixed in 1.0.1. I submitted 1.0.1—and as well as a request for expedited review—which was approved. 1.0.1 was released about 24 hours later.
So, you'll have to weigh the pros and cons for your own app, but I hope this info helps. :)
Yes it would, rejecting and resubmitting the binary will place you at the bottom of the review queue. It's unfortunate, but there is no work around.
If Apple allowed that then many devs would start uploading their beta version while trying to fix those last few bugs.
I had the same issue. I had submitted my app and it was in review. I was asked to change some metadata and resubmit the app. While doing that, I discovered a UI issue and fixed it. I was in a dilemma as to keep the current binary and release a version 1.01 or upload the new version. I did not want to send my first app with an issue so, I went ahead and rejected the binary and uploaded the new one. I immediately contacted Apple developer technical support. They claim that "The review time will not be affected and that our internal systems do have process your build before it can be reviewed (verifying it’s general correctness and resigning your app for the store), which can add some delay. However, that delay is fairly small and is only a minor factor in review time. More to that point, any delay here is much smaller than the delay of a new submission." I hope that is true and hope my app is not stuck in the "waiting for review or in review" limbo :(.
What are some things and techniques I can do to minimize the time it takes for my apps/updates to be approved for the App Store? Do smaller updates generally take less time, and do paid applications take longer than free ones? What about the size of the binary?
In my experience, everything takes exactly the same amount of time. You sit in the queue for 6 days, then they review it for an hour or so (much less for updates), and you're either in, or rejected. If you are rejected, it will take a few more days to work through whatever the issue was.
So the only way to take less time, is don't be rejected. :) Seriously, though, go read the developer agreement and the "do this and we'll reject you" document.
They aren't even looking at your app for that 6 day "cooling off" period, so I can't imagine what you could do to make it go faster. (Although I've heard that there is a mechanism for expedited updates in emergencies; but I have no first-hand experience with that).
I cannot post a comment yet, so I am posting this as an answer to your question based on my experience submitting new apps, as well as updates to existing apps in iTunesConnect.
Unfortunately there really isn't anything you can do to speed up the process, aside from fixing the issues in your app if it gets rejected, and re-submitting asap.
Apple allows you to request an expedited app review.
https://developer.apple.com/contact/app-store/?topic=expedite
Please note: If you're facing extenuating circumstances, you can request the review of your app to be expedited by completing the form below. Expedited reviews are granted on a limited basis and we cannot guarantee that every request will be approved.
I have personally used it twice. Once for a cosmetic issue in an app, which was rejected. Another time for a critical bug fix, which was accepted. I wrote a very detailed explanation of what my application did, what the bug was, why the bug was important to our (Mine and Apple's) customer.
One thing I have found is that free apps versus paid apps sometimes take different amounts of time.
For example I have a paid and free version of the same app. I submitted an updated for both one right after the other. First I submitted the free version, then I submitted the paid version immediately after. For some reason the paid version went into review, and was approved a day later, where as the free version is still waiting for review even know I submitted it first. I suspect that free and paid apps have different 'queues' or 'priorities' over at apple.
You can request an expedited review in emergencies. I used it once and the update was available about one or two days later.
However, they say, the expedited review will only be granted in limited cases. So I wouldn't use it if not absolutely necessary.
You can request the expedited review in iTunes Connect. I think the option was on the detail page for an app which is 'Waiting for Review'. There was also a list, in which cases an expedited review can be granted.
App approval times will vary depending more on what else is going on, and can otherwise vary for no obviously predictable reason. I've seen a small update to a simple app take longer to approve than a new large app with lots of features.
Maximum app review times seem to be around the days that lots of other developers are submitting apps, near some major holidays, shopping seasons, or when Apple has just released some OS update, app service or new device. Shorter wait times can sometimes be had by avoiding these longer review time periods. There are services that track the number of new apps introduced per week. Look for the nulls.
Staying well away from any hint of violating any of Apple's App store rules or guidelines, or anything else that can be seen as controversial, also helps not getting hit by a long (additional time required) review time. Other factors seem to make less difference.
Take a look Apple review support
Once you've submitted your app for review, you can view its status in the My Apps section of iTunes Connect or on the iTunes Connect App for iPhone and iPad. Review times may vary by app. On average, 50% of apps are reviewed in 24 hours and over 90% are reviewed in 48 hours. If your submission is incomplete, review times may be further delayed or your app may be rejected. Once your app has been reviewed, its status will be updated and you will be notified.
I tried to use the expedited review for an app for a skistation, so it would be available before the winter season started and it was declined.
You need obviously a very good reason like a big security issue etc to get a expedited review.
Step 1:
Related to your project, note what is the third party libraries are involved and make a note what makes it rejected in apple store.
Step 2:
Make your code stable and keeping in mind about rejection points which you cant keep
(i mean like really stable no warnings, no chance with wrong icons, no chance with mistakes).
Step 3:
Finally, then decide to send for review
That will at-least speed up your process. once you get rejected then its a bad, you have to really wait longer. (from experience saying)