Your submission gets rejected under Guideline 2.1 with language like “We were unable to evaluate the [team sharing / AI chat / Pro analytics] feature because it appears to require [a paid subscription / an admin role / an invite].” Your app is technically working; the reviewer simply hit a real gate (paywall, role, invite, region) that the demo credentials you provided didn’t let them pass. They tapped around, couldn’t unlock the feature in their 30-minute review window, and rejected.
Reviewers will not pay for your subscription, request an invite from your back office, or VPN themselves into a different country to test your features. The fix is to give them a “reviewer profile” account with every entitlement pre-granted server-side, plus a notes block walking them straight to the gated feature without detours.
Common causes
Ordered by hit rate.
1. Demo account is on the free tier; rejected feature is paid
You created a sandbox account and documented it in App Review notes, but server-side that user is on the Free plan. The reviewer logs in, tries to use the Pro feature, hits the paywall. They don’t have a credit card to subscribe; they reject.
How to spot it: Look up the demo account in your database. Check subscription_status or plan. If it’s not the highest tier, this is the cause.
2. Feature requires an admin or team-owner role
Your collaboration feature only shows for users with role = admin or role = owner. The demo account is a regular member of a sample workspace. Reviewer can’t get to admin settings, can’t see the feature.
How to spot it: In your role / permissions table, find the demo user’s role. If it’s not the highest, the reviewer is locked out.
3. Region-locked feature invisible from Apple’s review location
Reviewer is in Cupertino or Beijing (China review). Your feature is gated to region == "JP". The feature doesn’t even render its UI for the reviewer, so it looks missing.
How to spot it: Check your feature gating logic for any if region in ['US', 'JP', ...] checks. If reviewer’s IP / device region doesn’t match the allow list, you need a VPN-friendly path or a reviewer-mode bypass.
4. Invite-only feature accidentally requires an invite for reviewers
You shipped a “beta program” feature behind an invite code. The reviewer doesn’t have a code. They can’t try the feature without one. Even when the feature is documented in your release notes, Apple can’t evaluate it.
How to spot it: Search your code for any invite-code or feature-flag check that the demo account doesn’t pass. List every such gate; reviewer must pass all of them.
5. Required external service unreachable from reviewer environment
Your B2B app needs to talk to a customer’s on-prem SSO provider, a corporate VPN, or a partner API that’s IP-whitelisted. Reviewer’s network can’t reach it; SSO redirect fails, login dies.
How to spot it: Try your login flow on a public Wi-Fi network from outside your corporate IP range. If SSO or any backend call fails, the reviewer hit the same issue.
6. New gate added in this release without updating reviewer notes
Last release the demo account worked. This release you added an entitlement check that the demo account fails. Reviewer notes weren’t updated to match, and now you have a regression on access.
How to spot it: Diff this release’s feature-gating code against the previous version’s. Any new check that the demo user’s data doesn’t satisfy is the regression.
Information to collect
- The reviewer’s rejection text including the cited feature.
- A list of every gate in your code: subscription, role, region, invite, A/B test cohort, feature flag.
- The demo account’s current state in each gate’s relevant table.
- Whether your app has the concept of a “reviewer mode” or special override.
- Apple’s egress IP / region (you can sometimes ask via Contact App Review).
Shortest path to fix
Step 1: Build a “reviewer profile” account
Create a single account with every entitlement pre-granted server-side. Standard recipe:
UPDATE users SET
plan = 'pro_plus',
role = 'owner',
region_override = 'US',
invite_codes_consumed = ARRAY['*'],
is_internal = true
WHERE email = 'apple-review@yourdomain.com';
UPDATE workspaces SET
plan = 'enterprise',
feature_flags = ARRAY['*']
WHERE owner_id = (SELECT id FROM users WHERE email = 'apple-review@yourdomain.com');Pre-seed sample data so the home screen lands on a populated workspace.
Step 2: Write per-feature reviewer walkthroughs
For each gated feature, write a numbered step list in App Review notes:
TO TEST PRO ANALYTICS
1. Sign in with the demo account above.
2. Tap "Analytics" in the bottom navigation.
3. Tap "Pro Dashboard" — this is paid, but pre-unlocked for this account.
4. Expected: a chart with sample data from the last 7 days.
TO TEST TEAM SHARING
1. Sign in with the demo account (this account is the team owner).
2. Tap "Team" in Settings.
3. Tap "Invite Member" — copy the invite link (don't send).
4. Open the link in another browser; expected: invite acceptance screen.Step 3: Add a reviewer-mode toggle for features that can’t be entitled
Some features (real bank connection, real hardware, third-party SaaS that requires a real customer) cannot be granted via entitlement. For these, add a build-time flag that mocks the integration when the app detects the reviewer profile:
let isReviewerAccount = currentUser.email.hasPrefix("apple-review")
let bankClient = isReviewerAccount ? MockBankClient() : RealBankClient()In notes:
REVIEWER MODE
Bank connection uses mock data when signed in as apple-review@yourdomain.com.
Tap "Connect Bank" — sample transactions appear immediately.Step 4: Handle region-locked features
For features gated by region, either:
- Override the demo account’s region server-side (recommended):
region_override = 'US'. - Provide explicit VPN guidance in notes: “Set device region to United States in Settings → General → Language & Region for live scores feature.”
REGION REQUIREMENTS
Live scores feature is available only in US/CA/UK.
Demo account has region_override='US' set server-side; no VPN needed.Step 5: Resubmit with the new notes
In App Store Connect → App Information → App Review Information, paste the per-feature walkthroughs from Step 2-4. Then App Store tab → tap build → Submit for Review.
Most reviewer-access fixes are notes + server config only; no new build required.
Step 6: Reply in Resolution Center
Quote the reviewer’s question and point at the new walkthrough:
“Thank you for the feedback. We have updated App Review notes with a step-by-step walkthrough for the Pro Analytics feature. The demo account is now pre-set to the highest tier; please tap ‘Analytics’ on launch.”
How to confirm the fix
- A cold install + sign-in with the demo account lands on a populated workspace with all features unlocked.
- Each gated feature in the App Review notes walkthrough is reachable in <60 seconds.
- A non-developer team member following only the notes can reach every gated feature.
- Resubmission moves from Metadata Rejected to Waiting for Review within 1-2 hours.
If it still fails
- Reply in Resolution Center with a 30-second QuickTime recording of you logging in as the demo account and reaching the cited feature.
- Verify the demo account’s entitlement in your database — sometimes a deploy reverts seed scripts.
- Add a second demo account at a different entitlement tier (e.g., free + pro), in case the reviewer wants to see the paywall flow specifically.
- As a last resort, request a phone call from App Review and walk the reviewer through it live.
Prevention
- Maintain a “reviewer profile” seed script that runs on every release, granting every entitlement to a known email.
- When adding any new feature gate, update the seed script and App Review notes in the same PR.
- Add a release-checklist item: “non-dev tester signs in as reviewer profile, reaches every release-cited feature in <2 minutes.”
- Avoid pairing a new feature gate with a tight release deadline; gating is the #1 cause of preventable rejections.
- Tag the reviewer profile account
is_internal = trueso it doesn’t pollute analytics or billing.