Skip to content
Tosin Peter

HomeBlog

Guideline 2.1(b): fix in-app purchases not loading in review

App rejected because in-app purchases don't load? Real causes behind Guideline 2.1(b), a fix checklist for Expo, Flutter and RevenueCat, and how to resubmit.

Tosin Peter12 min read

  • App Store
  • iOS
  • Payments
  • RevenueCat

If Apple rejected your app under Guideline 2.1(b) because your in-app purchases “do not load”, the reviewer opened your paywall and saw no prices, an endless spinner or an error. Most of the time the code is fine. The cause is usually one of three things: your first subscription wasn’t submitted with the app version, a business or product setting in App Store Connect is incomplete, or your paywall has no way to recover when the store is slow.

Below is how to tell which one you’ve hit, how to fix it, and how to resubmit so you don’t lose another week to a third rejection.

What does Guideline 2.1(b) actually require?

Short answer: Guideline 2.1(b) says every in-app purchase you’ve configured must be complete, up to date, visible to the reviewer and working. If the reviewer taps “Upgrade” and nothing loads, or a product you created in App Store Connect can’t be found in the app, the app is incomplete and gets rejected. If a product can’t be reviewed for a good reason, you must explain why in the review notes.

The full text is in Apple’s App Review Guidelines, under 2.1 App Completeness. It sits next to 2.1(a), which covers crashes, placeholder content and missing demo accounts. Reviewers often bundle the two together, so read the whole rejection message.

Why in-app purchases load for you but not for App Review

This is the part that drives founders mad. Everything works in TestFlight, the paywall shows the right prices on your phone, and the reviewer still sees nothing.

There are a few reasons this happens:

  • The products were never sent to review. Your TestFlight build can fetch products that are still waiting to be submitted. Review is a different story: the products have to be part of the submission.
  • Sandbox can test things production can’t. TestFlight runs purchases in Apple’s sandbox environment, which reads your App Store Connect setup but doesn’t need the products to be approved. So a working TestFlight build proves your code works, not that the submission is complete.
  • The review device is slow, or the store is. Apple’s own troubleshooting note, TN3186, admits that purchases can be missing or unresponsive during review. A paywall that waits forever for products, with no timeout or retry, turns a slow response into a rejection.
  • Something changed after you tested. An expired agreement, a renamed product ID or a new build with a different bundle ID can break loading without touching a line of purchase code.

Developer forum threads from this year show all of these. One founder on the Apple Developer Forums was on their third 2.1(b) rejection in September 2026, with every product correctly configured and TestFlight working. Another, using Expo and RevenueCat, had prices showing as a dash only during review. Neither got a useful reply from App Review, which is why it pays to rule out every cause on your side before you resubmit.

Fix 1: Submit your first subscription with the app version

This is the most common cause on a first launch, and most guides skip it.

Apple’s rule is that the first in-app purchase of each type (consumable, non-consumable, auto-renewable subscription, non-renewing subscription) must be submitted with a new app version. If you submit the app on its own, or submit the subscriptions on their own, the reviewer gets a build whose products aren’t in the review. They don’t load, and you get 2.1(b).

How to fix it:

  1. In App Store Connect, open your app and go to Monetization → Subscriptions (or In-App Purchases).
  2. Open each product and fill in everything it asks for: price, at least one localization (display name and description) and the review screenshot of your paywall. A subscription also needs to sit in a subscription group, and the group needs its own localization.
  3. Go to your app version page, find the In-App Purchases and Subscriptions section and add every product you want reviewed.
  4. If a new subscription group hasn’t been approved yet, include the group in the same submission. The version, the group and the products all go in together.
  5. Submit for review once, as one submission.

If the In-App Purchases and Subscriptions section doesn’t show up on the version page, the usual reason is a product with missing information. Go back to step 2. If a product is stuck in a rejected state, fix what the rejection says and resubmit it alongside the new build, not separately.

After the first product of a type is approved, you can submit more products of that type without a new app version.

Fix 2: Check agreements, banking and tax

If any of these isn’t active, StoreKit quietly returns no products. There’s no error that tells you why.

In App Store Connect, go to Business (formerly Agreements, Tax, and Banking) and check:

  • The Paid Applications Agreement shows as Active. Free apps don’t need it, so founders who created the account for a free app first often miss it.
  • Bank account and tax forms both show as Active, not “Processing”.
  • Your Apple Developer Program membership is active. If it expired and you renewed, RevenueCat notes that agreements can take up to 24 hours to work again.

