App Review stuck in "Waiting for Review" for over 72 hours after replying to a rejection – Is anyone else experiencing this?

Hello everyone,

I'm looking for some advice because I'm not sure if this is normal or if there is currently a delay with App Review.

Here is my situation:

My app was initially rejected under Guideline 5.6. The issue was fixed immediately. The fix only required changing my Firebase Remote Config (no code changes or new binary were necessary). I replied to the App Review message explaining the fix and resubmitted the same version for review. Since then, the app has been stuck in "Waiting for Review" for more than 72 hours.

I have already:

Requested an expedited review. Contacted Apple Developer Support. Received no response so far.

My questions are:

Is anyone else currently experiencing unusually long "Waiting for Review" times? Does replying to a rejection with the same build place the submission in a different review queue? Would submitting a new build (with a higher build number) help, or would that simply restart the waiting time? Is there anything else I can do to get the review moving?

For those who have experienced this before:

How long did your review stay in "Waiting for Review"? What ultimately resolved the situation?

Any advice or recent experiences would be greatly appreciated.

Thank you!

Welcome to the forum.

If you browse rapidly in the forum, you'll see that's a frequent situation.

Your app was rejected, apparently for not respecting the code of conduct (5.6).

So it probably went to the end of the queue after this. Asking for expedited review is likely useless (so many are requesting).

 

Would submitting a new build (with a higher build number) help ?

Probably not, it could even make matters worse.

 

What ultimately resolved the situation?

Patience.

My guess is that you could get something after the weekend.

Don't forget to close the thread once resolved.

Good luck.

App Review stuck in "Waiting for Review" for over 72 hours after replying to a rejection – Is anyone else experiencing this?
 
 
Q