Ship It Checklist

Checklists /Ship to the App Store /Subscriptions

Critical

Attach the products to the version you submit

A product can be Ready to Submit and still not travel with this binary. On the version page, the In-App Purchases and Subscriptions section is where you attach the first submission of a product. If it is not attached, the reviewer cannot see it, and 2.1(b) is the usual reply.

How to check

  1. Open the iOS version you are submitting, not an older one.
  2. In In-App Purchases and Subscriptions, the products in this release should be listed.
  3. Submit the version after the products are attached. Attaching them later can mean a new submission.
  4. If a product was approved on an earlier version, you do not attach it again. Check status so you do not confuse the two cases.

Prompt

Fix prompt
Paste into Cursor or Claude Code
You are working in this iOS project. Do not add features.

Goal: Document which product ids must be attached to this version. Do not change purchase code unless an id is wrong.

The project may be Expo, React Native, Swift, a Capacitor wrapper, or a FlutterFlow export. Change only files that already exist.

Steps:
1. List the product ids referenced by the release build.
2. Note which ones are new and therefore need to be attached on the version page.
3. Do not remove a product id the paywall still shows.
4. Do not print certificates, private keys, API keys, or App Store Connect passwords.
5. Tell me which files you changed, and list anything I still have to do in Xcode or App Store Connect.

This uses the same ticks as the checklist page, saved in this browser.