The Account Holder has to accept new agreements. If someone else set up the account, they need to log in and do it.

Fix 3: Check product IDs, bundle ID and capability

Apple’s TN3186 lists these as the reasons products go missing. Go through them in order:

  • Product IDs match exactly. pro_monthly in the app and pro.monthly in App Store Connect is a different product. With RevenueCat, check the ID in the RevenueCat dashboard too.
  • Bundle ID matches. The bundle ID in your build must match the app record in App Store Connect, character for character. In Expo it’s ios.bundleIdentifier in app.json or app.config.ts. In Flutter it’s in the Xcode project under ios/Runner. In RevenueCat it’s in the app’s settings, and it’s case-sensitive.
  • The In-App Purchase capability is on for that App ID in Certificates, Identifiers & Profiles, and the App ID isn’t a wildcard. Wildcard IDs can’t test purchases.
  • Every product has a price and a localization. A product without either won’t be returned.
  • Country availability. If a product isn’t available in the reviewer’s storefront, it won’t load for them.

After a change in App Store Connect, Apple says it can take up to an hour to show up in the sandbox. Wait before you assume the fix didn’t work.

Fix 4: If you use RevenueCat, check its setup too

RevenueCat sits between your app and StoreKit, so there are a few more places for the chain to break. Its offerings troubleshooting guide covers them; these are the usual culprits:

  • In-App Purchase Key (P8) uploaded. RevenueCat says the key is required for every App Store app, and on newer SDKs (React Native 8+, Flutter 7+, iOS 5+) purchases fail to record without it. Create it in App Store Connect under Users and Access → Integrations → In-App Purchase, upload the .p8 and add the Issuer ID.
  • App-Specific Shared Secret added as well.
  • A current offering exists. One offering must be marked as current, and each package in it must have an iOS product attached. If offerings.current is null, this is usually why.
  • The right API key. iOS keys start with appl_. Passing your Google key, or a key from another project, loads the wrong (or empty) setup.

RevenueCat’s dashboard shows a product as Ready to Submit once its App Store Connect metadata is complete. That’s a good quick check before you submit.

Expo and AI-built apps: Expo Go can’t test real purchases

If your app was built with Rork, Bolt or another tool on Expo, note this: react-native-purchases runs in a mock Preview API Mode inside Expo Go. Your paywall will render, but no real product ever loads. RevenueCat’s Expo guide says you need a development build (expo-dev-client and EAS) to test real purchases. Test the exact build you submit, on a real device, signed in with a sandbox Apple Account.

Also check that your Xcode scheme has no StoreKit Configuration file selected for the build you ship. A local .storekit file is great for the simulator, but it replaces the real store.

Fix 5: Make the paywall survive a slow store

Even with a perfect setup, the review sandbox can be slow. If your paywall shows a spinner until products arrive, a 20-second delay looks exactly like a broken app.

Give the paywall three states instead of one: loading, loaded, and failed with a Try again button. Add a timeout and a couple of automatic retries. Never show $0.00, a blank price or a dash.

In React Native or Expo with RevenueCat:

import Purchases, { LOG_LEVEL, PurchasesOffering } from "react-native-purchases";

Purchases.setLogLevel(LOG_LEVEL.DEBUG); // remove or lower for production

function withTimeout<T>(promise: Promise<T>, ms: number): Promise<T> {
  return Promise.race([
    promise,
    new Promise<T>((_, reject) =>
      setTimeout(() => reject(new Error("Timed out loading products")), ms),
    ),
  ]);
}

export async function loadOffering(retries = 2): Promise<PurchasesOffering> {
  for (let attempt = 0; attempt <= retries; attempt++) {
    try {
      const offerings = await withTimeout(Purchases.getOfferings(), 10_000);
      if (offerings.current && offerings.current.availablePackages.length > 0) {
        return offerings.current;
      }
    } catch (error) {
      console.warn(`Offerings attempt ${attempt + 1} failed`, error);
    }
    await new Promise((r) => setTimeout(r, 1500 * (attempt + 1)));
  }
  // Let the paywall show an error state with a "Try again" button.
  throw new Error("No products available");
}

The same idea in Flutter with purchases_flutter:

import 'package:purchases_flutter/purchases_flutter.dart';

