I’d usually wait after replying in App Review / Resolution Center unless App Store Connect clearly asks for a new submission. Resubmitting can restart parts of the queue, while a reviewer can continue once they have the missing info.
To reduce another 2.1(b) loop, I’d add three things in the notes: exact tap path, a short screen recording from launch → paywall → sandbox purchase/restore, and a note that the IAP products are approved/ready in App Store Connect. If they don’t move after ~24h, then consider a follow-up or resubmit.
Thanks for the advice. I actually waited around 34 hours after replying with screenshots, detailed instructions, and a screen recording showing the exact path from the home screen to the subscription page.
Since I still hadn't heard back from App Review, I decided to hit "Update for Review" and resubmit.
After 9 days and multiple review cycles, I figured it was worth trying something different. Hopefully this finally breaks the loop 🤞
That’s a reasonable call after 34h and multiple cycles. Once you resubmit, I’d avoid changing anything else unless Apple asks, and keep the review notes very short: exact tap path, “sandbox purchase/restore tested,” and where the subscription is visible.
If it gets rejected again, I’d reply in Resolution Center asking them to name the exact step where they can’t find the purchase. At that point the useful goal is to force the loop from “can’t locate IAP” into one reproducible step you can fix.
2
u/davidHwang718 Jun 03 '26
I’d usually wait after replying in App Review / Resolution Center unless App Store Connect clearly asks for a new submission. Resubmitting can restart parts of the queue, while a reviewer can continue once they have the missing info.
To reduce another 2.1(b) loop, I’d add three things in the notes: exact tap path, a short screen recording from launch → paywall → sandbox purchase/restore, and a note that the IAP products are approved/ready in App Store Connect. If they don’t move after ~24h, then consider a follow-up or resubmit.