Skip to main content
StoreKit Configuration files in Xcode let you test in-app purchases locally, without connecting to App Store servers. Upload the file’s public certificate to Qonversion and your local test purchases flow through Qonversion just like real ones — entitlements, analytics, and webhooks all work.
Uploading a certificate does not affect real users. Production receipts signed by Apple keep validating through Apple; the certificate is only used to validate receipts produced by your StoreKit Configuration file.
Official Apple guide: Setting up StoreKit testing in Xcode.

​
1. Create a StoreKit Configuration file

1

Add the file

In Xcode, go to File → New → File from Template, search for StoreKit, and choose StoreKit Configuration File. Save it.
2

Add your products

Inside the .storekit file, add the in-app products you want to test — consumables, non-consumables, and auto-renewable subscriptions.
3

Attach it to your scheme

Open Product → Scheme → Edit Scheme… → Run → Options → StoreKit Configuration and select your .storekit file.

​
2. Export the public certificate

Qonversion needs the public certificate from your StoreKit Configuration file to validate transactions.
1

Select the file

In Xcode’s Project navigator, select the .storekit file.
2

Save the certificate

From the menu bar choose Editor → Save Public Certificate and save the .cer file locally.

​
3. Upload the certificate to Qonversion

1

Open Stores settings

In the Qonversion Dashboard go to Project Settings → Stores.
2

Add the certificate

In the Apple App Store card click Add certificate, then drop or select your .cer file in the panel that opens.
Once uploaded, the StoreKit test certificate chip turns green. To stop accepting StoreKit Configuration receipts, click Remove on that chip.
Only .cer and .pem public certificates are accepted — never upload a private key or an Apple production certificate.

​
4. Run test purchases

Run your app in the Simulator or on a device using the scheme with your StoreKit Configuration file, and buy products as usual. Qonversion validates each transaction with your uploaded certificate, so local test purchases grant entitlements and appear in analytics just like real ones.
If you set an accelerated subscription renewal rate in your StoreKit Configuration file, we strongly recommend not reusing the same test account. Accelerated renewals create a new transaction every few seconds, so that account piles up test data very quickly.Periodically reinstall the app to start fresh from a new clientUid and keep accounts from getting cluttered. For ordinary test cases (no accelerated renewals) this isn’t needed — data won’t accumulate.

​
5. Manage and clear test data

Purchases made through your StoreKit Configuration certificate are tagged sandbox and show up in your test-mode analytics next to Apple Sandbox purchases. They are not removed when you reset StoreKit in Xcode.
Use a separate clientUid (user identifier) in your test build so StoreKit test data stays isolated from your real customers.
To clear StoreKit test data from Qonversion:
  • The whole project — on the Customers page, open the ⚙ chart settings and choose Reset StoreKit test data.
  • A single customer — open the customer and use Reset StoreKit test data next to the sandbox icon.
This removes only purchases made through the StoreKit Configuration certificate. Apple Sandbox, TestFlight, and real App Store purchases are never affected.