Three rejections in a week for errors on the reviewer’s iPad, and a reviewer who couldn’t find the subscription the notes describe

I’d like to raise how our app’s review has gone, in the hope that someone at App Review sees it, and to ask whether other developers are seeing the same thing.

Our app is Suan, a sleep audio app. It’s iPhone-only. It has no server and no account, and one auto-renewing yearly subscription shown with Apple’s own SubscriptionStoreView.

What has happened:

30 Oct: submitted.
3 Nov: rejected under 5.1.1(iv) for the wording on our Apple Health screen. Fair enough. Fixed and resubmitted the same day.
5 Nov: rejected on three points:
5.1.1(iv) again, for a button label that was already there in the first review and wasn’t mentioned then;
2.1(b): the reviewer couldn’t find the In-App Purchase;
2.1(a): every audio download failed on an iPad Air (M3) on iPadOS 27.
We fixed all three. Every track now ships inside the app, so nothing downloads at all. The review notes say step by step where the subscription is: it appears straight after onboarding, it’s the first section in Settings, and it opens when you tap play on any track.

8 Nov: rejected under 2.1(a) for “an error during onboarding”, again on the iPad Air (M3). The reviewer’s screenshot shows Apple’s SubscriptionStoreView reporting “NSURLErrorDomain error -1009”. That error means the device is not connected to the internet. The screen is Apple’s own, loading our subscription from the App Store sandbox. Our onboarding makes no network requests.
So of the issues raised, two came from the review device having no connection, one was a subscription that the review notes explain how to find, and one was a button that passed the first review. None of them happen on our own iPhones. We’ve replied to every rejection in App Store Connect, and resubmitted each time within hours.

The Android version of the same app, with the same features, content and subscription, went through Google Play’s review and was approved.

Each round costs us two to three days, and we’ve now spent about two weeks on a launch that was ready at the start. I’d be grateful for a few things:

When the error in a screenshot is a network error like -1009, could reviewers check the device’s connection, or try again, before rejecting?
Could every issue be raised in one review, rather than a new one appearing after each fix?
Could reviewers read the review notes? For us they answered the question the rejection asked.
Has anyone else had StoreKit or network failures in review on iPad Air (M3) with iPadOS 27? I’ve seen a few threads describing the same thing. If anyone found a way past it, I’d love to hear it.

The quality of the testing effort has been pretty poor.

Thank you.

Does this forum have mods?

Is there anyone that can please look at my App review? Our luanch event is this weekend along side a book lunch.

Sorry you're going through this, especially with a launch this weekend. A few things that can actually move it, most urgent first:
Request an expedited review for the current build and mention the dated launch event: developer.apple.com/conta…. It isn't guaranteed, but a fixed launch date is the kind of reason it's meant for.

Reply to the 8 Nov rejection in App Store Connect with a short, factual note: -1009 is NSURLErrorNotConnectedToInternet, it comes from Apple's own SubscriptionStoreView, and onboarding makes no network requests. Attach a screen recording on an iPad running iPadOS 27 that shows onboarding, the paywall loading, and where the subscription is. A recording usually works better than notes for 2.1(b).

If it stalls again, appeal to the App Review Board or request a call with App Review: developer.apple.com/distr…

On the app side, one change is cheap and takes this failure mode off the table. Treat a failed product load as a normal state, not an error. Show "Couldn't load subscription options, try again" with a retry button, and let the user continue past onboarding instead of seeing the raw error. Reviewers judge what's on screen under 2.1(a), even when the cause is their network (developer.apple.com/app-s…). Testing once with Wi-Fi off on an iPad in iPhone compatibility mode shows exactly what they saw.

On the repeated new findings: each submission can be reviewed fresh, so new points can come up on screens that didn't change. It's frustrating, and a fair point to raise in the appeal, but it's not something the forum can override.

Is the 8 Nov build the one in review now, or have you resubmitted since?

On the -1009: you can't control the reviewer's network, but you can stop it being a rejection. What usually works for SubscriptionStoreView in review:

  1. Don't put the store view on the critical path of onboarding. Let users finish onboarding and reach the content even if products don't load; show your own "Couldn't load subscription options. Try again" state with a Retry button instead of the raw error.
  2. Preload and retry: call Product.products(for:) early, retry once or twice on failure, and only show the store view when products are loaded.
  3. Test the exact reviewer setup: iPhone-only apps are reviewed on iPad in compatibility mode. Run it on an iPadOS 27 simulator (or iPad) with networking off and on, and record that the app stays usable.
  4. In the reply: quote the error, say it means the device was offline, describe the new offline handling, and attach the recording. Ask the reviewer to list any other issues in one pass.
  5. With a dated launch, request an expedite for the new build and book an App Review appointment for the same week.

We made similar changes to the ones you've suggested and reubmitted it on the 16th.