endless waiting for review

Question

Created 21h

Replies 3

Boosts 1

Participants 4

Hey everyone, I need to vent and also ask for some advice because I’m starting to lose my mind here. I submitted a new build for my app 10 days ago, and it has been stuck in "Waiting for Review" ever since. Not "In Review," just waiting in the queue. The App ID is 6759559007 I get that Apple has millions of apps to sift through, but come on. The App Store is a core part of the iPhone experience, and having a review team that moves this slowly feels like a bottleneck that shouldn't exist in 2026. It’s especially frustrating because:

There are no rejection messages, so I know it’s not a guideline issue.
I have a planned marketing push that is now completely out of sync.
There is zero transparency. The status just sits there mocking me.

Any advice on how to actually get a human to look at this? Should I reject the binary and resubmit to "bump" it, or is that just sending me to the back of the line? Feeling pretty hopeless here. Any insights would be hugely appreciated. Thanks

Boost

Answer 1

App Review OP

Apple

10h

Thank you for your post. We're investigating and will contact you in App Store Connect to provide further assistance. If you continue to experience issues during review, please contact us.

0

Answer 2

hichamw OP

10h

That is so bad. I had to email their leadership sadly.

2

Answer 3

Chase0823 OP

8h

My app has been stuck on "In Review" for an unusually long time. Typically, it takes 2–3 days to move from "Waiting for Review" to "In Review," and only about 3 hours from "In Review" to a decision. However, this time it's been sitting in review well beyond that window. I can also confirm from my database that no reviewer has logged in or created a test account yet, so it doesn't appear the review has actively started. I'm not sure what's causing the delay. I'd prefer not to request an expedited review at this point, but I may need to - I have a time sensitive pre-order launch I'm trying to get live as soon as possible. Has anyone experienced something similar? Any advice on next steps?

0