Future<Offering> loadOffering({int retries = 2}) async {
  for (var attempt = 0; attempt <= retries; attempt++) {
    try {
      final offerings = await Purchases.getOfferings()
          .timeout(const Duration(seconds: 10));
      final current = offerings.current;
      if (current != null && current.availablePackages.isNotEmpty) {
        return current;
      }
    } catch (e) {
      // Log it; the next attempt may succeed.
    }
    await Future.delayed(Duration(milliseconds: 1500 * (attempt + 1)));
  }
  throw Exception('No products available'); // show a "Try again" state
}

While you’re on the paywall, check the rest of what review looks at there. Guideline 3.1.2 asks you to describe clearly what the user gets for the price before they subscribe, so show the price, the billing period and what’s included. Link to your privacy policy and terms of use from the paywall as well.

How to resubmit after a 2.1(b) rejection

Once you’ve gone through the fixes, a careful resubmission saves another round:

  1. Upload a new build if you changed any code or config. If you only fixed App Store Connect settings, you can usually resubmit the same build.
  2. Attach the products to the version again and confirm they’re all in the submission.
  3. Write clear review notes. Apple’s guidelines ask for detailed explanations of in-app purchases in the notes. Say where the paywall is (“Tap Upgrade on the Profile screen”), which products the reviewer should see, and give a demo account if the paywall is behind a login.
  4. Reply in App Review with a short message explaining what you fixed. Keep it factual.
  5. Don’t release the app before the products are approved. If you release first, real users get the same empty paywall.

If you’ve been rejected twice with a correct setup, mention in your reply that products load in TestFlight and that you’ve added a retry. Sometimes resubmitting the same build is all it takes, but only after you’ve ruled out everything above.

Pre-submission checklist for in-app purchases

Run through this before every submission that touches purchases:

  • Paid Applications Agreement, bank and tax all show Active
  • Each product has a price, localization and review screenshot
  • Subscriptions are in a group, and the group has a localization
  • First products of each type are attached to this app version
  • Product IDs match in code, App Store Connect and RevenueCat
  • Bundle ID matches everywhere; In-App Purchase capability is on
  • RevenueCat has the In-App Purchase Key, shared secret and a current offering
  • Tested the release build (not Expo Go) on a real device with a sandbox account
  • No StoreKit Configuration file in the release scheme
  • Paywall has loading, error and retry states; no blank prices
  • Price, period, privacy policy and terms are visible on the paywall
  • Review notes explain where the paywall is and include a demo login

When to bring in a developer

Most 2.1(b) rejections are fixable in an afternoon once you know where to look. It’s worth getting help when you’ve been rejected more than twice, when the app was generated by an AI builder and nobody on the team knows how the purchase code works, or when purchases go through but users don’t get what they paid for. That last one is an entitlement or webhook problem, and it costs you refunds and reviews, not just a delay.

If your Rork, Expo or Flutter app is stuck in review over in-app purchases, I can audit the App Store Connect setup and the purchase flow, fix it, and resubmit with you. Start with how I fix Rork apps, see my launch and rescue services, or tell me what the rejection says.

FAQ

Why do my in-app purchases work in TestFlight but not in App Review?

TestFlight uses Apple’s sandbox, which can return products that were never submitted for review. App Review only sees products that are part of the submission. Also, the review sandbox can be slow, so a paywall without a timeout and retry can look broken there even when your setup is right.

Do in-app purchases need to be approved before I test them?

No. In the sandbox and TestFlight, products load once their metadata is complete and your agreements are active. Approval only matters for the live App Store. Apple says changes can take up to an hour to show up in the sandbox.

Can I submit in-app purchases without a new app version?

Only after the first product of that type has been approved. Your first subscription, first consumable and so on must go in with an app version. After that, new products of the same type can be submitted on their own.

Why is RevenueCat’s offerings.current null?

Usually because no offering is marked as current, a package has no iOS product attached, or the product IDs don’t match App Store Connect. A missing In-App Purchase Key or an inactive Paid Applications Agreement can also stop products loading. Turn on debug logs to see which.

How long does it take to resubmit after a 2.1(b) rejection?

Fixing the setup is often quick, but each review round adds time. Get everything on the checklist right before you resubmit, so you only need one more round.

Further reading

Building something like this?

Tell me about it and let's see if I can help.

Work with me

More posts