in-app-purchases

StoreKit 2 in-app purchases are implemented by configuring products in a .storekit file, creating a centralized StoreManager to observe Transaction.updates, and handling consumables, non-consumables, and auto-renewable subscriptions. This approach replaces the older StoreKit API with a modern, async/await workflow for product setup, transaction handling, and receipt verification.

Use a testing-first workflow with a .storekit configuration file to simulate purchases, subscriptions, and restores in the sandbox environment. Write unit tests that validate transaction observation, subscription status changes, and receipt verification logic without hitting the App Store, ensuring your StoreManager handles all purchase flows correctly.

Monitor auto-renewable subscriptions by observing Transaction.updates to track active, expired, and revoked states. Implement a restore-purchases function that re-fetches the transaction history and updates your centralized observable state, allowing users to restore previous purchases across devices.

Yes, server-side receipt validation is essential for production in-app purchases. Verify receipts against Apple's IAP server APIs to prevent fraud and confirm legitimate transactions, especially for non-consumables and subscriptions where users expect persistent access across reinstalls and devices.

Yes, StoreKit 2 supports consumable products through the same unified API as non-consumables and subscriptions. Handle consumables by observing finished transactions, updating user inventory in your app state, and marking transactions as finished to enable repeat purchases.

StoreKit 2's Transaction.updates stream persists across app launches, so unfinished transactions are re-delivered when the app reopens. Your centralized StoreManager must replay pending transactions on startup and call finish() only after confirming the purchase was processed, preventing lost or duplicate transactions.