Hey guys, having a "what the hell" moment here, I just uploaded an update and it gave me an ITMS - 4000 error, possibly because of a bad bundle name. Okay, I can fix that.
Wait a minute...
I just got an email 2 minutes ago saying that "the status of your application has changed to waiting for review."
Huh? Anyone know why? I mean, I'm not complaining, just comfused.
You may want to investigate so you dont waste time. Your app could stay in queue for several days only to be rejected for an issue you could have fixed sooner. Just because the app was uploaded successfully, doesn't mean it is good to go; I would investigate further.
Related
Just checked the status on one of my iPhone applications and noticed it was rejected. However, due to complications the email account I have on the account is unavailable. So, that leaves me with absolutely no clue as to why the app was rejected.
Is anyone aware of any areas on apple's site that allows you to research why a specific app was rejected? Or am I stuck waiting the 2-3 days for a response from Apple support?
I think at the Resolution Center you can get your information. Take a look at http://developer.apple.com/appstore/contact/appreviewboard/index.html
There are can be variety of reasons for rejection. Known list of possible reasons will not help you, cause you really need to know exactly why they rejected it. Sometime you don't even need to re-submit application but simply change description.
You really should have email account available when doing any AppStore related activity.
I am unaware of any area on Apple's developer connection that lists this info. If your email server has been sending all your email to /dev/null, your best bet, after you fix and test your ADC email account, might be to resubmit the exact same binary again, with an explanation in the update notes, as that could well take less time than waiting for Apple support.
To solve this issue you would need or to email them again asking for a reply on the rejection message that states the reason for it, or resubmit the app and wait for them to review and reject it again.
Be sure to setup an email account that you are able to monitor.
The review after rejection starts usually quicker than when submitting a new app or new update, and so you would have a feedback in 2 or three days, that would be the same time they would take to reply you with previous rejection reason (if it is possible).
I would go for:
Setup the email and other info.
Resubmit the app and wait for the rejection again.
Good Luck!
Here is a good list of reasons that app's have been rejected for and it explains all of them.
http://iphoneincubator.com/blog/app-store/rejections
The 1.1 update of my App got rejected. Then, after making a change I uploaded it using the Application Loader, during uploading the Application Loader froze and I had to kill it myself. Then the status changed to “Upload Received”. So it seems the binary was uploaded anyway.
But now, it has been in “Upload Received” for 6 days (144 hours!). Normally it changes from “Upload Received” to “Waiting for Review” in a couple of minutes. iTunes Connect FAQ: “If your app has been in the Upload Received state for more than 24 hours, you should contact iTunes Connect Support through the iTunes Connect Contact Us system.”. Apple has not responded yet to my contact forms, I’ve used the contract form three times now….
In the meantime, when in status “Upload Received“ you can’t reject binary.
I'm not going to upload it using a different App name / ID, as my reviews and top list positions will be gone...
Any advice? Just wait? Anyone knows how to deal with this situation?
Cheers Jeroen
FYI, I fixed this by editing the screenshots and re-saved the metadata.
This issue was resolved by Apple on sep 3rd, after calling them (http://developer.apple.com/contact/phone.html). The phone call resulted in swift escalation within Apple.
They resolved it by putting my App in status "Waiting for review". After that, the normal process applied, after a couple of days it changed to "In review" and after 7 days total it changed to "Ready for sale".
So calling Apple would be the best action if the mails just won't get it done. I got some really standard email responses that didn't really indicate they were looking into the matter.
There is a specific selection under contact us for this very issue. Seems to be common for them to have this under the drop down. i would use this selection under contact us as it probably goes to a specific person that handles this issue.
Frequently Asked Questions:
Why is my app in Upload Received status for over 24 hours?
If your app has been delivered successfully but has the Upload Received status for more than 24 hours, there may be an issue with your binary. For additional support, use the Contact Us module.
If your app has been in the status Upload Received for over 24 hours, contact us.
Has anybody had the experience of Local Notifications being delivered from an app that has been uninstalled? I hesitate to ask since I can't reliably reproduce the issue, but we're receiving multiple reports of that occurring.
We're having an emergency debug session here, and since we barely know where to start looking for answers on this, wanted to see if anybody else has had this happen to them, as either a developer or as a consumer. Could this potentially be an iOS 4.0 bug?
Looks like there's a thread on it here: https://devforums.apple.com/message/253796
Likely an iOS bug.
I've been waiting on an iPhone app to go through the app store approval process. It's been in the queue for about two weeks now.
Apple recently added something to the dev center about reachability, pointing developers to their sample app. In my app, I'm posting to a URL on my server using HTTP - but I'm not doing a reachability check first. If the user tries to submit the request, it will eventually time out and they will see an error.
What are the chances that Apple will fail this app? I'm wondering if I should just quickly implement reachability and "reject binary" myself, submitting a new version. Might save me a couple of days if I'm just going to get rejected anyway.
Implement reachability, if your app uses the web and when there is no connectivity the app doesnt say something along the lines that "this is not working because you have no internet access" then 95 percent it will be rejected by apple
Sounds like you answered your own question to me - not handling that case is a serious UX problem you should definitely fix.
If I were expecting to deal with a reasonable, smart approval process, I would do exactly that -- fix the app to match their new documents. It's a classy move, implying you'd be a good citizen.
You may want to rely on someone who's been through the iPhone app store, though, for an answer with the right amount of cynicism.
I've submitted an app for the App Store via iTunes Connect, and the status is "In Review." I don't know if that means they actually started looking at it. I suspect it just means that it's been put into a reviewer's queue.
There's a tweak I'd like to add to it before it goes out. However, I don't want to update it if that means that hitting "Reject Binary" automatically sends it to the back of the overall queue again, and it has to wait another 3-4 weeks.
I realize that it's likely that no one knows how this works, but I figure it doesn't hurt to ask.
Yup, back of the queue. See the bottom question on this Apple Developer Connection page.
We've only had to do it once but it wasnt at all as bad as I had imagined and actually didnt take very long until the new binary got reviewed again. It's much better than releasing a buggy app...
Yes, a developer reject action on iTunes will result in the application being 'kicked out' from the current queue and put in the back of the queue. However, if you are lucky you can always try out expedite review, that could advance your review.