Anonymized internal case · 2026-09-23

Subscriptions were configured. Why were products still missing in review?

Separating store products, subscription groups, offerings, entitlements, build configuration, and review evidence prevented one dashboard screenshot from standing in for the full path.

Problem

Monthly and annual products existed, yet the review build did not consistently return the complete paywall. Several systems looked configured, but no single state proved that the final app used the correct bundle ID, API key, offering, and store products.

Approach

The workflow split evidence into store metadata, RevenueCat mapping, app configuration, signed artifact, and device runtime. Identity, version, and readback were recorded at every layer; an unreadable layer stayed unverified instead of borrowing success from its neighbor.

Result

The result was a repeatable subscription checklist and review-response evidence that distinguished code integration, dashboard configuration, device purchase availability, and reviewer acceptance. No account, revenue, user, or sensitive store data is disclosed.