Our build was rejected under Guideline 2.3.2 (Accurate Metadata) over subscription promotional images that were flagged as duplicates of, and too similar to, our app icon. The rejection was against the build, not the subscriptions directly.
At the time, all five subscriptions plus the subscription group were in "Submitted for Review" status, which meant they couldn't be edited directly.
Troubleshooting steps taken so far:
- Developer-cancelled each of the five subscriptions to get them out of "Submitted for Review" and into an editable state.
- Edited each subscription to remove the promotional image that triggered the 2.3.2 flag.
- Made changes to the Localization and Review Information fields on each subscription to force a new Save action.
- The Save completed successfully with no errors on any of the five subscriptions.
After this, all five subscriptions and the subscription group are showing "Removed" from the Review Status column of our iOS submission. However, "Developer Rejected" status still shows in the Subscriptions section of Monitization (ASC->Distribution). That status hasn't cleared despite the successful edit and save, and I'm not able to reattach the subscriptions to a build for a new review submission from this state.
Has anyone run into this — a subscription that was developer-cancelled, corrected, and successfully saved, but remains stuck on "Developer Rejected" instead of returning to a submittable state? Is there a separate action needed beyond edit-and-save (e.g., a distinct resubmit step, or removing and recreating the subscription) to move it forward from here?
Any guidance on the correct path would be appreciated — happy to provide additional screenshots or details if useful.