Submitted build stuck in “Waiting for Review” after replacing an approved build (possible queue issue?)

App update stuck in “Waiting for Review” after replacing an approved build (possible queue issue?)

Hello,

I would like to know whether other developers are experiencing a similar issue with App Review this weeks.

App: Spherag IOT Platform: iOS Current build: 1.2.34 (234) Status: Waiting for Review

Timeline

  • Friday, July 24: build 1.2.30 was reviewed and approved successfully.
  • We decided not to release that approved build.
  • Monday, July 27: we removed it from release and submitted 1.2.31 (231).
  • Build 1.2.31 remained in Waiting for Review for about 3 days and never moved to In Review.
  • We then submitted 1.2.34 (234), Today, August 04: after waiting several days with no progress, we removed the submission and re-submitted the same build, 1.2.34 (234), which is currently still in Waiting for Review.

I have already opened two Developer Support cases regarding this issue, but I have not yet received a resolution.

What concerns me most is that, after submitting build 1.2.34, the version history in App Store Connect appears inconsistent and previous entries are displayed as 1.2.34 (234). This makes me wonder whether there could be a display issue or a problem with the review queue state.

All Agreements, Tax and Banking information are active, and all required metadata, privacy details, export compliance and age rating information are complete.

This delay is becoming difficult to manage operationally: one release is already blocked, a second release is now waiting, and a third release will likely be ready before the current submission is reviewed.

Has anyone experienced a new submission remaining in “Waiting for Review” for several days after withdrawing a previously approved build and submitting a newer build?

If so, did it eventually move to review automatically, or was any action from Apple required?

Thank you.

Submitted build stuck in “Waiting for Review” after replacing an approved build (possible queue issue?)
 
 
Q