“sandbox”

@amacia See TN3186: Troubleshooting In-App Purchases availability in the sandbox identifies common configurations that make your In-App Purchases unavailable in the sandbox environment. With the production RevenueCat API key (iOS appl_..., same as the submitted build), everything works on local device but not when I download it from TestFlight....For IAP in WAITING_FOR_REVIEW, should App Review always use an Apple Sandbox account to test subscriptions until the product is fully approved? Apple reviews your In-App Purchases (consumable, non-consumable, auto-renewable subscription, and non-renewing subscription) in the sandbox, the same environment you use to test your products. TestFlight also uses the sandbox for In-App Purchases This environment uses data you configure for your app in App Store Connect when you call StoreKit APIs in your app. For Apple to review your products, they must exist in App Store Connect and you must submit them for review. Is it document

To debug your issue, see TN3186: Troubleshooting In-App Purchases availability in the sandbox. Apple reviews your In-App Purchases (consumable, non-consumable, auto-renewable subscription, and non-renewing subscription) in the sandbox, the same environment you use to test your products. This environment uses data you configure for your app in App Store Connect when you call StoreKit APIs in your app. For Apple to review your products, they must exist in App Store Connect and you must submit them for review.

@selimce, @669miller , @Gascad , @slowfast , and @touchlinebet Apple reviews your In-App Purchases (consumable, non-consumable, auto-renewable subscription, and non-renewing subscription) in the sandbox, the same environment you use to test your products. This environment uses data you configure for your app in App Store Connect when you call StoreKit APIs in your app. For Apple to review your products, they must exist in App Store Connect and you must submit them for review. Same problem with non-renewable IAP. My review is rejected because of the IAP's were not seent in the sanbox environment. For us, it is seen in both xcode and testflight environments. Probably because of this bug in review view. Please follow these steps, then let me know about the outcome: Create a Sandbox Apple Account. On your testing device, sign into the above account. For more information, see Sign in to your Sandbox Apple Account for a development-signed app. Disable StoreKit Testing in Xcode in your Xco

[quote='823069021, natasha_m, /thread/823069, /profile/natasha_m'] What is the effective validity period of an Ad Hoc build? [/quote] My understanding is that: This is gated by the app’s provisioning profile. Ad Hoc provisioning profiles live for about a year. However, you can check this for yourself by dumping the provisioning profile. TN3125 Inside Code Signing: Provisioning Profiles explains how to do that. IMPORTANT Some types of provisioning profiles have an ExpirationDate property, which makes the expiration date very clear. In others you have to combine the CreationDate property and the TimeToLive property, the latter being a count of days. Development provisioning profiles have a similar limit, and you can work that out in the same way. [quote='823069021, natasha_m, /thread/823069, /profile/natasha_m'] If we distribute the app using a development (debug) build via provisioning profiles, what is the expiration timeline? [/quote] You need to distinguish between: Build configuration (Debug or Release) Co