App update stuck in "Waiting for Review" for 24 days (since Oct 9), no communication

Hello,

Our iOS app update has been "Waiting for Review" since October 9, 2026, with no status change or message from App Review.

App: LoveYug: Couple Games for Two
Apple ID: 6764535507
App Store: https://apps.apple.com/app/id6764535507
Version: iOS 2.0.1 (Build 61)
Submission ID: ee368da7-67ea-47b4-af79-6a0b301f3896

Timeline:

  • October 2: Version 2.0.1 was rejected under Guideline 1.1 for a keyword in our App Store metadata.
  • October 3: We removed it from the metadata in every localization, replied in App Review, and resubmitted.
  • October 9: We withdrew the submission to include a new build (61) and resubmitted the same day.
  • November 2: Still "Waiting for Review", with no further questions or issues reported.

What we have tried:

  • Requested an expedited review twice
  • Contacted App Review through the Contact Us form
  • Opened two Developer Support cases: 102988518785, 103012593576

None of these has received a substantive response.

Our app is already live on the App Store (version 2.0.0), and this update is already live on Google Play. iOS users are stuck on the older version, without the new features and fixes. We fixed the earlier issue the same day and have not changed the binary or metadata since October 9.

We are not asking for approval without review. We only want to confirm the submission is correctly queued and not stuck on a hold, or to learn whether we need to do anything else.

Could someone from App Review look at this submission or escalate it?

Thank you.

The Oct 9 withdraw-and-resubmit is the likely reason the clock restarted: a new build makes it a new submission, and earlier replies don't carry over. Things worth checking before contacting them again:

  1. App Review page: open the submission (not just the version) and look for an "Unresolved Issues" or "Developer Action Needed" state. A metadata rejection sometimes leaves a message there that the version page doesn't show.

  2. The 1.1 keyword everywhere: subtitle, keywords, promotional text, in-app purchase display names, and screenshots in every localization. If it's still in one place, they can sit on it.

  3. Put the history in App Review Information → Notes: "Oct 2 rejected under 1.1 for keyword X; removed from all localizations on Oct 3; build 61 adds bug fixes only." Whoever picks it up then sees it without the old thread.

  4. Don't withdraw again. One expedite request that cites a concrete user impact (a bug in 2.0.0 that 2.0.1 fixes) tends to get further than "please review".

If you ship regularly, consider phased releases so you can pause a bad update without needing a fast review.