What does “missing subscription metadata” mean?
Your StoreKit products exist. Apple still will not approve them. Every subscription and in-app purchase needs its own display name, description, review screenshot, and pricing — in each localization you sell in. One missing field in one locale blocks the whole product.
What metadata does Apple require?
A localized display name and description for every subscription. A review screenshot showing the subscription in the app. Correct subscription group assignment and duration. Pricing set for every territory or a sensible default. For auto-renewables: the subscription must be assigned to a group, and the group needs at least one localized display name.
Why do AI-built apps hit this so often?
The agent wires up StoreKit, the paywall works in testing, and everyone assumes the App Store side is done. It is not. The product configuration in App Store Connect is a separate surface from the code, with its own per-locale requirements that no compiler checks.
How do you catch it before review does?
Check subscription state the same way you check build state: read what Apple actually has. AiSCent verifies StoreKit product configuration, per-locale metadata completeness, and review readiness, then re-verifies after you fill the gaps.