Our app was reviewed on 8 October and returned under Guideline 2.1 (Information Needed) because the reviewer could not sign in with the demo account. The cause was on our side and was fixed the same evening: the review account now uses a fixed verification code, the App Review notes were updated with step-by-step instructions, we replied in the Resolution Center, and we resubmitted on 9 October.
Since then the submission has shown Waiting for Review with no further contact — 13 days as of today. The first cycle of the same submission also waited eight days before review. We requested an expedited review on 14 October and have had no reply to that either. Submission ID: 9f09ed47-0ac0-45d1-8b6c-af9c05c8e3bd.
We have verified the demo sign-in end to end against production and are available at any time if a reviewer needs anything. Two questions:
- Is there anything about a resubmission after a 2.1 note that places it in a different or slower queue than a new submission?
- Would cancelling and resubmitting the identical build as a new submission be the right move at this point, or does that risk losing a place in an escalated queue we can't see?
Thanks for any guidance.
I would not cancel and resubmit the identical build. You cannot see from App Store Connect whether it is in a separate queue, and creating another submission could just add another wait without fixing anything. Since the demo account and review notes are now verified, keep the current submission active and make sure those credentials remain available to the reviewer.
For the existing support follow-up, include the submission ID and state exactly what changed after the 2.1 issue, including that the fixed-code login was tested against production. An expedited request is only a request, so it may not get a separate response. If App Review needs access or more information, they can contact you through the Resolution Center.
