Connect the App Store

Connecting the App Store lets Voidhash validate StoreKit transactions on the server and receive subscription lifecycle updates from Apple. Do this once your app and its subscription products exist in App Store Connect.

Creating keys requires an Account Holder or Admin in App Store Connect. An App Manager can complete the other steps.

Before you connect

Confirm the following in App Store Connect:

• The Paid Apps Agreement is active, and banking and tax details are complete.
• The app's bundle identifier matches the one in Xcode.
• At least one auto-renewable subscription exists.
• You can create and download an In-App Purchase key.

Apple's In-App Purchase setup overview describes the account prerequisites in more detail.

Configure Voidhash

In Studio, open Settings → Payment providers → App Store. Work through the sections in order.

Connect products

Open each Voidhash product and add the matching App Store subscription product ID. Product IDs cannot be changed in App Store Connect, so copy them exactly.

To sell a promotional offer from a paywall, add it under Promotional offers with the offer ID your paywalls use and its identifier from App Store Connect. Voidhash signs it with the In-App Purchase key from this configuration. See Offer a discount.

Product metadata can take time to reach Apple's sandbox. If useProducts() returns null right after a change, wait and retry before you change your app code.

Non-renewing subscriptions

Apple does not record when a non-renewing subscription ends, so Voidhash takes its length from the product you map it to:

• Subscription product with a billing duration. Each purchase grants access for that duration, starting when it was bought. A purchase made while earlier access is still running starts its own period; it does not extend the earlier one.
• One-time or consumable product. The purchase is recorded like any purchase of that kind. A one-time product grants access that does not expire.

A refund or revocation from Apple ends the access, as it does for other products.

Optional settings

• Small Business Program. Add the effective dates only if your account participates.
• Apple Server Notification forwarding URL. Receive a copy of each verified Apple notification on a public HTTPS endpoint. See Forward Apple Server Notifications.
• StoreKit development assets. Upload the subscription-offer key and the local testing certificate only when your Xcode test setup needs them.

Verify

1. Build the app with the same bundle identifier.
2. Sign in with a Sandbox Apple Account.
3. Load the product and confirm the localized displayPrice appears.
4. Complete a purchase and check for an active grant in useCurrentPerson().
5. Restore purchases after reinstalling or resetting the test app.

See Make and restore purchases for the client flow on your platform.

Sandbox purchases in your published app

A purchase made with a Sandbox Apple Account, in TestFlight, or by Apple's App Review is free and appears in Studio's Sandbox environment. By default it also unlocks access in the build you publish: your app sends the same requests from TestFlight and from the App Store, so Voidhash cannot tell those builds apart, and App Review buys with a sandbox account in the build you submit. Google Play test purchases work the same way.

The catch is that a tester's sandbox purchase keeps unlocking that account in the store build, for as long as the purchase lasts. A free sandbox lifetime purchase unlocks it for good.

To stop this, turn off Unlock access in production apps under Settings → General → Sandbox purchases in Studio. Production apps and secret-key entitlement checks then count only real store purchases. The change applies at once, to sandbox purchases already made too.

Sandbox purchases are still validated and recorded either way, and webhooks still deliver them, with environment set to sandbox. If your backend grants access from webhooks, check that field yourself.