StoreKit

RSS for tag

Support in-app purchases and interactions with the App Store using StoreKit.

StoreKit Documentation

Posts under StoreKit subtopic

Post

Replies

Boosts

Views

Activity

In-App Purchase Resources
General: Forums topic: StoreKit Forums tag: In-App Purchase App Store Pathway Simple and safe In-App Purchases Auto-renewable subscriptions In-App Purchase documentation Getting started with In-App Purchase using StoreKit views documentation Supporting business model changes by using the app transaction documentation Testing at all stages of development with Xcode and the sandbox documentation App Store Server Notifications documentation App Store Server API documentation Simplifying your implementation by using the App Store Server Library documentation TN3185: Troubleshooting In-App Purchases availability in Xcode technote TN3186: Troubleshooting In-App Purchases availability in the sandbox technote TN3188: Troubleshooting In-App Purchases availability in the App Store technote Understanding StoreKit workflows sample code Implementing a store in your app using the StoreKit API sample code What’s new in StoreKit and In-App Purchase video
0
0
2.3k
Jun ’26
StoreKit 2 returns USA storefront and USD price in TestFlight despite Japanese Apple Account
Hello, I'm developing an iOS app that uses StoreKit 2 for an auto-renewable subscription. I'm experiencing an issue where StoreKit returns the US storefront and USD pricing in TestFlight, even though the device's Apple Account and Sandbox Apple Account are configured for Japan. Environment App: YonsanmaruTimer (430タイマー) App version: 1.2.0 (TestFlight build 4) Bundle ID: com.manyouen.YonsanmaruTimer Product ID: com.manyouen.YonsanmaruTimer.plusassist.monthly StoreKit 2 Xcode Archive configuration: Release App Store Connect configuration The subscription is configured with the following prices: Japan: ¥200/month, with a one-month free trial United States: $0.99/month The app is intended for distribution in Japan. Observed behavior When fetching the subscription product using Product.products(for:), I log the current storefront and product price. The result is: Storefront: USA Price: $0.99 Currency: USDAs a result, the subscription price displayed in the app using product.displayPrice is $0.99 instead of ¥200. What I have already checked The device's Apple Account country/region for Media & Purchases is Japan. TestFlight is installed using my regular Japanese Apple Account. I created a new Sandbox Apple Account with Japan as its country/region and signed in through Settings → Developer → Sandbox Apple Account. The storefront still returns USA after restarting the TestFlight app. The app is archived using the Release build configuration. In an earlier subscription purchase test, Apple's native purchase confirmation sheet displayed ¥200, even though the app's product display price was $0.99. Questions Why would Storefront.current return USA in TestFlight under these conditions? Is this expected behavior in the TestFlight sandbox environment? Could this behavior also occur after the app is released on the App Store? Is there any additional account, device, or App Store Connect configuration I should check? I would like to ensure that the subscription price displayed in my app matches the price shown in Apple's purchase confirmation sheet before submitting the app for review. Any guidance would be greatly appreciated. Thank you.
0
0
77
12h
Sandbox IAP: AuthKit succeeds, then AMSServerErrorDomain -5000 (cancel-purchase-batch)
Every sandbox purchase of our auto-renewable subscriptions cancels right after AuthKit sign-in succeeds. It's blocking our 1.0 release. Filed as FB25469063, no reply yet. Capacitor iOS app, bundle io.xrplive.app, 1.0.0 (TestFlight), products io.xrplive.app.pro.monthly / .yearly, iPhone 17 Pro Max on iOS 27.0.1, StoreKit via @capgo/native-purchases. Console on every attempt: (1) AMSAuthKitUpdateTask: "The AuthKit authentication succeeded." (2) Then: Error Domain=AMSServerErrorDomain Code=-5000 UserInfo={failureType=-5000, m-allowed=false, cancel-purchase-batch=true, customerMessage=Check the account information you entered and try again.} Also AMSErrorDomain Code=100 (Authentication Failed), Code=2 ("Password reuse not available for account"), and a 401 from sandbox.itunes.apple.com/commerce/messages/app/inbox. We already fixed a purchase(confirmIn:) presentation issue. This failure is in sandbox verification after a successful sign-in, which we can't fix from the client. Is -5000 with cancel-purchase-batch a known sandbox account or commerce issue? Is there a sandbox tester or storefront state that fixes it when AuthKit succeeds but verification still fails?
1
0
67
12h
StoreKit says purchase succeeded but didn't, AppStore.sync() throws error Unable to Complete Request
One user of my app reached out reporting an interesting in-app purchase issue. Has anyone encountered this or have an idea what's going on here? Proceed to purchase the non-consumable IAP in the app downloaded from the App Store iOS shows the price sheet as expected Confirm with the side button iOS shows an alert "You've already purchased this. Would you like to get it again for free?" Tap OK iOS shows an alert "You're all set. Your purchase was successful." Tap OK The app's content remains locked Tap Restore Purchases iOS shows an alert to sign (with the same account shown in step 2) Input the password and tap OK iOS shows an alert "Unable to Complete Request" (which is the error.localizedDescription thrown from AppStore.sync())
4
0
456
1d
All auto-renewable subscriptions returning expirationIntent = 5 after resolving an agreement issue (StoreKit 1 and StoreKit 2)
Hello, We are currently seeing errors when validating receipts for every auto-renewable subscription purchased through both StoreKit 1 and StoreKit 2. Details below. Case 1 — StoreKit 1 Calling https://buy.itunes.apple.com/verifyReceipt with the subscription receipt returns: "status": 21006, "expiration_intent": "5" Case 2 — StoreKit 2 Calling https://api.storekit.itunes.apple.com/inApps/v1/subscriptions and reading the most recent transaction (LastTransactionsItem) returns status 3. Within JWSRenewalInfoDecodedPayload: autoRenewStatus = 1, expirationIntent = 5 Timeline We believe renewals stopped processing for essentially all auto-renewing subscribers of our app as of 2026-09-18 09:30 KST (UTC+9). After resolving an agreement/licensing issue on our side, new purchases and some receipt validations recovered as of 2026-09-21 11:49 KST. However, most existing receipts still return expirationIntent = 5 when we query receipt validation or subscription status. Questions Is any action required on our side — a server-side change, a configuration change in App Store Connect, or a further review of our agreements? Now that the agreement issue is resolved, when are the renewals that were left pending during the outage expected to be processed? Any guidance would be appreciated. Thank you.
1
0
305
1d
App Store Server API mass renewal date extension remains incomplete for 11 days
Hello, I submitted a mass subscription renewal date extension request using the App Store Server API on September 9, 2026. The request was accepted successfully. However, when I check the request using getStatusOfSubscriptionRenewalDateExtensions, the status continues to return: complete: false As of September 20, the request has remained incomplete for 11 days. Request details: Extension: 1 day Reason: temporary service interruption Environment: Production The documentation states that a mass renewal date extension may take hours or even days to complete, but I have not been able to find guidance for a request that remains incomplete this long. Only three subscribers were affected by the service interruption, and I have their originalTransactionId values. I am considering using the individual subscription renewal date extension API instead. My questions are: Is it expected for a mass renewal date extension request to remain complete: false for 11 days? Could this mass request still complete at a later date? Is there any way to cancel or determine whether this mass request is stuck? If I extend the three affected subscriptions individually now, is there a risk that the pending mass request could later complete and extend them a second time? I would like to compensate the affected subscribers as soon as possible while avoiding duplicate extensions. Thank you for any guidance.
1
0
340
1d
TestFlight: StoreKit returns CHN/CNY but purchase sheet shows USD
I see different storefronts in StoreKit product queries and Apple’s purchase sheet when testing through TestFlight. Xcode-installed builds work normally. iPhone — iOS 26.6 (23G71), US Media & Purchases account Both StoreKit 1 and StoreKit 2 return CHN/CNY. The app displays CNY 128 for a non-consumable, but Apple’s sandbox purchase sheet shows USD 29.99 for the same product. This reproduces in a standalone 177-line Swift sample using Product.displayPrice directly, with no third-party dependencies, currency conversion, or local .storekit configuration. Reloading products and signing out of the sandbox account did not resolve it. Mac Catalyst — macOS 26.3 (25D125), China purchase account The original TestFlight app returns USA/USD. Purchasing shows “Account Not In This Store” and asks to switch to China, although the purchase account is already set to China. The Mac symptom has not yet been verified in the standalone sample. Reproduction on the affected iPhone: install via TestFlight, load products and log Storefront.current plus the SK1 storefront, open the purchase sheet for the same product, then compare currencies. No completed purchase is needed. Built with Xcode 26.1 (17B55). Has anyone found a workaround for this TestFlight-only mismatch? Should the app handle storefront updates differently, and which additional diagnostics would help distinguish a device/account-session issue from a StoreKit service issue? Feedback: FB24873070. A focused sample and diagnostic evidence are prepared for Apple Developer Technical Support. Reproduction on other devices/accounts is not yet confirmed.
1
0
306
1d
TestFlight sandbox: iTunes account creation not allowed during app sign-in / purchase testing
We are testing version 1.0 Build 29 through TestFlight after a Guideline 2.1(b) rejection: Purchase did not respond on iPad Air 11-inch (M3). Paid Apps Agreement is Active, and subscription price, availability, localization and review screenshot are present. Restores worked, but a fresh purchase is not yet verified. On iPhone 13, Build 29 is installed, Developer Mode is on, and Media & Purchases was signed out. The tester reports signing into Developer > Sandbox Apple Account, then trying to sign into the app. During this sequence an email verification prompt was followed by: "iTunes account creation not allowed. This Apple account cannot be used with iTunes Store at this time. Please try again later." The app uses Sign in with Apple separately from StoreKit. We have not isolated which system authentication flow produced the error. What is the supported sequence for regular iCloud/Sign in with Apple alongside a Sandbox Apple Account for TestFlight purchases? Which diagnostics distinguish account setup failure from app authentication or StoreKit failure? Should we escalate through Feedback Assistant or Developer Support, and which logs should accompany the report? We want to verify a fresh purchase on an 11-inch iPad before resubmission.
1
0
238
1d
Advanced Commerce API support for native macOS apps
Hello, We are considering using the Advanced Commerce API for a native macOS app distributed through the Mac App Store. Our use case is a base auto-renewable subscription with optional subscription add-ons (e.g. Effects and Templates). The Advanced Commerce API eligibility page lists Mac Catalyst, but does not explicitly list native macOS. However, the macOS 15.4 release notes mention support for Advanced Commerce API purchases in StoreKit. Could someone please clarify: Is Advanced Commerce API supported for native macOS App Store apps (not Mac Catalyst), including subscriptions with optional add-ons? Does it support introductory free trials, e.g. a 3-day free trial for the base subscription? Can existing auto-renewable subscription subscribers be migrated to Advanced Commerce API and then purchase optional add-ons as part of the same subscription? Many thanks!
1
0
135
1d
Guidelines 3.1.1 and 3.1.3(c): enterprise-only access on iOS
Hello, I’m looking for guidance on how App Review Guidelines 3.1.1 and 3.1.3(c) apply to an enterprise learning platform with the following access model: Organizations purchase access for their employees through a business-to-business agreement. Employees sign in to the iOS app using accounts provided by their organization. They do not purchase access or pay within the app. Individual users may access the platform separately through the web or Android, but the iOS app is intended only for employees covered by an organization’s agreement. Would this model generally qualify for the enterprise services exception under Guideline 3.1.3(c)? If so, what information or configuration would help App Review verify that iOS access is limited to eligible organization-funded users? I understand that each app is reviewed on its specific implementation. I’d appreciate any guidance or relevant experience from developers who have dealt with a similar setup. Thank you!
0
0
31
2d
Refund requests in the testing environment are never approved, only DECLINE resolves (consumables, non-renewing subscription) – FB25652374
We are testing refunds for consumables and a non-renewing subscription, installed from TestFlight (tester's own Apple Account, storefront VNM, iPhone 15, iOS 27.0.1), with App Store Server Notifications V2 on the sandbox URL. "Testing refund requests" says: "select any refund reason on the refund request sheet, and submit the sheet. The App Store automatically approves the refund request in the testing environment." What we see: DECLINE resolves every time, about 8 minutes after the CONSUMPTION_REQUEST: REFUND_DECLINED arrives whether our server answers refundPreference: DECLINE or the tester types DECLINE under Issue > Other. Nothing else resolves, for up to 43 hours so far (11 requests): no REFUND notification, no revocationDate in Get Transaction Info, empty Get Refund History. This covers: a listed reason with our server answering without refundPreference, answering GRANT_FULL (Send Consumption Information V2, inside the 5-minute window, 202), or not answering; GRANT_PRORATED and GRANT_FULL typed under Issue > Other. Every CONSUMPTION_REQUEST has consumptionRequestReason UNINTENDED_PURCHASE, even when the tester chose Issue > Other. Questions: Should a refund request in the testing environment be approved when the server answers without a preference, answers GRANT_FULL, or does not answer? Is the GRANT_PRORATED keyword still supported? Does refund testing require a Sandbox Apple Account instead of a TestFlight install? Full details, transaction IDs and decoded notification history are in FB25652374. Thread 743381 looks similar.
0
0
26
2d
verifyReceipt returns empty then historical transactions with different receipt metadata during an IAP flow
We are investigating two different production app receipts collected before and after an in-app purchase flow for the same signed-in user of our iOS app. Both receipts were validated against https://buy.itunes.apple.com/verifyReceipt. Both responses returned status = 0 and environment = Production, and both have the same bundle_id and app_item_id. However, their transaction histories and app receipt metadata differ substantially. Observed differences Receipt A (before the purchase flow): receipt.in_app is empty. latest_receipt_info, latest_receipt, and pending_renewal_info are absent. application_version is 31436; original_application_version is 25069. Receipt B (after the purchase flow, validated approximately 78 seconds later): receipt.in_app contains one historical auto-renewable subscription transaction. latest_receipt_info contains two historical subscription transactions; the later one includes promotional_offer_id and offer_code_ref_name. application_version is 31323; original_application_version is 18440. receipt_creation_date is approximately three months earlier than Receipt A's creation date, despite B being collected later in the flow. receipt.original_purchase_date differs by approximately two years. download_id and version_external_identifier also differ. The transactions shown in B predate this purchase flow. These responses alone do not establish that a new purchase completed successfully. What we know and what remains unconfirmed The same application user is involved before and after the flow. We have not yet independently confirmed continuity of the underlying Media & Purchases Apple Account. The supplied server logs do not contain the exact StoreKit callbacks or any receipt refresh/restore calls. We do not currently have a focused standalone reproduction project or confirmed device OS/tool versions for this occurrence. We understand that transaction contents can change as receipts are updated. What we need help understanding is the combination of an empty transaction history changing to historical subscriptions, an older receipt creation date, and different original app purchase metadata during one user's purchase flow. Questions Under what circumstances can this combination of changes occur? Could a cached receipt, receipt refresh/restoration, or a change in App Store account context explain it? Which StoreKit callbacks, receipt acquisition/refresh events, and other diagnostics should we capture to distinguish these possibilities without collecting Apple Account credentials? What is the recommended way to obtain and validate the applicable subscription history when the initial app receipt contains no in-app transactions? If Apple needs the original receipt payloads to investigate this occurrence, which private support or Feedback Assistant channel should we use? Raw receipt data, transaction identifiers, account tokens, download identifiers, and user-specific timestamps have been omitted from this public post. We can provide the original request/response files through an appropriate private Apple support channel. Any guidance from the StoreKit team would be appreciated.
0
0
154
2d
StoreKit 2 returns USD product metadata in TestFlight while the storefront is FRA/EUR
Hello, We would appreciate some guidance regarding an unexpected StoreKit currency result in a TestFlight build. Our iPhone language and region are both set to France. The Sandbox tester is also configured for France, and our subscription products have French availability and pricing configured in App Store Connect. In the TestFlight build we diagnosed, StoreKit reports the current storefront as France with EUR: storefront=FRA/143442/EUR However, all 10 subscription products are returned with USD product metadata: products=10/10 formatCurrencies=USD localeCurrencies=USD error=NONE Example: formatCurrency=USD locale=fr_US_currency_USD localeCurrency=USD display=1,99 $US price=1.99 We first observed this through Flutter's in_app_purchase integration. To determine whether the Flutter plugin was involved, we added a native StoreKit 2 diagnostic to the same TestFlight build. The native result was identical: receipt=sandboxReceipt storefront before=FRA/143442/EUR storefront after=FRA/143442/EUR products=10/10 formatCurrencies=USD localeCurrencies=USD error=NONE The issue appears specific to the TestFlight distribution. When the application is installed directly from the development computer, prices are returned in euros on the same device. We also tested with the regular Media & Purchases account signed out and a French Sandbox tester connected. Once the products loaded successfully, StoreKit still returned USD metadata. In another configuration, the application displayed the USD price while Apple's purchase sheet displayed the price in euros. We are using the price and formatting information returned directly by StoreKit. We do not want to infer the currency from the device region or perform a client-side currency conversion, because StoreKit should remain the authoritative source. Could you please help us understand: Is it expected for Storefront.current to report FRA/EUR while Product.priceFormatStyle.currencyCode, its locale currency, and Product.displayPrice use USD? Could a TestFlight or App Store Connect configuration cause product metadata to use a different currency from the current storefront? Is there another account, availability, pricing or distribution setting that we should verify? Is there a recommended way to refresh or invalidate the product metadata used by a TestFlight installation? We have already filed Feedback Assistant report FB24723329, which is currently under investigation. Thank you very much for any clarification or additional diagnostic steps you can suggest.
11
1
1.6k
2d
Introductory Offer Start Timing
Hi everyone, I set up an auto-renewable subscription introductory offer in App Store Connect with a scheduled start date of September 7 for the Philippines storefront. According to the documentation App Store pricing and availability start times by country or region, scheduled pricing and offer updates are expected to go live based on local regional times. However, the offer did not show up in the Current Introductory Offers in app store connect portal at the documented start time (14:00 Sep 6th UTC). Instead, it stayed in the Upcoming Offers until 7:00 Sep 7th UTC which is 17 hours after the time in the doc. We met a similar situation a few days later when we launch another introductory offer in Thailand. I would appreciate clarification on the following points: What is the underlying reason for the discrepancy between the documented start time behavior and the actual start time observed in production? Can Apple update the App Store pricing and availability start times by country or region reference documentation so that it accurately reflects the practical start time and propagation window for each region? Any insights or shared experiences with offer scheduling in the APAC region would be greatly appreciated.
1
0
416
2d
StoreKit auto-renewable subscription hangs indefinitely in TestFlight — purchase sheet never appears
I’m trying to diagnose a StoreKit issue with an auto-renewable subscription in my iOS app. The subscription is called “Lighthouse Plus” and is $9.99/month. The app is currently being tested through TestFlight. When the user taps the Lighthouse Plus subscription button, the app begins the purchase process/loading state, but the Apple purchase sheet never appears. The UI then remains stuck loading indefinitely. This has continued across multiple TestFlight builds, including our current Build 11. What happens: Install/open the app through TestFlight. Sign into the app. Navigate to Lighthouse Plus. Tap the subscription/purchase button. The app enters a loading state. No Apple purchase confirmation sheet appears. The loading state never resolves. We have also been investigating Restore Purchases and Manage Subscription behavior as part of the same StoreKit implementation. The subscription product has been configured in App Store Connect and associated with the app. We have repeatedly tested new builds while trying to determine whether the failure is in our StoreKit implementation, product configuration, TestFlight sandbox environment, or communication with the App Store. The particularly difficult part is that we are not receiving a visible StoreKit error on the device — the purchase attempt appears to wait indefinitely rather than returning a clear success, cancellation, or failure. I do not currently have access to a Mac for direct Xcode/StoreKit Console debugging, so I am trying to determine the best way to diagnose exactly where this transaction is stopping from a TestFlight device. Questions: What would cause a StoreKit subscription purchase request to remain pending/loading without ever presenting Apple's purchase sheet? Is there a way to retrieve useful StoreKit/TestFlight transaction diagnostics without access to Xcode on a Mac? Are there specific App Store Connect subscription states/configuration issues that can cause this behavior without StoreKit returning an obvious error? What StoreKit transaction/product logging should we add to the app itself so the next TestFlight build can identify exactly where the request is failing? Should the purchase call have an explicit timeout/error path if StoreKit never returns? I can provide the product identifier, relevant StoreKit implementation/code, App Store Connect configuration screenshots, and additional diagnostics if needed. Any guidance on isolating whether this is an App Store configuration issue versus an implementation issue would be greatly appreciated.
1
0
167
2d
StoreKit 2 transaction verification fails during App Review with localized error 「資訊對裝置無效」; how should our app handle this?
We are implementing in-app purchases using StoreKit 2. The issue we need guidance on is how our app should correctly handle a StoreKit 2 transaction that becomes .unverified during Apple App Review. In our local development testing, purchases work correctly. When we test the same IAP products locally, the transaction returned from Product.purchase() is .verified, and the purchase flow completes successfully. However, during Apple App Review, the reviewer appears to encounter a failure where the StoreKit 2 transaction is returned as .unverified on the client side. The original localized error message shown is in Traditional Chinese: 「資訊對裝置無效」 Our English translation of this message is: “The information is not valid for this device.” Because the message is localized, we are not sure what the exact original English StoreKit error string would be. This failure happens in the client app before our backend receipt or server-side validation flow. We are not using verifyReceipt for this step. The failure occurs at the StoreKit 2 VerificationResult level when checking the transaction returned by StoreKit. Our current implementation only accepts .verified transactions. If StoreKit 2 returns .unverified, we treat the transaction as failed and do not unlock the purchased content. We believe this is the recommended secure behavior, but we would like to confirm the correct handling, especially because this issue is appearing during App Review while our local development purchases succeed. Additional context: • Distribution/review context: App Review / IAP review • API: StoreKit 2 • Failure point: VerificationResult returned as .unverified • Localized error message: 「資訊對裝置無效」 • Rough English translation: “The information is not valid for this device.” • Local development testing: purchases return .verified and succeed • The issue occurs before backend validation • Our app currently rejects .unverified transactions and does not unlock content Questions: What are the known causes of StoreKit 2 returning .unverified with the localized error message 「資訊對裝置無效」 during App Review? Is our current behavior correct: only unlock content for .verified transactions and reject .unverified transactions? If App Review receives .unverified, what should the app do from Apple’s recommended perspective? Should we show a retry/error message, ask the reviewer to retry, refresh entitlements, or take another action? Is there any App Review environment, device configuration, Apple ID configuration, or StoreKit account state that can cause this device-related verification error? Since local development purchases succeed but App Review fails, what diagnostics or logs should we collect and provide to identify the root cause? Should we ever bypass StoreKit 2 transaction verification in App Review/TestFlight, or should .unverified always be treated as a failed transaction? We would appreciate guidance on the correct code-level handling so that our app remains secure while also passing App Review reliably. Thank you.
2
0
567
3d
StoreKit introductoryOfferEligibility: safe retry after JWS expiration
How should a server safely retire or renew an unused JWS for Product.PurchaseOption.introductoryOfferEligibility(compactJWS:) after cancellation or interruption? Our application allows a first-purchase discount once per application account across payment platforms. We bind the signed eligibility request to a verified Apple app transaction, product, and purchase attempt, persist the exact JWS, and reuse it for the same attempt. Once a paid purchase is verified, we consume the application's eligibility. We do not automatically issue another nonce after cancellation, a signature error, or an empty transaction history. Apple's JWS documentation describes a one-time nonce and expiration calculated from iat, and says not to include exp: https://developer.apple.com/documentation/storekit/generating-jws-to-sign-app-store-requests I could not find the lifetime or a supported retirement/renewal procedure for the introductory-offer-eligibility audience. Keeping an unusable authorization forever would prevent the customer from trying another checkout; replacing it without retiring the original might leave two redeemable authorizations. What we observed Environment: Xcode 27.2 (27B52), macOS 26.6.2, physical iPhone 16 with iOS 27.0, Apple Sandbox. Verify the Apple-signed AppTransaction and issue one eligibility JWS. Start the purchase using that JWS, then cancel the payment sheet (userCancelled). Terminate and relaunch the app without resetting purchase history or replacing the authorization. Retry the same product and Apple account using the byte-for-byte identical JWS. Complete the Sandbox purchase and verify the Apple-signed transaction on an isolated server. The successful verification happened about 164 seconds after issuance. This is one successful cancellation/retry observation, not a reproduced expiration failure or proof of a general validity/nonce-consumption rule. It also did not verify our intended introductory price. The purchase call uses the persisted value: let result = try await product.purchase(options: [ .introductoryOfferEligibility(compactJWS: existingJWS) ])Supported lifecycle questions What is the validity period derived from iat, including clock-skew allowances and any Sandbox/production differences? Which API or documented error can establish that a previously issued authorization is definitively unusable, rather than merely absent from transaction history? When is the nonce consumed, and what happens after userCancelled, interruption, pending approval, expiration, or an uncertain result? Is invalidOfferSignature specific enough to distinguish expiration from consumption, account mismatch, or a bad signature? Is it supported to keep the same nonce and all bindings, update only iat, and re-sign? If so, is one-time use enforced across every version and for what retention period? If renewal requires a new nonce, how can the prior authorization be invalidated first? Is there another recommended recovery flow that prevents duplicate redemption without indefinitely blocking checkout? DTS directed us to ask this lifecycle question on the forums. A sanitized minimal Xcode project was already supplied privately to DTS; it demonstrates the observed cancel/relaunch/same-JWS retry, not an expiration failure. We would appreciate a supported procedure or documentation reference.
1
0
84
3d
StoreKit Sandbox returns 0 products after TN3186 checks — catalog association issue?
We are testing two auto-renewable subscriptions for a new iOS app. In Apple Sandbox, StoreKit 2 Product.products(for:) always returns an empty array. Legacy SKProductsRequest independently reports both identifiers as invalid. Environment: Physical iPhone, iOS 26.5 Xcode development build with automatic signing Storefront.current = USA (143441) canMakePayments = true No StoreKit Configuration file in the Run scheme Direct native StoreKit 2 diagnostics, without a third-party purchase SDK TN3186 checks completed: Explicit Bundle ID matches the App Store Connect app, installed app, and provisioning profile In-App Purchase is enabled for the App ID Developer membership, Paid Apps Agreement, banking, and tax are active One subscription group with monthly and yearly subscriptions is visible Pricing, localizations, and availability are configured Neither subscription is Rejected or Developer Action Needed The scheme is using real Sandbox data, not local StoreKit testing Results: StoreKit 2 batch query: rawCount = 0 SKProductsRequest: valid = []; both identifiers are invalid StoreKit 2 individual monthly query: 0 StoreKit 2 individual yearly query: 0 No exception; failure occurs during product discovery Related reports: https://developer.apple.com/forums/thread/839313 — TN3186 verified and USA storefront valid, but still 0 products; no replies https://developer.apple.com/forums/thread/841722 — Apple Commerce mentioned Rejected or Developer Action Needed states; ours have neither https://developer.apple.com/forums/thread/820656 — Apple DTS confirmed first subscriptions do not require review before Sandbox testing Apple Developer Support referred us to TN3186, and we verified every applicable item. The individual subscription detail route in App Store Connect also intermittently remains on a loading indicator although the group and both records are visible. Could an App Store Commerce or StoreKit engineer check whether the app-to-IAP catalog association is populated correctly on Apple's side, or advise an official escalation path to have the Sandbox catalog reprocessed? Exact account, app, product, device, email, and support-case identifiers are omitted from this public post and can be supplied privately through Apple Support or Feedback Assistant.
1
0
522
3d
Subscriptions suddenly stopped working in all my apps – StoreKit returns 0 products
Since November 5, in-app subscriptions have suddenly stopped working in all three of my apps on the App Store. Everything worked perfectly before, and no changes were made to the apps. The subscription purchase buttons no longer display prices, only a dash ("–"). Existing apps can still be downloaded normally. I reproduced the problem in Xcode on my own device. StoreKit reports: STOREKIT: Received 0 products STOREKIT: Invalid IDs = ( "TEE_year", "TEE_month", "TEE_week" ) All subscription products are still configured in App Store Connect, and the agreements appear to be active. Interestingly, the problem started around the time I accepted updated Apple agreements and changed my address in my developer account. I don't know whether this is related. Several customers have already independently reported the same problem, so this is not limited to my own device or Apple ID. I strongly suspect an App Store Connect or StoreKit backend issue rather than an app-specific programming error. I've contacted Apple Developer Support (case ID is 30000008123797) but haven't received a solution yet. Has anyone else experienced subscriptions suddenly becoming unavailable across multiple apps? Could this be related to updated agreements or account information?
1
0
138
3d
Supported backend recovery after RESCIND_CONSENT
We are integrating age assurance into two iOS apps with authenticated backend services. We need to handle one specific transition: a parent revokes app consent, then subsequently grants consent again. Our implementation can verify App Store Server Notifications V2 and associate a RESCIND_CONSENT event with its appTransactionId, app and environment. Our backend can then recognize that withdrawal. We do not treat a newly signed AppTransaction, an absent withdrawal record, or acceptance of our Terms as renewed parental permission. We also keep PermissionKit significant-update responses separate from permission to use the app itself. We reviewed the Age Assurance Q&A, Requesting people share their age range with your app, AppTransaction.appTransactionID, and Testing age assurance in sandbox. The documentation explains withdrawal notifications and app-launch prevention. We have not established the supported backend recovery signal after a parent subsequently approves the app again. What supported API, signed field or server notification establishes that later approval for the same appTransactionId? If there is no server-verifiable signal, what supported architecture should a developer use to restore backend access without mistaking a replayed transaction or a significant-update response for renewed app consent? Please identify the supported OS/API versions and a sandbox procedure to exercise withdrawal followed by reapproval, including whether the appTransactionId remains the same. Our current verification uses synthetic withdrawal events and isolated backend tests; we have not yet verified this transition using a genuine parent/child Sandbox Apple Account setup. We are asking about supported API behavior, not reporting an observed Apple service failure or requesting legal advice. References: https://developer.apple.com/support/age-assurance/ https://developer.apple.com/documentation/declaredagerange/requesting-people-share-their-age-range-with-your-app https://developer.apple.com/documentation/storekit/apptransaction/apptransactionid https://developer.apple.com/documentation/storekit/testing-age-assurance-in-sandbox
0
0
38
3d
StoreKit returns USD prices instead of EUR in TestFlight, blocking app release (iOS 27.0.1)
We are experiencing the same issue with two independent native iOS apps on an iPhone running iOS 27.0.1, using TestFlight in France. Our annual subscription displays US$34.90 instead of €39.90, and our non-consumable purchase displays US$5.99 instead of €6.99. Both apps displayed the correct EUR prices during local Xcode testing. In TestFlight, Apple's native purchase sheets still show the correct EUR prices, and both purchases work successfully. We have contacted Apple Developer Support (case 103017935062). As this issue is delaying the time-sensitive release of our educational app, could Apple confirm whether a workaround is available or whether a fix is planned? https://developer.apple.com/forums/thread/845478 Thank you.
3
0
92
3d
In-App Purchase Resources
General: Forums topic: StoreKit Forums tag: In-App Purchase App Store Pathway Simple and safe In-App Purchases Auto-renewable subscriptions In-App Purchase documentation Getting started with In-App Purchase using StoreKit views documentation Supporting business model changes by using the app transaction documentation Testing at all stages of development with Xcode and the sandbox documentation App Store Server Notifications documentation App Store Server API documentation Simplifying your implementation by using the App Store Server Library documentation TN3185: Troubleshooting In-App Purchases availability in Xcode technote TN3186: Troubleshooting In-App Purchases availability in the sandbox technote TN3188: Troubleshooting In-App Purchases availability in the App Store technote Understanding StoreKit workflows sample code Implementing a store in your app using the StoreKit API sample code What’s new in StoreKit and In-App Purchase video
Replies
0
Boosts
0
Views
2.3k
Activity
Jun ’26
StoreKit 2 returns USA storefront and USD price in TestFlight despite Japanese Apple Account
Hello, I'm developing an iOS app that uses StoreKit 2 for an auto-renewable subscription. I'm experiencing an issue where StoreKit returns the US storefront and USD pricing in TestFlight, even though the device's Apple Account and Sandbox Apple Account are configured for Japan. Environment App: YonsanmaruTimer (430タイマー) App version: 1.2.0 (TestFlight build 4) Bundle ID: com.manyouen.YonsanmaruTimer Product ID: com.manyouen.YonsanmaruTimer.plusassist.monthly StoreKit 2 Xcode Archive configuration: Release App Store Connect configuration The subscription is configured with the following prices: Japan: ¥200/month, with a one-month free trial United States: $0.99/month The app is intended for distribution in Japan. Observed behavior When fetching the subscription product using Product.products(for:), I log the current storefront and product price. The result is: Storefront: USA Price: $0.99 Currency: USDAs a result, the subscription price displayed in the app using product.displayPrice is $0.99 instead of ¥200. What I have already checked The device's Apple Account country/region for Media & Purchases is Japan. TestFlight is installed using my regular Japanese Apple Account. I created a new Sandbox Apple Account with Japan as its country/region and signed in through Settings → Developer → Sandbox Apple Account. The storefront still returns USA after restarting the TestFlight app. The app is archived using the Release build configuration. In an earlier subscription purchase test, Apple's native purchase confirmation sheet displayed ¥200, even though the app's product display price was $0.99. Questions Why would Storefront.current return USA in TestFlight under these conditions? Is this expected behavior in the TestFlight sandbox environment? Could this behavior also occur after the app is released on the App Store? Is there any additional account, device, or App Store Connect configuration I should check? I would like to ensure that the subscription price displayed in my app matches the price shown in Apple's purchase confirmation sheet before submitting the app for review. Any guidance would be greatly appreciated. Thank you.
Replies
0
Boosts
0
Views
77
Activity
12h
Sandbox IAP: AuthKit succeeds, then AMSServerErrorDomain -5000 (cancel-purchase-batch)
Every sandbox purchase of our auto-renewable subscriptions cancels right after AuthKit sign-in succeeds. It's blocking our 1.0 release. Filed as FB25469063, no reply yet. Capacitor iOS app, bundle io.xrplive.app, 1.0.0 (TestFlight), products io.xrplive.app.pro.monthly / .yearly, iPhone 17 Pro Max on iOS 27.0.1, StoreKit via @capgo/native-purchases. Console on every attempt: (1) AMSAuthKitUpdateTask: "The AuthKit authentication succeeded." (2) Then: Error Domain=AMSServerErrorDomain Code=-5000 UserInfo={failureType=-5000, m-allowed=false, cancel-purchase-batch=true, customerMessage=Check the account information you entered and try again.} Also AMSErrorDomain Code=100 (Authentication Failed), Code=2 ("Password reuse not available for account"), and a 401 from sandbox.itunes.apple.com/commerce/messages/app/inbox. We already fixed a purchase(confirmIn:) presentation issue. This failure is in sandbox verification after a successful sign-in, which we can't fix from the client. Is -5000 with cancel-purchase-batch a known sandbox account or commerce issue? Is there a sandbox tester or storefront state that fixes it when AuthKit succeeds but verification still fails?
Replies
1
Boosts
0
Views
67
Activity
12h
StoreKit says purchase succeeded but didn't, AppStore.sync() throws error Unable to Complete Request
One user of my app reached out reporting an interesting in-app purchase issue. Has anyone encountered this or have an idea what's going on here? Proceed to purchase the non-consumable IAP in the app downloaded from the App Store iOS shows the price sheet as expected Confirm with the side button iOS shows an alert "You've already purchased this. Would you like to get it again for free?" Tap OK iOS shows an alert "You're all set. Your purchase was successful." Tap OK The app's content remains locked Tap Restore Purchases iOS shows an alert to sign (with the same account shown in step 2) Input the password and tap OK iOS shows an alert "Unable to Complete Request" (which is the error.localizedDescription thrown from AppStore.sync())
Replies
4
Boosts
0
Views
456
Activity
1d
All auto-renewable subscriptions returning expirationIntent = 5 after resolving an agreement issue (StoreKit 1 and StoreKit 2)
Hello, We are currently seeing errors when validating receipts for every auto-renewable subscription purchased through both StoreKit 1 and StoreKit 2. Details below. Case 1 — StoreKit 1 Calling https://buy.itunes.apple.com/verifyReceipt with the subscription receipt returns: "status": 21006, "expiration_intent": "5" Case 2 — StoreKit 2 Calling https://api.storekit.itunes.apple.com/inApps/v1/subscriptions and reading the most recent transaction (LastTransactionsItem) returns status 3. Within JWSRenewalInfoDecodedPayload: autoRenewStatus = 1, expirationIntent = 5 Timeline We believe renewals stopped processing for essentially all auto-renewing subscribers of our app as of 2026-09-18 09:30 KST (UTC+9). After resolving an agreement/licensing issue on our side, new purchases and some receipt validations recovered as of 2026-09-21 11:49 KST. However, most existing receipts still return expirationIntent = 5 when we query receipt validation or subscription status. Questions Is any action required on our side — a server-side change, a configuration change in App Store Connect, or a further review of our agreements? Now that the agreement issue is resolved, when are the renewals that were left pending during the outage expected to be processed? Any guidance would be appreciated. Thank you.
Replies
1
Boosts
0
Views
305
Activity
1d
App Store Server API mass renewal date extension remains incomplete for 11 days
Hello, I submitted a mass subscription renewal date extension request using the App Store Server API on September 9, 2026. The request was accepted successfully. However, when I check the request using getStatusOfSubscriptionRenewalDateExtensions, the status continues to return: complete: false As of September 20, the request has remained incomplete for 11 days. Request details: Extension: 1 day Reason: temporary service interruption Environment: Production The documentation states that a mass renewal date extension may take hours or even days to complete, but I have not been able to find guidance for a request that remains incomplete this long. Only three subscribers were affected by the service interruption, and I have their originalTransactionId values. I am considering using the individual subscription renewal date extension API instead. My questions are: Is it expected for a mass renewal date extension request to remain complete: false for 11 days? Could this mass request still complete at a later date? Is there any way to cancel or determine whether this mass request is stuck? If I extend the three affected subscriptions individually now, is there a risk that the pending mass request could later complete and extend them a second time? I would like to compensate the affected subscribers as soon as possible while avoiding duplicate extensions. Thank you for any guidance.
Replies
1
Boosts
0
Views
340
Activity
1d
TestFlight: StoreKit returns CHN/CNY but purchase sheet shows USD
I see different storefronts in StoreKit product queries and Apple’s purchase sheet when testing through TestFlight. Xcode-installed builds work normally. iPhone — iOS 26.6 (23G71), US Media & Purchases account Both StoreKit 1 and StoreKit 2 return CHN/CNY. The app displays CNY 128 for a non-consumable, but Apple’s sandbox purchase sheet shows USD 29.99 for the same product. This reproduces in a standalone 177-line Swift sample using Product.displayPrice directly, with no third-party dependencies, currency conversion, or local .storekit configuration. Reloading products and signing out of the sandbox account did not resolve it. Mac Catalyst — macOS 26.3 (25D125), China purchase account The original TestFlight app returns USA/USD. Purchasing shows “Account Not In This Store” and asks to switch to China, although the purchase account is already set to China. The Mac symptom has not yet been verified in the standalone sample. Reproduction on the affected iPhone: install via TestFlight, load products and log Storefront.current plus the SK1 storefront, open the purchase sheet for the same product, then compare currencies. No completed purchase is needed. Built with Xcode 26.1 (17B55). Has anyone found a workaround for this TestFlight-only mismatch? Should the app handle storefront updates differently, and which additional diagnostics would help distinguish a device/account-session issue from a StoreKit service issue? Feedback: FB24873070. A focused sample and diagnostic evidence are prepared for Apple Developer Technical Support. Reproduction on other devices/accounts is not yet confirmed.
Replies
1
Boosts
0
Views
306
Activity
1d
TestFlight sandbox: iTunes account creation not allowed during app sign-in / purchase testing
We are testing version 1.0 Build 29 through TestFlight after a Guideline 2.1(b) rejection: Purchase did not respond on iPad Air 11-inch (M3). Paid Apps Agreement is Active, and subscription price, availability, localization and review screenshot are present. Restores worked, but a fresh purchase is not yet verified. On iPhone 13, Build 29 is installed, Developer Mode is on, and Media & Purchases was signed out. The tester reports signing into Developer > Sandbox Apple Account, then trying to sign into the app. During this sequence an email verification prompt was followed by: "iTunes account creation not allowed. This Apple account cannot be used with iTunes Store at this time. Please try again later." The app uses Sign in with Apple separately from StoreKit. We have not isolated which system authentication flow produced the error. What is the supported sequence for regular iCloud/Sign in with Apple alongside a Sandbox Apple Account for TestFlight purchases? Which diagnostics distinguish account setup failure from app authentication or StoreKit failure? Should we escalate through Feedback Assistant or Developer Support, and which logs should accompany the report? We want to verify a fresh purchase on an 11-inch iPad before resubmission.
Replies
1
Boosts
0
Views
238
Activity
1d
Advanced Commerce API support for native macOS apps
Hello, We are considering using the Advanced Commerce API for a native macOS app distributed through the Mac App Store. Our use case is a base auto-renewable subscription with optional subscription add-ons (e.g. Effects and Templates). The Advanced Commerce API eligibility page lists Mac Catalyst, but does not explicitly list native macOS. However, the macOS 15.4 release notes mention support for Advanced Commerce API purchases in StoreKit. Could someone please clarify: Is Advanced Commerce API supported for native macOS App Store apps (not Mac Catalyst), including subscriptions with optional add-ons? Does it support introductory free trials, e.g. a 3-day free trial for the base subscription? Can existing auto-renewable subscription subscribers be migrated to Advanced Commerce API and then purchase optional add-ons as part of the same subscription? Many thanks!
Replies
1
Boosts
0
Views
135
Activity
1d
Guidelines 3.1.1 and 3.1.3(c): enterprise-only access on iOS
Hello, I’m looking for guidance on how App Review Guidelines 3.1.1 and 3.1.3(c) apply to an enterprise learning platform with the following access model: Organizations purchase access for their employees through a business-to-business agreement. Employees sign in to the iOS app using accounts provided by their organization. They do not purchase access or pay within the app. Individual users may access the platform separately through the web or Android, but the iOS app is intended only for employees covered by an organization’s agreement. Would this model generally qualify for the enterprise services exception under Guideline 3.1.3(c)? If so, what information or configuration would help App Review verify that iOS access is limited to eligible organization-funded users? I understand that each app is reviewed on its specific implementation. I’d appreciate any guidance or relevant experience from developers who have dealt with a similar setup. Thank you!
Replies
0
Boosts
0
Views
31
Activity
2d
Refund requests in the testing environment are never approved, only DECLINE resolves (consumables, non-renewing subscription) – FB25652374
We are testing refunds for consumables and a non-renewing subscription, installed from TestFlight (tester's own Apple Account, storefront VNM, iPhone 15, iOS 27.0.1), with App Store Server Notifications V2 on the sandbox URL. "Testing refund requests" says: "select any refund reason on the refund request sheet, and submit the sheet. The App Store automatically approves the refund request in the testing environment." What we see: DECLINE resolves every time, about 8 minutes after the CONSUMPTION_REQUEST: REFUND_DECLINED arrives whether our server answers refundPreference: DECLINE or the tester types DECLINE under Issue > Other. Nothing else resolves, for up to 43 hours so far (11 requests): no REFUND notification, no revocationDate in Get Transaction Info, empty Get Refund History. This covers: a listed reason with our server answering without refundPreference, answering GRANT_FULL (Send Consumption Information V2, inside the 5-minute window, 202), or not answering; GRANT_PRORATED and GRANT_FULL typed under Issue > Other. Every CONSUMPTION_REQUEST has consumptionRequestReason UNINTENDED_PURCHASE, even when the tester chose Issue > Other. Questions: Should a refund request in the testing environment be approved when the server answers without a preference, answers GRANT_FULL, or does not answer? Is the GRANT_PRORATED keyword still supported? Does refund testing require a Sandbox Apple Account instead of a TestFlight install? Full details, transaction IDs and decoded notification history are in FB25652374. Thread 743381 looks similar.
Replies
0
Boosts
0
Views
26
Activity
2d
verifyReceipt returns empty then historical transactions with different receipt metadata during an IAP flow
We are investigating two different production app receipts collected before and after an in-app purchase flow for the same signed-in user of our iOS app. Both receipts were validated against https://buy.itunes.apple.com/verifyReceipt. Both responses returned status = 0 and environment = Production, and both have the same bundle_id and app_item_id. However, their transaction histories and app receipt metadata differ substantially. Observed differences Receipt A (before the purchase flow): receipt.in_app is empty. latest_receipt_info, latest_receipt, and pending_renewal_info are absent. application_version is 31436; original_application_version is 25069. Receipt B (after the purchase flow, validated approximately 78 seconds later): receipt.in_app contains one historical auto-renewable subscription transaction. latest_receipt_info contains two historical subscription transactions; the later one includes promotional_offer_id and offer_code_ref_name. application_version is 31323; original_application_version is 18440. receipt_creation_date is approximately three months earlier than Receipt A's creation date, despite B being collected later in the flow. receipt.original_purchase_date differs by approximately two years. download_id and version_external_identifier also differ. The transactions shown in B predate this purchase flow. These responses alone do not establish that a new purchase completed successfully. What we know and what remains unconfirmed The same application user is involved before and after the flow. We have not yet independently confirmed continuity of the underlying Media & Purchases Apple Account. The supplied server logs do not contain the exact StoreKit callbacks or any receipt refresh/restore calls. We do not currently have a focused standalone reproduction project or confirmed device OS/tool versions for this occurrence. We understand that transaction contents can change as receipts are updated. What we need help understanding is the combination of an empty transaction history changing to historical subscriptions, an older receipt creation date, and different original app purchase metadata during one user's purchase flow. Questions Under what circumstances can this combination of changes occur? Could a cached receipt, receipt refresh/restoration, or a change in App Store account context explain it? Which StoreKit callbacks, receipt acquisition/refresh events, and other diagnostics should we capture to distinguish these possibilities without collecting Apple Account credentials? What is the recommended way to obtain and validate the applicable subscription history when the initial app receipt contains no in-app transactions? If Apple needs the original receipt payloads to investigate this occurrence, which private support or Feedback Assistant channel should we use? Raw receipt data, transaction identifiers, account tokens, download identifiers, and user-specific timestamps have been omitted from this public post. We can provide the original request/response files through an appropriate private Apple support channel. Any guidance from the StoreKit team would be appreciated.
Replies
0
Boosts
0
Views
154
Activity
2d
StoreKit 2 returns USD product metadata in TestFlight while the storefront is FRA/EUR
Hello, We would appreciate some guidance regarding an unexpected StoreKit currency result in a TestFlight build. Our iPhone language and region are both set to France. The Sandbox tester is also configured for France, and our subscription products have French availability and pricing configured in App Store Connect. In the TestFlight build we diagnosed, StoreKit reports the current storefront as France with EUR: storefront=FRA/143442/EUR However, all 10 subscription products are returned with USD product metadata: products=10/10 formatCurrencies=USD localeCurrencies=USD error=NONE Example: formatCurrency=USD locale=fr_US_currency_USD localeCurrency=USD display=1,99 $US price=1.99 We first observed this through Flutter's in_app_purchase integration. To determine whether the Flutter plugin was involved, we added a native StoreKit 2 diagnostic to the same TestFlight build. The native result was identical: receipt=sandboxReceipt storefront before=FRA/143442/EUR storefront after=FRA/143442/EUR products=10/10 formatCurrencies=USD localeCurrencies=USD error=NONE The issue appears specific to the TestFlight distribution. When the application is installed directly from the development computer, prices are returned in euros on the same device. We also tested with the regular Media & Purchases account signed out and a French Sandbox tester connected. Once the products loaded successfully, StoreKit still returned USD metadata. In another configuration, the application displayed the USD price while Apple's purchase sheet displayed the price in euros. We are using the price and formatting information returned directly by StoreKit. We do not want to infer the currency from the device region or perform a client-side currency conversion, because StoreKit should remain the authoritative source. Could you please help us understand: Is it expected for Storefront.current to report FRA/EUR while Product.priceFormatStyle.currencyCode, its locale currency, and Product.displayPrice use USD? Could a TestFlight or App Store Connect configuration cause product metadata to use a different currency from the current storefront? Is there another account, availability, pricing or distribution setting that we should verify? Is there a recommended way to refresh or invalidate the product metadata used by a TestFlight installation? We have already filed Feedback Assistant report FB24723329, which is currently under investigation. Thank you very much for any clarification or additional diagnostic steps you can suggest.
Replies
11
Boosts
1
Views
1.6k
Activity
2d
Introductory Offer Start Timing
Hi everyone, I set up an auto-renewable subscription introductory offer in App Store Connect with a scheduled start date of September 7 for the Philippines storefront. According to the documentation App Store pricing and availability start times by country or region, scheduled pricing and offer updates are expected to go live based on local regional times. However, the offer did not show up in the Current Introductory Offers in app store connect portal at the documented start time (14:00 Sep 6th UTC). Instead, it stayed in the Upcoming Offers until 7:00 Sep 7th UTC which is 17 hours after the time in the doc. We met a similar situation a few days later when we launch another introductory offer in Thailand. I would appreciate clarification on the following points: What is the underlying reason for the discrepancy between the documented start time behavior and the actual start time observed in production? Can Apple update the App Store pricing and availability start times by country or region reference documentation so that it accurately reflects the practical start time and propagation window for each region? Any insights or shared experiences with offer scheduling in the APAC region would be greatly appreciated.
Replies
1
Boosts
0
Views
416
Activity
2d
StoreKit auto-renewable subscription hangs indefinitely in TestFlight — purchase sheet never appears
I’m trying to diagnose a StoreKit issue with an auto-renewable subscription in my iOS app. The subscription is called “Lighthouse Plus” and is $9.99/month. The app is currently being tested through TestFlight. When the user taps the Lighthouse Plus subscription button, the app begins the purchase process/loading state, but the Apple purchase sheet never appears. The UI then remains stuck loading indefinitely. This has continued across multiple TestFlight builds, including our current Build 11. What happens: Install/open the app through TestFlight. Sign into the app. Navigate to Lighthouse Plus. Tap the subscription/purchase button. The app enters a loading state. No Apple purchase confirmation sheet appears. The loading state never resolves. We have also been investigating Restore Purchases and Manage Subscription behavior as part of the same StoreKit implementation. The subscription product has been configured in App Store Connect and associated with the app. We have repeatedly tested new builds while trying to determine whether the failure is in our StoreKit implementation, product configuration, TestFlight sandbox environment, or communication with the App Store. The particularly difficult part is that we are not receiving a visible StoreKit error on the device — the purchase attempt appears to wait indefinitely rather than returning a clear success, cancellation, or failure. I do not currently have access to a Mac for direct Xcode/StoreKit Console debugging, so I am trying to determine the best way to diagnose exactly where this transaction is stopping from a TestFlight device. Questions: What would cause a StoreKit subscription purchase request to remain pending/loading without ever presenting Apple's purchase sheet? Is there a way to retrieve useful StoreKit/TestFlight transaction diagnostics without access to Xcode on a Mac? Are there specific App Store Connect subscription states/configuration issues that can cause this behavior without StoreKit returning an obvious error? What StoreKit transaction/product logging should we add to the app itself so the next TestFlight build can identify exactly where the request is failing? Should the purchase call have an explicit timeout/error path if StoreKit never returns? I can provide the product identifier, relevant StoreKit implementation/code, App Store Connect configuration screenshots, and additional diagnostics if needed. Any guidance on isolating whether this is an App Store configuration issue versus an implementation issue would be greatly appreciated.
Replies
1
Boosts
0
Views
167
Activity
2d
StoreKit 2 transaction verification fails during App Review with localized error 「資訊對裝置無效」; how should our app handle this?
We are implementing in-app purchases using StoreKit 2. The issue we need guidance on is how our app should correctly handle a StoreKit 2 transaction that becomes .unverified during Apple App Review. In our local development testing, purchases work correctly. When we test the same IAP products locally, the transaction returned from Product.purchase() is .verified, and the purchase flow completes successfully. However, during Apple App Review, the reviewer appears to encounter a failure where the StoreKit 2 transaction is returned as .unverified on the client side. The original localized error message shown is in Traditional Chinese: 「資訊對裝置無效」 Our English translation of this message is: “The information is not valid for this device.” Because the message is localized, we are not sure what the exact original English StoreKit error string would be. This failure happens in the client app before our backend receipt or server-side validation flow. We are not using verifyReceipt for this step. The failure occurs at the StoreKit 2 VerificationResult level when checking the transaction returned by StoreKit. Our current implementation only accepts .verified transactions. If StoreKit 2 returns .unverified, we treat the transaction as failed and do not unlock the purchased content. We believe this is the recommended secure behavior, but we would like to confirm the correct handling, especially because this issue is appearing during App Review while our local development purchases succeed. Additional context: • Distribution/review context: App Review / IAP review • API: StoreKit 2 • Failure point: VerificationResult returned as .unverified • Localized error message: 「資訊對裝置無效」 • Rough English translation: “The information is not valid for this device.” • Local development testing: purchases return .verified and succeed • The issue occurs before backend validation • Our app currently rejects .unverified transactions and does not unlock content Questions: What are the known causes of StoreKit 2 returning .unverified with the localized error message 「資訊對裝置無效」 during App Review? Is our current behavior correct: only unlock content for .verified transactions and reject .unverified transactions? If App Review receives .unverified, what should the app do from Apple’s recommended perspective? Should we show a retry/error message, ask the reviewer to retry, refresh entitlements, or take another action? Is there any App Review environment, device configuration, Apple ID configuration, or StoreKit account state that can cause this device-related verification error? Since local development purchases succeed but App Review fails, what diagnostics or logs should we collect and provide to identify the root cause? Should we ever bypass StoreKit 2 transaction verification in App Review/TestFlight, or should .unverified always be treated as a failed transaction? We would appreciate guidance on the correct code-level handling so that our app remains secure while also passing App Review reliably. Thank you.
Replies
2
Boosts
0
Views
567
Activity
3d
StoreKit introductoryOfferEligibility: safe retry after JWS expiration
How should a server safely retire or renew an unused JWS for Product.PurchaseOption.introductoryOfferEligibility(compactJWS:) after cancellation or interruption? Our application allows a first-purchase discount once per application account across payment platforms. We bind the signed eligibility request to a verified Apple app transaction, product, and purchase attempt, persist the exact JWS, and reuse it for the same attempt. Once a paid purchase is verified, we consume the application's eligibility. We do not automatically issue another nonce after cancellation, a signature error, or an empty transaction history. Apple's JWS documentation describes a one-time nonce and expiration calculated from iat, and says not to include exp: https://developer.apple.com/documentation/storekit/generating-jws-to-sign-app-store-requests I could not find the lifetime or a supported retirement/renewal procedure for the introductory-offer-eligibility audience. Keeping an unusable authorization forever would prevent the customer from trying another checkout; replacing it without retiring the original might leave two redeemable authorizations. What we observed Environment: Xcode 27.2 (27B52), macOS 26.6.2, physical iPhone 16 with iOS 27.0, Apple Sandbox. Verify the Apple-signed AppTransaction and issue one eligibility JWS. Start the purchase using that JWS, then cancel the payment sheet (userCancelled). Terminate and relaunch the app without resetting purchase history or replacing the authorization. Retry the same product and Apple account using the byte-for-byte identical JWS. Complete the Sandbox purchase and verify the Apple-signed transaction on an isolated server. The successful verification happened about 164 seconds after issuance. This is one successful cancellation/retry observation, not a reproduced expiration failure or proof of a general validity/nonce-consumption rule. It also did not verify our intended introductory price. The purchase call uses the persisted value: let result = try await product.purchase(options: [ .introductoryOfferEligibility(compactJWS: existingJWS) ])Supported lifecycle questions What is the validity period derived from iat, including clock-skew allowances and any Sandbox/production differences? Which API or documented error can establish that a previously issued authorization is definitively unusable, rather than merely absent from transaction history? When is the nonce consumed, and what happens after userCancelled, interruption, pending approval, expiration, or an uncertain result? Is invalidOfferSignature specific enough to distinguish expiration from consumption, account mismatch, or a bad signature? Is it supported to keep the same nonce and all bindings, update only iat, and re-sign? If so, is one-time use enforced across every version and for what retention period? If renewal requires a new nonce, how can the prior authorization be invalidated first? Is there another recommended recovery flow that prevents duplicate redemption without indefinitely blocking checkout? DTS directed us to ask this lifecycle question on the forums. A sanitized minimal Xcode project was already supplied privately to DTS; it demonstrates the observed cancel/relaunch/same-JWS retry, not an expiration failure. We would appreciate a supported procedure or documentation reference.
Replies
1
Boosts
0
Views
84
Activity
3d
StoreKit Sandbox returns 0 products after TN3186 checks — catalog association issue?
We are testing two auto-renewable subscriptions for a new iOS app. In Apple Sandbox, StoreKit 2 Product.products(for:) always returns an empty array. Legacy SKProductsRequest independently reports both identifiers as invalid. Environment: Physical iPhone, iOS 26.5 Xcode development build with automatic signing Storefront.current = USA (143441) canMakePayments = true No StoreKit Configuration file in the Run scheme Direct native StoreKit 2 diagnostics, without a third-party purchase SDK TN3186 checks completed: Explicit Bundle ID matches the App Store Connect app, installed app, and provisioning profile In-App Purchase is enabled for the App ID Developer membership, Paid Apps Agreement, banking, and tax are active One subscription group with monthly and yearly subscriptions is visible Pricing, localizations, and availability are configured Neither subscription is Rejected or Developer Action Needed The scheme is using real Sandbox data, not local StoreKit testing Results: StoreKit 2 batch query: rawCount = 0 SKProductsRequest: valid = []; both identifiers are invalid StoreKit 2 individual monthly query: 0 StoreKit 2 individual yearly query: 0 No exception; failure occurs during product discovery Related reports: https://developer.apple.com/forums/thread/839313 — TN3186 verified and USA storefront valid, but still 0 products; no replies https://developer.apple.com/forums/thread/841722 — Apple Commerce mentioned Rejected or Developer Action Needed states; ours have neither https://developer.apple.com/forums/thread/820656 — Apple DTS confirmed first subscriptions do not require review before Sandbox testing Apple Developer Support referred us to TN3186, and we verified every applicable item. The individual subscription detail route in App Store Connect also intermittently remains on a loading indicator although the group and both records are visible. Could an App Store Commerce or StoreKit engineer check whether the app-to-IAP catalog association is populated correctly on Apple's side, or advise an official escalation path to have the Sandbox catalog reprocessed? Exact account, app, product, device, email, and support-case identifiers are omitted from this public post and can be supplied privately through Apple Support or Feedback Assistant.
Replies
1
Boosts
0
Views
522
Activity
3d
Subscriptions suddenly stopped working in all my apps – StoreKit returns 0 products
Since November 5, in-app subscriptions have suddenly stopped working in all three of my apps on the App Store. Everything worked perfectly before, and no changes were made to the apps. The subscription purchase buttons no longer display prices, only a dash ("–"). Existing apps can still be downloaded normally. I reproduced the problem in Xcode on my own device. StoreKit reports: STOREKIT: Received 0 products STOREKIT: Invalid IDs = ( "TEE_year", "TEE_month", "TEE_week" ) All subscription products are still configured in App Store Connect, and the agreements appear to be active. Interestingly, the problem started around the time I accepted updated Apple agreements and changed my address in my developer account. I don't know whether this is related. Several customers have already independently reported the same problem, so this is not limited to my own device or Apple ID. I strongly suspect an App Store Connect or StoreKit backend issue rather than an app-specific programming error. I've contacted Apple Developer Support (case ID is 30000008123797) but haven't received a solution yet. Has anyone else experienced subscriptions suddenly becoming unavailable across multiple apps? Could this be related to updated agreements or account information?
Replies
1
Boosts
0
Views
138
Activity
3d
Supported backend recovery after RESCIND_CONSENT
We are integrating age assurance into two iOS apps with authenticated backend services. We need to handle one specific transition: a parent revokes app consent, then subsequently grants consent again. Our implementation can verify App Store Server Notifications V2 and associate a RESCIND_CONSENT event with its appTransactionId, app and environment. Our backend can then recognize that withdrawal. We do not treat a newly signed AppTransaction, an absent withdrawal record, or acceptance of our Terms as renewed parental permission. We also keep PermissionKit significant-update responses separate from permission to use the app itself. We reviewed the Age Assurance Q&A, Requesting people share their age range with your app, AppTransaction.appTransactionID, and Testing age assurance in sandbox. The documentation explains withdrawal notifications and app-launch prevention. We have not established the supported backend recovery signal after a parent subsequently approves the app again. What supported API, signed field or server notification establishes that later approval for the same appTransactionId? If there is no server-verifiable signal, what supported architecture should a developer use to restore backend access without mistaking a replayed transaction or a significant-update response for renewed app consent? Please identify the supported OS/API versions and a sandbox procedure to exercise withdrawal followed by reapproval, including whether the appTransactionId remains the same. Our current verification uses synthetic withdrawal events and isolated backend tests; we have not yet verified this transition using a genuine parent/child Sandbox Apple Account setup. We are asking about supported API behavior, not reporting an observed Apple service failure or requesting legal advice. References: https://developer.apple.com/support/age-assurance/ https://developer.apple.com/documentation/declaredagerange/requesting-people-share-their-age-range-with-your-app https://developer.apple.com/documentation/storekit/apptransaction/apptransactionid https://developer.apple.com/documentation/storekit/testing-age-assurance-in-sandbox
Replies
0
Boosts
0
Views
38
Activity
3d
StoreKit returns USD prices instead of EUR in TestFlight, blocking app release (iOS 27.0.1)
We are experiencing the same issue with two independent native iOS apps on an iPhone running iOS 27.0.1, using TestFlight in France. Our annual subscription displays US$34.90 instead of €39.90, and our non-consumable purchase displays US$5.99 instead of €6.99. Both apps displayed the correct EUR prices during local Xcode testing. In TestFlight, Apple's native purchase sheets still show the correct EUR prices, and both purchases work successfully. We have contacted Apple Developer Support (case 103017935062). As this issue is delaying the time-sensitive release of our educational app, could Apple confirm whether a workaround is available or whether a fix is planned? https://developer.apple.com/forums/thread/845478 Thank you.
Replies
3
Boosts
0
Views
92
Activity
3d