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

Sandbox: CONSUMPTION_REQUEST received but REFUND / REFUND_DECLINED never sent (auto-renewable subscription)
We are testing refunds for an auto-renewable subscription in the Sandbox environment using Transaction.beginRefundRequest(in:), following "Testing refund requests". Our server receives CONSUMPTION_REQUEST, but a REFUND or REFUND_DECLINED notification never follows. What we did (4 transactions, Nov 16, 2026) Purchased a monthly subscription with sandbox renewal rates of 1 hour, 30 minutes and 5 minutes, then turned off auto-renew. Submitted the refund sheet: one request with a standard reason; others with Issue = Other and text GRANT_PRORATED. We also used a second sandbox account. For one transaction, we called Send Consumption Information v2 within 5 minutes of the CONSUMPTION_REQUEST. The body was customerConsented: true, deliveryStatus: DELIVERED, sampleContentProvided: false, refundPreference: GRANT_PRORATED. The API returned 202 Accepted. What we see CONSUMPTION_REQUEST arrives 1–2 minutes after the refund sheet is submitted. Our server returns HTTP 200, and Get Notification History shows the send attempt as SUCCESS. No REFUND or REFUND_DECLINED arrived. Get Refund History v2 is empty, Get Transaction Info shows no revocationDate, and Get Notification History has no refund notification. All other sandbox notifications are delivered within a second: SUBSCRIBED, DID_CHANGE_RENEWAL_STATUS, EXPIRED. In production, REFUND, REFUND_DECLINED and REFUND_REVERSED are delivered normally for the same app. Sandbox transaction IDs 2000001266241009, 2000001266277405, 2000001266288964, 2000001266312137 Feedback: FB25595203 Questions Is there a known issue with Sandbox not deciding refund requests for auto-renewable subscriptions after CONSUMPTION_REQUEST? Is there a supported way to receive a real REFUND notification in Sandbox for end-to-end server testing? Thank you.
0
0
72
4d
SKTestSession.setSimulatedError does not work - Products load successfully despite error configuration
Description I'm attempting to test error handling in my StoreKit implementation using SKTestSession.setSimulatedError(), but it doesn't trigger any errors. All StoreKit APIs (.loadProducts, .purchase, .appTransaction) succeed despite error simulation being configured before API calls. According to Apple's documentation, setSimulatedError(_:forAPI:) should cause the specified API to throw an error, but this doesn't happen in my testing environment. Background / Known issue I found a previous forum discussion: "SKTestSession.setSimulatedError() not working for .loadProducts API in iOS 26.2" which mentioned this was a bug in iOS 26.2 and was supposedly fixed in iOS 26.3. However, I'm experiencing the same issue in my current environment (Xcode 26.6 / iOS 26.5), which suggests either: The bug has regressed, or There's a different underlying issue, or I'm missing something in my implementation I wanted to report this to confirm whether this is still a known issue or if additional steps are needed. Environment Xcode: 26.6 Test Environment: iOS Simulator - iPhone 17 Pro(26.5) Testing Framework: XCTest StoreKitTest Framework: Included in Xcode Code Unit test code import XCTest import StoreKit import StoreKitTest final class StoreKitErrorTests: XCTestCase { func test_LoadProducts_SetSimulatedError() async throws { // Arrange let session = try SKTestSession(configurationFileNamed: "storekit") session.clearTransactions() session.disableDialogs = true // Set simulated error for loadProducts API try await session.setSimulatedError( .generic(.unknown), forAPI: .loadProducts ) // Act - Attempt to load products do { let products = try await Product.products(for: ["com.example.app.testproduct"]) // This line executes - products were loaded successfully print("[TEST] FAIL: Loaded \(products.count) products") XCTFail("setSimulatedError did not work - products loaded successfully") } catch { // This should execute, but it doesn't print("[TEST] PASS: Error was thrown") } } }.storekit file Note: Showing only the product definition. File also contains settings and version info. { "products" : [ { "displayPrice" : "1.23", "familyShareable" : false, "internalID" : "5AE6F98A", "localizations" : [ { "description" : "Test app", "displayName" : "LsStorekit", "locale" : "en_US" } ], "productID" : "com.example.app.testproduct", "referenceName" : "LsStorekit", "type" : "NonConsumable" } ] }Expected Behavior The Product.products(for:) call should throw an error because setSimulatedError(.generic(.unknown), forAPI: .loadProducts) was called before the API invocation. The test should: Configure the simulated error Attempt to load products Catch an error in the catch block Test passes with: "[TEST] PASS: Error was thrown" Actual Behavior Products are loaded successfully despite the error simulation: • The do block completes without throwing • 1 product is returned from Product.products(for:) • XCTFail() is called, indicating the error simulation didn't work • Test fails with: "[TEST] FAIL: Loaded 1 products" Console Output [TEST] FAIL: Loaded 1 products Additional Testing I've tested setSimulatedError with multiple APIs, and all show the same behavior: APIError configurationResult.loadProducts.generic(.unknown)No error thrown.purchase.generic(.unknown)No error thrown.appTransaction.generic(.unknown)No error thrown.appStoreSync.generic(.unknown)No error thrownWhat I've Already Tried • Calling setSimulatedError before app launch (in UI tests) • Calling setSimulatedError after app launch but before API calls • Using different error types (.generic(.unknown), .generic(.networkError(...))) • Testing in both Unit Tests and UI Tests • Using different APIs (.loadProducts, .purchase, .appTransaction) • Clearing transactions and resetting session state • Verifying the .storekit file is correctly loaded (products load successfully) • Running the app first (⌘R) to ensure StoreKit configuration is registered with the StoreKit daemon - This was necessary to fix an initial issue where products weren't loading at all Questions Is this a known limitation of SKTestSession.setSimulatedError()? Are there additional steps required to make error simulation work? Is there an alternative approach to test StoreKit error handling? Does this work in specific Xcode/iOS SDK versions only? Any guidance would be greatly appreciated. I need to test error handling in my StoreKit implementation, but cannot find a way to simulate errors reliably.
0
0
39
5d
Production AppTransaction.shared throws StoreKitError.unknown when reading original app acquisition date
I'm the developer of Freezon, and I ran into this on my own iPhone with the App Store version of the app. I use the verified AppTransaction.originalPurchaseDate to give Pro access to people who first downloaded the app before a published cutoff. This includes free downloads; I need the original acquisition date of the app itself, not an in-app purchase date. On this device, AppTransaction.shared repeatedly threw StoreKitError.unknown before returning a VerificationResult: let result = try await AppTransaction.shared switch result { case let .verified(transaction): let firstAcquisitionDate = transaction.originalPurchaseDate // Check early-adopter eligibility. case let .unverified(_, error): throw error }The error occurs at shared, before the switch. The App Store on this iPhone shows my Apple Account as signed in. However, when I purchase or restore, I keep getting asked for my password, and sometimes for both my Apple Account and password. I used to get the usual purchase confirmation more directly. I don't know whether these prompts are related to the shared failure. For context: App Store release 1.1.1 (2), bundle com.zyiszy.PrivateVault, App Store ID 6810494416. The app diagnostic recorded iOS 27.0.1. It did not capture the exact OS build or hardware model. In one capture, 13 native shared calls failed between 2026-11-16 01:11:43.824 and 01:13:16.124 UTC. All were matched as StoreKitError.unknown, with NSError domain StoreKit.StoreKitError, code 2, and no underlying error. This is not SKErrorDomain code 2 / payment cancellation. The first call failed while the network path was unsatisfied. The next 12 failed with a satisfied path, the app active and protected data available. Those calls returned in 0-1 ms. Bounded retries, with about 2- and 5-second delays, did not help in that capture. Product catalog requests succeeded during the same period. I realize that does not confirm connectivity to every App Store endpoint. The app does not automatically call refresh() or AppStore.sync() during this eligibility check. After force-quitting, reopening and using Restore, I eventually got access again. Unfortunately, I don't have a log of the successful recovery, so I can't tell which call succeeded. Could StoreKit still need fresh authentication even though the App Store shows the account as signed in? Can that cause shared to throw unknown without an underlying error, and is there a supported way to distinguish it from missing app transaction data? For this acquisition-date check, should the recovery button call AppTransaction.refresh() and use its verified result directly? Is AppStore.sync() needed at all? If more evidence is needed, which StoreKit logs or diagnostic profile should I collect before trying recovery next time? I also submitted DTS Case-ID: 23550827 with a small Xcode project and the redacted timeline. The project builds and isolates the API calls, but it has its own bundle identity and does not reproduce this production account state.
1
0
208
5d
StoreKit 2 returns USA/USD in TestFlight but DEU/EUR in local Release build on the same device
Hi everyone, We are currently preparing the release of our Flutter-based iOS application and are experiencing an unusual StoreKit 2 storefront issue that only occurs when the app is installed through TestFlight. The problem When our application is installed through TestFlight, StoreKit 2 consistently returns the United States storefront (USA), and all six auto-renewable subscription products are displayed with USD prices. However, both the regular Apple Account and the Sandbox Apple Account are configured for Germany. We have verified the following: All six subscription products are correctly configured in App Store Connect with EUR prices for Germany. The subscriptions are available in Germany, Austria, and Switzerland. We created a completely new Sandbox tester with Germany selected during account creation, using an email address that had never previously been used for sandbox testing. The issue occurs on two different physical devices (iPhone and iPad). No local StoreKit configuration file is used. Our application does not override the storefront, modify localized prices, or contain any hardcoded USD fallback. Controlled comparison We performed additional tests using the same application code on the same iPhone. The results were: Installation method Storefront Currency Local Debug build via Xcode/Flutter DEU EUR Local development-signed Release build via Flutter DEU EUR TestFlight Release build USA USD The locally installed Release build successfully retrieves all six subscription products with their correct German prices. For example, StoreKit returns the following values for one of our subscriptions: Local Release build: Storefront.current.countryCode = DEU Product currencyCode = EUR Product.displayPrice = 6,99 € TestFlight build: Storefront.current.countryCode = USA Product currencyCode = USD Both builds use the same StoreKit 2 integration and product identifiers. Technical environment Framework: Flutter StoreKit integration: StoreKit 2 Flutter plugin: in_app_purchase_storekit 0.4.11+2 Devices: Physical iPhone and iPad iOS/iPadOS: 26.6.2 Subscription products: Six auto-renewable subscriptions Expected storefront: Germany (DEU) Actual TestFlight storefront: United States (USA) We have traced the storefront country code directly to StoreKit 2’s Storefront.current.countryCode and the localized prices to the product information returned by Product.products(for:). There is no application-level storefront override or price conversion. Questions Why would StoreKit 2 return a different storefront in TestFlight compared with a locally installed development-signed Release build on the same physical device? Could TestFlight use a different sandbox storefront or Apple Account context than a locally installed build? Is there a recommended way to diagnose or reset the storefront association used by TestFlight? Has anyone experienced similar behavior where TestFlight consistently returns USA despite using a German Apple Account and newly created German sandbox testers? We have already contacted Apple Developer Support and followed their recommendation to create a completely new German sandbox tester, but the issue persists. Any guidance from Apple engineers or developers who have encountered similar behavior would be greatly appreciated. Thank you!
4
0
146
5d
StoreKit 2 returns USA/USD in TestFlight but DEU/EUR in local Release build on the same device
Hi everyone, We are currently preparing the release of our Flutter-based iOS application and are experiencing an unusual StoreKit 2 storefront issue that only occurs when the app is installed through TestFlight. The problem When our application is installed through TestFlight, StoreKit 2 consistently returns the United States storefront (USA), and all six auto-renewable subscription products are displayed with USD prices. However, both the regular Apple Account and the Sandbox Apple Account are configured for Germany. We have verified the following: All six subscription products are correctly configured in App Store Connect with EUR prices for Germany. The subscriptions are available in Germany, Austria, and Switzerland. We created a completely new Sandbox tester with Germany selected during account creation, using an email address that had never previously been used for sandbox testing. The issue occurs on two different physical devices (iPhone and iPad). No local StoreKit configuration file is used. Our application does not override the storefront, modify localized prices, or contain any hardcoded USD fallback. Controlled comparison We performed additional tests using the same application code on the same iPhone. The results were: Installation method Storefront Currency Local Debug build via Xcode/Flutter DEU EUR Local development-signed Release build via Flutter DEU EUR TestFlight Release build USA USD The locally installed Release build successfully retrieves all six subscription products with their correct German prices. For example, StoreKit returns the following values for one of our subscriptions: Local Release build: Storefront.current.countryCode = DEU Product currencyCode = EUR Product.displayPrice = 6,99 € TestFlight build: Storefront.current.countryCode = USA Product currencyCode = USD Both builds use the same StoreKit 2 integration and product identifiers. Technical environment Framework: Flutter StoreKit integration: StoreKit 2 Flutter plugin: in_app_purchase_storekit 0.4.11+2 Devices: Physical iPhone and iPad iOS/iPadOS: 26.6.2 Subscription products: Six auto-renewable subscriptions Expected storefront: Germany (DEU) Actual TestFlight storefront: United States (USA) We have traced the storefront country code directly to StoreKit 2’s Storefront.current.countryCode and the localized prices to the product information returned by Product.products(for:). There is no application-level storefront override or price conversion. Questions Why would StoreKit 2 return a different storefront in TestFlight compared with a locally installed development-signed Release build on the same physical device? Could TestFlight use a different sandbox storefront or Apple Account context than a locally installed build? Is there a recommended way to diagnose or reset the storefront association used by TestFlight? Has anyone experienced similar behavior where TestFlight consistently returns USA despite using a German Apple Account and newly created German sandbox testers? We have already contacted Apple Developer Support and followed their recommendation to create a completely new German sandbox tester, but the issue persists. Any guidance from Apple engineers or developers who have encountered similar behavior would be greatly appreciated. Thank you!
1
0
82
5d
TestFlight: StoreKit 2 product metadata shows USD 0.99 and no trial while the purchase sheet reports the configured offer
We are investigating a discrepancy between StoreKit 2 product metadata and the Apple purchase confirmation sheet in an iPad app distributed through internal TestFlight. The app offers one auto-renewable monthly subscription, configured for China mainland at CNY 6.80/month with a two-week introductory free trial. We would appreciate guidance on targeted diagnostics, without assuming that the cause is an Apple platform defect. Observed product metadata: build 1.0 (4) On an iPad (A16) running iPadOS 27.0.1, we independently verified the installed build and captured these public diagnostic fields during one product-loading invocation: Storefront.current.countryCode = CHN Product.priceFormatStyle.currencyCode = USD Product.price = 0.99 Product.displayPrice = US$0.99 Product.subscription.introductoryOffer = nil Product.subscription.isEligibleForIntroOffer = trueThe product and subscription-group identifiers matched the configured identifiers. Product metadata and Storefront.current were read sequentially with asynchronous calls, so this is not an atomic StoreKit snapshot. The currency and offer fields above are logged values, rather than an inference from the custom UI. For this build and product, the tester reported that the Apple system purchase sheet displayed a two-week free trial followed by CNY 6.80/month. We did not capture a screenshot of that system sheet, and no successful purchase or charge is being claimed. Subsequent replacement product: build 1.0 (5) The developer subsequently deleted the original product and created a replacement in the same subscription group. We saved and refreshed App Store Connect to check the replacement's China-mainland availability, CNY 6.80 monthly price, and two-week free-trial offer. Build 1.0 (5) uses the replacement identifier and is available in the existing internal TestFlight group. The tester confirmed installing build 5 and supplied an App screenshot showing US$0.99/month without the trial overview. The screenshot itself does not contain the build number; that attribution relies on the installation report. We have not yet captured fresh raw Product fields for this replacement. The tester also reports that its system purchase sheet is normal, but has not supplied its exact current wording or a screenshot. We therefore keep this evidence separate from the build 4 log values. Changing the ordinary Apple account under Media & Purchases did not change the reported App display. This was not a dedicated Sandbox Apple Account comparison. We have not established the replacement product's propagation state or the platform root cause. Relevant implementation path The following condensed excerpts show the production path, not a standalone reproduction project. Validation, state handling, and transaction verification are omitted here: // Product loading: let values = try await Product.products(for: [id]) guard values.count == 1, let product = values.first, product.id == id else { throw SubscriptionClientError.invalidProduct } products[id] = product // The UI model copies product.displayPrice directly. // Later, in the purchase method: guard let product = products[productID] else { throw SubscriptionClientError.unavailable } return try resolvePurchase(try await product.purchase(confirmIn: scene))Within a single completed load, the UI fields and cached purchase Product come from the same result and configured identifier. We do not convert the display price to USD or configure a separate CNY price for the system sheet. The trial overview requires an eligible two-week free-trial offer in the product data. Audited distribution artifacts did not contain a local StoreKit testing configuration or price fixture. What diagnostics would help distinguish product-metadata/storefront behavior from application state handling? Is a dedicated Sandbox-account storefront comparison the appropriate next control? Are there documented refresh requirements or known TestFlight issues relevant to this discrepancy? The existing build already logs product identifiers, raw price, currency, offer structure, and eligibility, so we can collect a targeted replacement-product observation if useful.
3
0
109
5d
Storefront.current.countryCode returns USA despite Apple ID, device region, and sandbox tester all set to Spain
We have an app in TestFlight with a subscription group and an introductory offer (7-day free trial) configured only for Spain. When testing a sandbox purchase, no free trial is offered and prices display in USD. We confirmed via Purchases.storefront (RevenueCat SDK, which wraps Storefront.current.countryCode from StoreKit natively) that the resolved storefront is consistently USA, not ESP. Steps taken to troubleshoot, all showing Spain, with no change to the result: Real Apple ID's country/region (Settings > Name > Media & Purchases > View Account): Spain, locked/non-editable. 3 different sandbox tester accounts (App Store Connect > Sandbox): all set to Spain. Device Language & Region (Settings > General): Spain. No VPN active. Fully deleted and reinstalled the app (not just relaunched). Fully signed out and back in to the real Apple ID on the device, and changed/reverted device Region. Checked billing address on file for the payment method: Spain. Checked carrier/SIM: Orange España. App-level Pricing and Availability in App Store Connect was never configured before (base country defaulted to United States) — we corrected it to Spain and waited 24+ hours. No change. Unchecked "Pause subscription renewals for this tester" (an Apple sandbox testing flag meant to simulate a Terms & Conditions interruption) — no change. In every case, storefront.countryCode continues to return "USA". Question: What else determines the resolved StoreKit storefront for a given Apple ID/device combination, given that every visible setting indicates Spain? Is there a known cache that needs to be cleared on Apple's side? (We also have an open Apple Developer Support case, #30000007050484, still awaiting a first response after 6 days.)
2
0
115
1w
Subscriptions load in TestFlight sandbox but not during App Review — 2.1(b), third rejection
Our first submission has now been rejected under Guideline 2.1(b), with the message: "the in-app purchases do not load successfully." Each review was performed on an iPad Air 11-inch (M3) running iPadOS 26.6. The app sells only auto-renewable subscriptions. We cannot reproduce the failure, and we have verified every part of the configuration we can think of. WHAT WE VERIFIED (via the App Store Connect API, not just the UI) Two subscriptions in one group, state READY_TO_SUBMIT Product IDs exactly match what the app requests Available in 175 territories, including the United States Prices set, en-US localizations present for both products and for the group App review screenshots attached to both, state COMPLETE Both subscriptions are included in the review submission (READY_FOR_REVIEW) Paid Apps Agreement: Active. Bank account: Active. Tax forms: Active. WHAT WORKS On our own devices, installed via TestFlight (sandbox environment), the products load correctly and a purchase completes and activates as expected. This works on both a real Apple ID and a Sandbox Tester account. WHAT WE OBSERVED FROM THE REVIEW SESSION We use RevenueCat. Their server-side API returns our offering with both packages and the correct product identifiers, so the offering metadata is fine. Our backend also shows that the reviewer's session reached our servers and signed in successfully at the review timestamp, so the device had working network connectivity. That leaves StoreKit itself returning no products on the reviewer's device, which is what empties the offering. QUESTIONS Are there known conditions under which StoreKit returns no products in the App Review sandbox for subscriptions that are in "Ready to Submit" and are attached to the same submission as the binary? For an app that has never been approved, is product loading during review handled differently from a normal sandbox session on a released app? Is there any way to obtain diagnostics from a review session, or to ask the reviewer for a screenshot of the failing screen? Replies in Resolution Center so far have only repeated the original rejection text. Is there anything specific to iPadOS 26.6 that could affect StoreKit 2 product lookups? For the next submission we have added a timeout and automatic retries around the product lookup, plus a visible retry control instead of a spinner, in case the failure is a transient cold-start timeout. But we would rather understand the actual cause than keep guessing. Any pointers appreciated.
3
1
586
1w
StoreKit 2: Does Transaction.currentEntitlements get updated when my app isn't running?
TL;DR: Does iOS automatically receive App Store transaction updates in the background when internet connection is available so the backing storage state of Transaction.currentEntitlements gets synced even when my app is not running? Or does iOS update Transaction.currentEntitlements only when my app is running? The long version: Imagine the following situation: A user has purchased a non-consumable IAP in my app and is granted the locked premium content. The IAP transaction is now present in Transaction.currentEntitlements (it's also cached locally). The user blocks internet access every time before my app gets opened (either enables the Airplane mode and/or disconnects from the Wi-Fi before launching my app). So from this point on, my app never gets a chance to connect to the internet. The user gets refunded for the IAP. The user uses their iPhone to browse the internet via Safari, checks emails, etc. Then, before launching my app, the user blocks internet access. My app gets is launched (without internet access) and reads entitlements from Transaction.currentEntitlements. The question is: does the StoreKit service know that the IAP has been refunded? Did iOS update the local cached storage of Transaction.currentEntitlements while the user was connected to the internet in step 4? Or will Transaction.currentEntitlements contain the old state from step 1 so the app won't know about the refund and the user will be able to use my app's premium content which has been refunded by now? Is the behavior the same for auto-renewable subscriptions as it is for non-consumable IAPs?
1
0
628
1w
Trials entering billing retry instead of converting
We have a monthly subscription and an annual subscription with a 3-day free trial. The monthly converts fine. On the annual, trials tend to enter billing retry rather than convert — users don't cancel, the charge just fails. We've audited our implementation and found nothing on our side that participates in the renewal charge. What can a developer actually do about this? Does trial length, price point, or using a paid introductory offer instead of a free trial make a difference?
1
0
156
1w
Build behaving differently in testflight compared to simulator
Hi all I have an app I’m pretty much done with, and on the Xcode simulator it works perfectly and the IAP shows us when the purchase buttons are clicked but for some reason when it goes to testflight none of the buttons respond, is there any reason that would cause it to behave differently in testflight when its coded correctly and works in the simulator. thanks
1
0
612
1w
Is receiving the same transaction multiple times from Transaction.updates expected behavior?
I'm seeing behavior similar to what was reported in this thread: https://developer.apple.com/forums/thread/816344 I read the discussion in the related thread (816320) as well, but I couldn't determine whether receiving the same transaction multiple times from Transaction.updates is considered expected behavior. In my case, I'm testing an auto-renewable subscription in the Sandbox environment. After successfully processing and calling finish() on a transaction, Transaction.updates sometimes provides another transaction with the same transactionId. I've also observed the same transactionId being delivered multiple times through Transaction.updates itself. I compared the JWS representations of these transactions. They are not byte-for-byte identical, but the transaction information appears to be the same. The only differences I've identified are: signedDate deviceVerificationNonce deviceVerification This looks as though the same transaction is being signed again at a different time. I'd like to clarify the intended way to handle this: Is it expected behavior for Transaction.updates to deliver the same transactionId multiple times in this way? If so, after an app has successfully processed and finished a transaction, is it safe to recognize subsequent transactions with the same transactionId as already processed, skip entitlement-related processing, and simply call finish() on them? In other words, can an app use transactionId to prevent duplicate processing of transactions that it has already successfully handled? I'm specifically interested in whether doing so could cause the app to miss any meaningful update that StoreKit might later deliver using the same transactionId.
3
0
838
1w
App Review sandbox: revenuecat product loads, then STORE_PROBLEM followed by PRODUCT_NOT_AVAILABLE_FOR_PURCHASE on iPadOS 26.6
Hello, I am investigating an intermittent In-App Purchase failure that occurred during App Review for the first release of my app. Environment Review device: iPad Air 11-inch (M3) OS: iPadOS 26.6 Environment: App Review sandbox Product type: Consumable StoreKit integration: RevenueCat through react-native-purchases 10.4.3 Observed behavior StoreKit successfully returned the products, localized names, and prices. The reviewer could see the credit packs and initiate the native purchase flow. My diagnostics show this sequence: Purchase initiated PURCHASE_CANCELLED; no transaction evidence Purchase initiated again RevenueCat code 2: STORE_PROBLEM elapsed: 9.4 seconds no transaction evidence Purchase initiated again RevenueCat code 5: PRODUCT_NOT_AVAILABLE_FOR_PURCHASE no transaction evidence Purchase initiated again RevenueCat code 5: PRODUCT_NOT_AVAILABLE_FOR_PURCHASE elapsed: 0.6 seconds no transaction evidence code-block The relevant sanitized logs are: { "occurredAt": "2026-08-25T12:52:59.733Z", "platform": "ios", "appVersion": "1.0.0", "build": "14", "productId": "HIDDEN_FOR_DISPLAY", "stage": "STORE_CHECKOUT", "providerCode": "2", "providerReadableCode": "STORE_PROBLEM", "transactionEvidence": false, "elapsedMs": 9417 } code-block { "occurredAt": "2026-08-25T12:55:42.752Z", "platform": "ios", "appVersion": "1.0.0", "build": "14", "productId": "HIDDEN_FOR_DISPLAY", "stage": "STORE_CHECKOUT", "providerCode": "5", "providerReadableCode": "PRODUCT_NOT_AVAILABLE_FOR_PURCHASE", "transactionEvidence": false, "elapsedMs": 637 } code-block No App Store transaction was created, and therefore RevenueCat received no transaction or webhook for these attempts. Configuration verified I confirmed that: The affected product and the other consumable products are attached to the App Review submission. Product IDs match between the app, App Store Connect, and RevenueCat. Prices and localizations are configured. The products are available in the relevant storefronts. The Paid Apps Agreement is active. Banking and tax information are active. The In-App Purchase capability is present. The distribution build does not use a local StoreKit configuration file. The same build and affected product completed successfully afterward on a physical device using Apple Sandbox. The native purchase sheet opened, the transaction completed, and the consumable content was delivered successfully in my reproduction. The product metadata clearly remained available because its localized name and price were displayed. However, after the initial STORE_PROBLEM, subsequent purchase requests were rejected almost immediately as PRODUCT_NOT_AVAILABLE_FOR_PURCHASE. I do not have the underlying Apple NSError, such as an ASDServerErrorDomain or AMSErrorDomain value, because it was not exposed in my remote diagnostic record. Questions Can a failed sandbox transaction leave the StoreKit account/session or commerce-catalog state temporarily inconsistent, causing subsequent requests for an otherwise loaded product to return storeProductNotAvailable? Does StoreKit use separate metadata and transaction-eligibility services, allowing product information to load while the same product is rejected during purchase()? Are there known sandbox or StoreKit issues on iPadOS 26.6 that could produce this sequence? Could a stale App Review sandbox account token or storefront session explain the transition from STORE_PROBLEM to PRODUCT_NOT_AVAILABLE_FOR_PURCHASE? Is there any developer-side configuration that could explain this when the same product and binary complete successfully using another sandbox session? What additional logging should I capture from RevenueCat’s React Native SDK to preserve the complete underlying Apple error chain?
3
0
1k
1w
StoreKit Testing on iOS 27.2 Simulator returns the refunded renewal when repurchasing a subscription
I'm testing auto-renewable subscriptions with a local .storekit configuration in Xcode 27.2 (27B52). With the same app and configuration on iPhone 17 simulators, I get different results on iOS 26.2 (23C54) and iOS 27.2 (24B8117). Set SKTestSession.timeRate to .oneRenewalEveryThirtySeconds, then purchase an auto-renewable subscription in the app with StoreKit 2. Wait for the original period to expire and the first automatic renewal to appear. Refund that renewal using SKTestSession.refundTransaction(identifier:) and wait for the app to receive the revocation. While the app is still running, purchase the same product again and inspect the verified transaction returned directly by Product.purchase(). Both runtimes return .success with a verified transaction. On iOS 26.2, the repurchase returns a new transaction ID with revocationDate == nil, and Transaction.currentEntitlements contains it. On iOS 27.2, the result has the same ID, purchaseDate, and non-nil revocationDate as the refunded renewal. The current entitlement check yields no verified unrevoked transaction. This reproduced for both a monthly and a three-month subscription. The monthly case also reproduced when calling Product.purchase() without an appAccountToken option. Is this a known issue in StoreKit Testing on iOS 27.2 Simulator? Is there a supported way to test the repurchase path while preserving the refunded transaction in the test history?
0
0
78
1w
Title: StoreKit Sandbox: supportsMultiSeatPurchase is true, but pricingTerms contains no seatBased terms
We’re testing an annual multiseat subscription on a physical iPad. StoreKit returns the expected product and reports supportsMultiSeatPurchase == true, but its pricingTerms contains one term and no seatBased terms. Our app therefore cannot calculate a two-seat quote and stops before attempting a purchase. Environment iPad Air 11-inch (M3) iPadOS 27.3 beta (24C5037i) Xcode 27.3 beta (27C5020n) Development-signed app, version 1.0, diagnostic build 44 Physical-device testing with a US Sandbox purchaser App Store Connect configuration Annual auto-renewable subscription Multiseat purchases allowed Invitations provided by Apple Annual upfront availability enabled for the United States at USD 6.99 Subscription status: Prepare for Submission Sandbox purchases and renewals enabled Steps to reproduce Request the subscription using Product.products(for:). Confirm that the expected annual product is returned. Check supportsMultiSeatPurchase, which returns true. Inspect pricingTerms for supported upfront seatBased terms. Attempt to prepare a quote for two total seats. Actual result Total pricing terms: 1 Seat-based pricing terms: 0 Supported group pricing terms: 0 No purchase is attempted. Production sponsorship sales remain disabled. Expected result A supported upfront seat-based pricing term with Apple-provided pricing tiers that can be used to calculate a two-seat quote. Questions Is additional configuration or account eligibility required for Sandbox to return seat-based pricing terms? Must the subscription progress beyond Prepare for Submission before multiseat pricing can be tested? Can supportsMultiSeatPurchase legitimately return true while no seat-based pricing terms are available? If so, what conditions cause this? Is this a known limitation in this beta, and is there a supported workaround or recommended testing configuration? The issue was reproduced again on November 10, 2026, at approximately 9:57 PM Mountain Time. A sysdiagnose captured at 10:03:11 PM Mountain Time was attached privately to FB25451377. DTS directed us to post here under Case-ID: 23369152. We can provide a focused reproduction project if needed.
0
0
88
1w
StoreKit 2 returns no products for a non-renewing subscription in TestFlight Sandbox (China mainland)
I’m testing the first in-app purchase for an iOS app. It is a non-renewing subscription that grants 12 months of access. On November 9, a physical iPhone running our TestFlight build reproduced the same issue twice in the China mainland Sandbox storefront. Setup checked at the time The annual product was Ready to Submit in App Store Connect, with China mainland availability, a CNY 98 price, and a Simplified Chinese localization. The annual product identifier matched the identifier requested by the app. The explicit Bundle ID matched App Store Connect and had In-App Purchase enabled. The Paid Apps Agreement was active, and banking and tax records were in place. We used a mainland-China Sandbox tester and called the native StoreKit 2 Product.products(for:) API. The request included the configured annual product and an old monthly identifier that has no corresponding product in App Store Connect. Steps and results Install the app from TestFlight on a physical iPhone and open the purchase screen in Sandbox. Refresh the available products. We expect the annual product and its localized price to appear. Product.products(for:) completes with an empty array. Device logs show an HTTP 200 response from the China mainland Sandbox catalog followed by Ignoring empty product response. After the 600-second cache lifetime, the query received a different server correlation key and still returned no products. This occurs during product lookup, before any purchase call. TN3186 says that Sandbox testing can take place before submission for review. Has anyone reproduced this specifically with a non-renewing subscription? Is there another way to verify Sandbox catalog visibility for the configured annual product or diagnose why it is omitted? An annual-only StoreKit query would be a useful follow-up test. We can share the exact app and product identifiers, request correlation keys, and device diagnostics with Apple through Feedback Assistant.
0
0
40
1w
Question About StoreKit Request Rate Limits and Capacity
Hello, We are looking for information about the capacity limits for requests sent directly to the App Store through the StoreKit SDK when clients make in-app purchases. In our expected usage, we anticipate a peak request volume of approximately 30 transactions per second (TPS) through this communication path. Does anyone know if Apple imposes any rate limits or maximum request processing limits on requests sent directly to the App Store via the StoreKit SDK? If such limits exist, it would be helpful if you could share any details about the applicable thresholds. Thank you!
0
0
86
1w
StoreKit 2 – AppStore.sync() fails with StoreKitError.unknown (code 2) in TestFlight**
Subject: StoreKit 2 – AppStore.sync() fails with StoreKitError.unknown (code 2) in TestFlight Hello Apple Developer forum We are investigating a reproducible issue with StoreKit 2's AppStore.sync() in our iOS application, Elins Nystan. Environment App: Elins Nystan Bundle Identifier: poworg.ElinsNystan-2 TestFlight version: 1.43 (build 8) Device: iPhone 16 Date: November 10, 2026 Environment: TestFlight / App Store sandbox StoreKit: StoreKit 2 Problem The app correctly recognizes an existing subscription and grants Premium access to the account associated with the original purchase. Premium remains active after restarting the application, and subscription-dependent functionality works correctly. However, when the user selects “Restore Purchases,” the app calls AppStore.sync(). An Apple account authentication dialog appears and the user enters their password. After approximately 26 seconds, AppStore.sync() throws an error. Captured device logs All timestamps below are UTC: 2026-11-10 21:33:10 — restore.started 2026-11-10 21:33:10 — restore.syncStarted 2026-11-10 21:33:36 — restore.syncFailed Error details: Domain: StoreKit.StoreKitError Code: 2 Classification: unknownThe three log events share the same operation identifier. The app reports that Restore could not be completed due to an unknown error. Additional observations Premium was active before Restore. Previous testing confirmed that Premium remained active after a failed Restore. No corresponding backend reconciliation request was observed during an earlier Restore failure. No confirmed application-side cancellation or overlapping Restore request has been identified. AppStore.sync() has been part of the Restore implementation since December 2025. We have not identified a source-code regression that explains the StoreKit error. We have not verified a previously successful Restore under equivalent TestFlight conditions. We are not attempting to change subscription ownership or bypass purchase verification. Questions What conditions can cause AppStore.sync() to throw StoreKitError.unknown (code 2) in TestFlight? Could this be related to the sandbox Apple Account, authentication, or an existing subscription with multiple renewal transactions? Are there additional StoreKit or system diagnostics that would help identify the underlying cause? Is there a recommended way to recover from this error while preserving the existing verified subscription entitlement? Is this a known TestFlight/sandbox issue, or should we investigate a specific application configuration? We can provide redacted device logs and additional technical details if required. Thank you for your assistance.
0
0
57
1w
First iOS App Stuck in Waiting for Review for Over 30 Days –– No Support Response
Hello Apple App Review Team, My first iOS app, Loopa – Video & Audio Editor (version 1.0.0), has been stuck in "Waiting for Review" for approximately 30 days. I have already contacted Apple Developer Support through the official contact form but have not received a response. Could an Apple representative please investigate whether my submission is progressing normally or whether additional information is required? I would appreciate any assistance. Thank you.
0
0
36
1w
Sandbox: CONSUMPTION_REQUEST received but REFUND / REFUND_DECLINED never sent (auto-renewable subscription)
We are testing refunds for an auto-renewable subscription in the Sandbox environment using Transaction.beginRefundRequest(in:), following "Testing refund requests". Our server receives CONSUMPTION_REQUEST, but a REFUND or REFUND_DECLINED notification never follows. What we did (4 transactions, Nov 16, 2026) Purchased a monthly subscription with sandbox renewal rates of 1 hour, 30 minutes and 5 minutes, then turned off auto-renew. Submitted the refund sheet: one request with a standard reason; others with Issue = Other and text GRANT_PRORATED. We also used a second sandbox account. For one transaction, we called Send Consumption Information v2 within 5 minutes of the CONSUMPTION_REQUEST. The body was customerConsented: true, deliveryStatus: DELIVERED, sampleContentProvided: false, refundPreference: GRANT_PRORATED. The API returned 202 Accepted. What we see CONSUMPTION_REQUEST arrives 1–2 minutes after the refund sheet is submitted. Our server returns HTTP 200, and Get Notification History shows the send attempt as SUCCESS. No REFUND or REFUND_DECLINED arrived. Get Refund History v2 is empty, Get Transaction Info shows no revocationDate, and Get Notification History has no refund notification. All other sandbox notifications are delivered within a second: SUBSCRIBED, DID_CHANGE_RENEWAL_STATUS, EXPIRED. In production, REFUND, REFUND_DECLINED and REFUND_REVERSED are delivered normally for the same app. Sandbox transaction IDs 2000001266241009, 2000001266277405, 2000001266288964, 2000001266312137 Feedback: FB25595203 Questions Is there a known issue with Sandbox not deciding refund requests for auto-renewable subscriptions after CONSUMPTION_REQUEST? Is there a supported way to receive a real REFUND notification in Sandbox for end-to-end server testing? Thank you.
Replies
0
Boosts
0
Views
72
Activity
4d
SKTestSession.setSimulatedError does not work - Products load successfully despite error configuration
Description I'm attempting to test error handling in my StoreKit implementation using SKTestSession.setSimulatedError(), but it doesn't trigger any errors. All StoreKit APIs (.loadProducts, .purchase, .appTransaction) succeed despite error simulation being configured before API calls. According to Apple's documentation, setSimulatedError(_:forAPI:) should cause the specified API to throw an error, but this doesn't happen in my testing environment. Background / Known issue I found a previous forum discussion: "SKTestSession.setSimulatedError() not working for .loadProducts API in iOS 26.2" which mentioned this was a bug in iOS 26.2 and was supposedly fixed in iOS 26.3. However, I'm experiencing the same issue in my current environment (Xcode 26.6 / iOS 26.5), which suggests either: The bug has regressed, or There's a different underlying issue, or I'm missing something in my implementation I wanted to report this to confirm whether this is still a known issue or if additional steps are needed. Environment Xcode: 26.6 Test Environment: iOS Simulator - iPhone 17 Pro(26.5) Testing Framework: XCTest StoreKitTest Framework: Included in Xcode Code Unit test code import XCTest import StoreKit import StoreKitTest final class StoreKitErrorTests: XCTestCase { func test_LoadProducts_SetSimulatedError() async throws { // Arrange let session = try SKTestSession(configurationFileNamed: "storekit") session.clearTransactions() session.disableDialogs = true // Set simulated error for loadProducts API try await session.setSimulatedError( .generic(.unknown), forAPI: .loadProducts ) // Act - Attempt to load products do { let products = try await Product.products(for: ["com.example.app.testproduct"]) // This line executes - products were loaded successfully print("[TEST] FAIL: Loaded \(products.count) products") XCTFail("setSimulatedError did not work - products loaded successfully") } catch { // This should execute, but it doesn't print("[TEST] PASS: Error was thrown") } } }.storekit file Note: Showing only the product definition. File also contains settings and version info. { "products" : [ { "displayPrice" : "1.23", "familyShareable" : false, "internalID" : "5AE6F98A", "localizations" : [ { "description" : "Test app", "displayName" : "LsStorekit", "locale" : "en_US" } ], "productID" : "com.example.app.testproduct", "referenceName" : "LsStorekit", "type" : "NonConsumable" } ] }Expected Behavior The Product.products(for:) call should throw an error because setSimulatedError(.generic(.unknown), forAPI: .loadProducts) was called before the API invocation. The test should: Configure the simulated error Attempt to load products Catch an error in the catch block Test passes with: "[TEST] PASS: Error was thrown" Actual Behavior Products are loaded successfully despite the error simulation: • The do block completes without throwing • 1 product is returned from Product.products(for:) • XCTFail() is called, indicating the error simulation didn't work • Test fails with: "[TEST] FAIL: Loaded 1 products" Console Output [TEST] FAIL: Loaded 1 products Additional Testing I've tested setSimulatedError with multiple APIs, and all show the same behavior: APIError configurationResult.loadProducts.generic(.unknown)No error thrown.purchase.generic(.unknown)No error thrown.appTransaction.generic(.unknown)No error thrown.appStoreSync.generic(.unknown)No error thrownWhat I've Already Tried • Calling setSimulatedError before app launch (in UI tests) • Calling setSimulatedError after app launch but before API calls • Using different error types (.generic(.unknown), .generic(.networkError(...))) • Testing in both Unit Tests and UI Tests • Using different APIs (.loadProducts, .purchase, .appTransaction) • Clearing transactions and resetting session state • Verifying the .storekit file is correctly loaded (products load successfully) • Running the app first (⌘R) to ensure StoreKit configuration is registered with the StoreKit daemon - This was necessary to fix an initial issue where products weren't loading at all Questions Is this a known limitation of SKTestSession.setSimulatedError()? Are there additional steps required to make error simulation work? Is there an alternative approach to test StoreKit error handling? Does this work in specific Xcode/iOS SDK versions only? Any guidance would be greatly appreciated. I need to test error handling in my StoreKit implementation, but cannot find a way to simulate errors reliably.
Replies
0
Boosts
0
Views
39
Activity
5d
Production AppTransaction.shared throws StoreKitError.unknown when reading original app acquisition date
I'm the developer of Freezon, and I ran into this on my own iPhone with the App Store version of the app. I use the verified AppTransaction.originalPurchaseDate to give Pro access to people who first downloaded the app before a published cutoff. This includes free downloads; I need the original acquisition date of the app itself, not an in-app purchase date. On this device, AppTransaction.shared repeatedly threw StoreKitError.unknown before returning a VerificationResult: let result = try await AppTransaction.shared switch result { case let .verified(transaction): let firstAcquisitionDate = transaction.originalPurchaseDate // Check early-adopter eligibility. case let .unverified(_, error): throw error }The error occurs at shared, before the switch. The App Store on this iPhone shows my Apple Account as signed in. However, when I purchase or restore, I keep getting asked for my password, and sometimes for both my Apple Account and password. I used to get the usual purchase confirmation more directly. I don't know whether these prompts are related to the shared failure. For context: App Store release 1.1.1 (2), bundle com.zyiszy.PrivateVault, App Store ID 6810494416. The app diagnostic recorded iOS 27.0.1. It did not capture the exact OS build or hardware model. In one capture, 13 native shared calls failed between 2026-11-16 01:11:43.824 and 01:13:16.124 UTC. All were matched as StoreKitError.unknown, with NSError domain StoreKit.StoreKitError, code 2, and no underlying error. This is not SKErrorDomain code 2 / payment cancellation. The first call failed while the network path was unsatisfied. The next 12 failed with a satisfied path, the app active and protected data available. Those calls returned in 0-1 ms. Bounded retries, with about 2- and 5-second delays, did not help in that capture. Product catalog requests succeeded during the same period. I realize that does not confirm connectivity to every App Store endpoint. The app does not automatically call refresh() or AppStore.sync() during this eligibility check. After force-quitting, reopening and using Restore, I eventually got access again. Unfortunately, I don't have a log of the successful recovery, so I can't tell which call succeeded. Could StoreKit still need fresh authentication even though the App Store shows the account as signed in? Can that cause shared to throw unknown without an underlying error, and is there a supported way to distinguish it from missing app transaction data? For this acquisition-date check, should the recovery button call AppTransaction.refresh() and use its verified result directly? Is AppStore.sync() needed at all? If more evidence is needed, which StoreKit logs or diagnostic profile should I collect before trying recovery next time? I also submitted DTS Case-ID: 23550827 with a small Xcode project and the redacted timeline. The project builds and isolates the API calls, but it has its own bundle identity and does not reproduce this production account state.
Replies
1
Boosts
0
Views
208
Activity
5d
StoreKit 2 returns USA/USD in TestFlight but DEU/EUR in local Release build on the same device
Hi everyone, We are currently preparing the release of our Flutter-based iOS application and are experiencing an unusual StoreKit 2 storefront issue that only occurs when the app is installed through TestFlight. The problem When our application is installed through TestFlight, StoreKit 2 consistently returns the United States storefront (USA), and all six auto-renewable subscription products are displayed with USD prices. However, both the regular Apple Account and the Sandbox Apple Account are configured for Germany. We have verified the following: All six subscription products are correctly configured in App Store Connect with EUR prices for Germany. The subscriptions are available in Germany, Austria, and Switzerland. We created a completely new Sandbox tester with Germany selected during account creation, using an email address that had never previously been used for sandbox testing. The issue occurs on two different physical devices (iPhone and iPad). No local StoreKit configuration file is used. Our application does not override the storefront, modify localized prices, or contain any hardcoded USD fallback. Controlled comparison We performed additional tests using the same application code on the same iPhone. The results were: Installation method Storefront Currency Local Debug build via Xcode/Flutter DEU EUR Local development-signed Release build via Flutter DEU EUR TestFlight Release build USA USD The locally installed Release build successfully retrieves all six subscription products with their correct German prices. For example, StoreKit returns the following values for one of our subscriptions: Local Release build: Storefront.current.countryCode = DEU Product currencyCode = EUR Product.displayPrice = 6,99 € TestFlight build: Storefront.current.countryCode = USA Product currencyCode = USD Both builds use the same StoreKit 2 integration and product identifiers. Technical environment Framework: Flutter StoreKit integration: StoreKit 2 Flutter plugin: in_app_purchase_storekit 0.4.11+2 Devices: Physical iPhone and iPad iOS/iPadOS: 26.6.2 Subscription products: Six auto-renewable subscriptions Expected storefront: Germany (DEU) Actual TestFlight storefront: United States (USA) We have traced the storefront country code directly to StoreKit 2’s Storefront.current.countryCode and the localized prices to the product information returned by Product.products(for:). There is no application-level storefront override or price conversion. Questions Why would StoreKit 2 return a different storefront in TestFlight compared with a locally installed development-signed Release build on the same physical device? Could TestFlight use a different sandbox storefront or Apple Account context than a locally installed build? Is there a recommended way to diagnose or reset the storefront association used by TestFlight? Has anyone experienced similar behavior where TestFlight consistently returns USA despite using a German Apple Account and newly created German sandbox testers? We have already contacted Apple Developer Support and followed their recommendation to create a completely new German sandbox tester, but the issue persists. Any guidance from Apple engineers or developers who have encountered similar behavior would be greatly appreciated. Thank you!
Replies
4
Boosts
0
Views
146
Activity
5d
StoreKit 2 returns USA/USD in TestFlight but DEU/EUR in local Release build on the same device
Hi everyone, We are currently preparing the release of our Flutter-based iOS application and are experiencing an unusual StoreKit 2 storefront issue that only occurs when the app is installed through TestFlight. The problem When our application is installed through TestFlight, StoreKit 2 consistently returns the United States storefront (USA), and all six auto-renewable subscription products are displayed with USD prices. However, both the regular Apple Account and the Sandbox Apple Account are configured for Germany. We have verified the following: All six subscription products are correctly configured in App Store Connect with EUR prices for Germany. The subscriptions are available in Germany, Austria, and Switzerland. We created a completely new Sandbox tester with Germany selected during account creation, using an email address that had never previously been used for sandbox testing. The issue occurs on two different physical devices (iPhone and iPad). No local StoreKit configuration file is used. Our application does not override the storefront, modify localized prices, or contain any hardcoded USD fallback. Controlled comparison We performed additional tests using the same application code on the same iPhone. The results were: Installation method Storefront Currency Local Debug build via Xcode/Flutter DEU EUR Local development-signed Release build via Flutter DEU EUR TestFlight Release build USA USD The locally installed Release build successfully retrieves all six subscription products with their correct German prices. For example, StoreKit returns the following values for one of our subscriptions: Local Release build: Storefront.current.countryCode = DEU Product currencyCode = EUR Product.displayPrice = 6,99 € TestFlight build: Storefront.current.countryCode = USA Product currencyCode = USD Both builds use the same StoreKit 2 integration and product identifiers. Technical environment Framework: Flutter StoreKit integration: StoreKit 2 Flutter plugin: in_app_purchase_storekit 0.4.11+2 Devices: Physical iPhone and iPad iOS/iPadOS: 26.6.2 Subscription products: Six auto-renewable subscriptions Expected storefront: Germany (DEU) Actual TestFlight storefront: United States (USA) We have traced the storefront country code directly to StoreKit 2’s Storefront.current.countryCode and the localized prices to the product information returned by Product.products(for:). There is no application-level storefront override or price conversion. Questions Why would StoreKit 2 return a different storefront in TestFlight compared with a locally installed development-signed Release build on the same physical device? Could TestFlight use a different sandbox storefront or Apple Account context than a locally installed build? Is there a recommended way to diagnose or reset the storefront association used by TestFlight? Has anyone experienced similar behavior where TestFlight consistently returns USA despite using a German Apple Account and newly created German sandbox testers? We have already contacted Apple Developer Support and followed their recommendation to create a completely new German sandbox tester, but the issue persists. Any guidance from Apple engineers or developers who have encountered similar behavior would be greatly appreciated. Thank you!
Replies
1
Boosts
0
Views
82
Activity
5d
TestFlight: StoreKit 2 product metadata shows USD 0.99 and no trial while the purchase sheet reports the configured offer
We are investigating a discrepancy between StoreKit 2 product metadata and the Apple purchase confirmation sheet in an iPad app distributed through internal TestFlight. The app offers one auto-renewable monthly subscription, configured for China mainland at CNY 6.80/month with a two-week introductory free trial. We would appreciate guidance on targeted diagnostics, without assuming that the cause is an Apple platform defect. Observed product metadata: build 1.0 (4) On an iPad (A16) running iPadOS 27.0.1, we independently verified the installed build and captured these public diagnostic fields during one product-loading invocation: Storefront.current.countryCode = CHN Product.priceFormatStyle.currencyCode = USD Product.price = 0.99 Product.displayPrice = US$0.99 Product.subscription.introductoryOffer = nil Product.subscription.isEligibleForIntroOffer = trueThe product and subscription-group identifiers matched the configured identifiers. Product metadata and Storefront.current were read sequentially with asynchronous calls, so this is not an atomic StoreKit snapshot. The currency and offer fields above are logged values, rather than an inference from the custom UI. For this build and product, the tester reported that the Apple system purchase sheet displayed a two-week free trial followed by CNY 6.80/month. We did not capture a screenshot of that system sheet, and no successful purchase or charge is being claimed. Subsequent replacement product: build 1.0 (5) The developer subsequently deleted the original product and created a replacement in the same subscription group. We saved and refreshed App Store Connect to check the replacement's China-mainland availability, CNY 6.80 monthly price, and two-week free-trial offer. Build 1.0 (5) uses the replacement identifier and is available in the existing internal TestFlight group. The tester confirmed installing build 5 and supplied an App screenshot showing US$0.99/month without the trial overview. The screenshot itself does not contain the build number; that attribution relies on the installation report. We have not yet captured fresh raw Product fields for this replacement. The tester also reports that its system purchase sheet is normal, but has not supplied its exact current wording or a screenshot. We therefore keep this evidence separate from the build 4 log values. Changing the ordinary Apple account under Media & Purchases did not change the reported App display. This was not a dedicated Sandbox Apple Account comparison. We have not established the replacement product's propagation state or the platform root cause. Relevant implementation path The following condensed excerpts show the production path, not a standalone reproduction project. Validation, state handling, and transaction verification are omitted here: // Product loading: let values = try await Product.products(for: [id]) guard values.count == 1, let product = values.first, product.id == id else { throw SubscriptionClientError.invalidProduct } products[id] = product // The UI model copies product.displayPrice directly. // Later, in the purchase method: guard let product = products[productID] else { throw SubscriptionClientError.unavailable } return try resolvePurchase(try await product.purchase(confirmIn: scene))Within a single completed load, the UI fields and cached purchase Product come from the same result and configured identifier. We do not convert the display price to USD or configure a separate CNY price for the system sheet. The trial overview requires an eligible two-week free-trial offer in the product data. Audited distribution artifacts did not contain a local StoreKit testing configuration or price fixture. What diagnostics would help distinguish product-metadata/storefront behavior from application state handling? Is a dedicated Sandbox-account storefront comparison the appropriate next control? Are there documented refresh requirements or known TestFlight issues relevant to this discrepancy? The existing build already logs product identifiers, raw price, currency, offer structure, and eligibility, so we can collect a targeted replacement-product observation if useful.
Replies
3
Boosts
0
Views
109
Activity
5d
Storefront.current.countryCode returns USA despite Apple ID, device region, and sandbox tester all set to Spain
We have an app in TestFlight with a subscription group and an introductory offer (7-day free trial) configured only for Spain. When testing a sandbox purchase, no free trial is offered and prices display in USD. We confirmed via Purchases.storefront (RevenueCat SDK, which wraps Storefront.current.countryCode from StoreKit natively) that the resolved storefront is consistently USA, not ESP. Steps taken to troubleshoot, all showing Spain, with no change to the result: Real Apple ID's country/region (Settings > Name > Media & Purchases > View Account): Spain, locked/non-editable. 3 different sandbox tester accounts (App Store Connect > Sandbox): all set to Spain. Device Language & Region (Settings > General): Spain. No VPN active. Fully deleted and reinstalled the app (not just relaunched). Fully signed out and back in to the real Apple ID on the device, and changed/reverted device Region. Checked billing address on file for the payment method: Spain. Checked carrier/SIM: Orange España. App-level Pricing and Availability in App Store Connect was never configured before (base country defaulted to United States) — we corrected it to Spain and waited 24+ hours. No change. Unchecked "Pause subscription renewals for this tester" (an Apple sandbox testing flag meant to simulate a Terms & Conditions interruption) — no change. In every case, storefront.countryCode continues to return "USA". Question: What else determines the resolved StoreKit storefront for a given Apple ID/device combination, given that every visible setting indicates Spain? Is there a known cache that needs to be cleared on Apple's side? (We also have an open Apple Developer Support case, #30000007050484, still awaiting a first response after 6 days.)
Replies
2
Boosts
0
Views
115
Activity
1w
Subscriptions load in TestFlight sandbox but not during App Review — 2.1(b), third rejection
Our first submission has now been rejected under Guideline 2.1(b), with the message: "the in-app purchases do not load successfully." Each review was performed on an iPad Air 11-inch (M3) running iPadOS 26.6. The app sells only auto-renewable subscriptions. We cannot reproduce the failure, and we have verified every part of the configuration we can think of. WHAT WE VERIFIED (via the App Store Connect API, not just the UI) Two subscriptions in one group, state READY_TO_SUBMIT Product IDs exactly match what the app requests Available in 175 territories, including the United States Prices set, en-US localizations present for both products and for the group App review screenshots attached to both, state COMPLETE Both subscriptions are included in the review submission (READY_FOR_REVIEW) Paid Apps Agreement: Active. Bank account: Active. Tax forms: Active. WHAT WORKS On our own devices, installed via TestFlight (sandbox environment), the products load correctly and a purchase completes and activates as expected. This works on both a real Apple ID and a Sandbox Tester account. WHAT WE OBSERVED FROM THE REVIEW SESSION We use RevenueCat. Their server-side API returns our offering with both packages and the correct product identifiers, so the offering metadata is fine. Our backend also shows that the reviewer's session reached our servers and signed in successfully at the review timestamp, so the device had working network connectivity. That leaves StoreKit itself returning no products on the reviewer's device, which is what empties the offering. QUESTIONS Are there known conditions under which StoreKit returns no products in the App Review sandbox for subscriptions that are in "Ready to Submit" and are attached to the same submission as the binary? For an app that has never been approved, is product loading during review handled differently from a normal sandbox session on a released app? Is there any way to obtain diagnostics from a review session, or to ask the reviewer for a screenshot of the failing screen? Replies in Resolution Center so far have only repeated the original rejection text. Is there anything specific to iPadOS 26.6 that could affect StoreKit 2 product lookups? For the next submission we have added a timeout and automatic retries around the product lookup, plus a visible retry control instead of a spinner, in case the failure is a transient cold-start timeout. But we would rather understand the actual cause than keep guessing. Any pointers appreciated.
Replies
3
Boosts
1
Views
586
Activity
1w
StoreKit 2: Does Transaction.currentEntitlements get updated when my app isn't running?
TL;DR: Does iOS automatically receive App Store transaction updates in the background when internet connection is available so the backing storage state of Transaction.currentEntitlements gets synced even when my app is not running? Or does iOS update Transaction.currentEntitlements only when my app is running? The long version: Imagine the following situation: A user has purchased a non-consumable IAP in my app and is granted the locked premium content. The IAP transaction is now present in Transaction.currentEntitlements (it's also cached locally). The user blocks internet access every time before my app gets opened (either enables the Airplane mode and/or disconnects from the Wi-Fi before launching my app). So from this point on, my app never gets a chance to connect to the internet. The user gets refunded for the IAP. The user uses their iPhone to browse the internet via Safari, checks emails, etc. Then, before launching my app, the user blocks internet access. My app gets is launched (without internet access) and reads entitlements from Transaction.currentEntitlements. The question is: does the StoreKit service know that the IAP has been refunded? Did iOS update the local cached storage of Transaction.currentEntitlements while the user was connected to the internet in step 4? Or will Transaction.currentEntitlements contain the old state from step 1 so the app won't know about the refund and the user will be able to use my app's premium content which has been refunded by now? Is the behavior the same for auto-renewable subscriptions as it is for non-consumable IAPs?
Replies
1
Boosts
0
Views
628
Activity
1w
Trials entering billing retry instead of converting
We have a monthly subscription and an annual subscription with a 3-day free trial. The monthly converts fine. On the annual, trials tend to enter billing retry rather than convert — users don't cancel, the charge just fails. We've audited our implementation and found nothing on our side that participates in the renewal charge. What can a developer actually do about this? Does trial length, price point, or using a paid introductory offer instead of a free trial make a difference?
Replies
1
Boosts
0
Views
156
Activity
1w
Build behaving differently in testflight compared to simulator
Hi all I have an app I’m pretty much done with, and on the Xcode simulator it works perfectly and the IAP shows us when the purchase buttons are clicked but for some reason when it goes to testflight none of the buttons respond, is there any reason that would cause it to behave differently in testflight when its coded correctly and works in the simulator. thanks
Replies
1
Boosts
0
Views
612
Activity
1w
Is receiving the same transaction multiple times from Transaction.updates expected behavior?
I'm seeing behavior similar to what was reported in this thread: https://developer.apple.com/forums/thread/816344 I read the discussion in the related thread (816320) as well, but I couldn't determine whether receiving the same transaction multiple times from Transaction.updates is considered expected behavior. In my case, I'm testing an auto-renewable subscription in the Sandbox environment. After successfully processing and calling finish() on a transaction, Transaction.updates sometimes provides another transaction with the same transactionId. I've also observed the same transactionId being delivered multiple times through Transaction.updates itself. I compared the JWS representations of these transactions. They are not byte-for-byte identical, but the transaction information appears to be the same. The only differences I've identified are: signedDate deviceVerificationNonce deviceVerification This looks as though the same transaction is being signed again at a different time. I'd like to clarify the intended way to handle this: Is it expected behavior for Transaction.updates to deliver the same transactionId multiple times in this way? If so, after an app has successfully processed and finished a transaction, is it safe to recognize subsequent transactions with the same transactionId as already processed, skip entitlement-related processing, and simply call finish() on them? In other words, can an app use transactionId to prevent duplicate processing of transactions that it has already successfully handled? I'm specifically interested in whether doing so could cause the app to miss any meaningful update that StoreKit might later deliver using the same transactionId.
Replies
3
Boosts
0
Views
838
Activity
1w
App Review sandbox: revenuecat product loads, then STORE_PROBLEM followed by PRODUCT_NOT_AVAILABLE_FOR_PURCHASE on iPadOS 26.6
Hello, I am investigating an intermittent In-App Purchase failure that occurred during App Review for the first release of my app. Environment Review device: iPad Air 11-inch (M3) OS: iPadOS 26.6 Environment: App Review sandbox Product type: Consumable StoreKit integration: RevenueCat through react-native-purchases 10.4.3 Observed behavior StoreKit successfully returned the products, localized names, and prices. The reviewer could see the credit packs and initiate the native purchase flow. My diagnostics show this sequence: Purchase initiated PURCHASE_CANCELLED; no transaction evidence Purchase initiated again RevenueCat code 2: STORE_PROBLEM elapsed: 9.4 seconds no transaction evidence Purchase initiated again RevenueCat code 5: PRODUCT_NOT_AVAILABLE_FOR_PURCHASE no transaction evidence Purchase initiated again RevenueCat code 5: PRODUCT_NOT_AVAILABLE_FOR_PURCHASE elapsed: 0.6 seconds no transaction evidence code-block The relevant sanitized logs are: { "occurredAt": "2026-08-25T12:52:59.733Z", "platform": "ios", "appVersion": "1.0.0", "build": "14", "productId": "HIDDEN_FOR_DISPLAY", "stage": "STORE_CHECKOUT", "providerCode": "2", "providerReadableCode": "STORE_PROBLEM", "transactionEvidence": false, "elapsedMs": 9417 } code-block { "occurredAt": "2026-08-25T12:55:42.752Z", "platform": "ios", "appVersion": "1.0.0", "build": "14", "productId": "HIDDEN_FOR_DISPLAY", "stage": "STORE_CHECKOUT", "providerCode": "5", "providerReadableCode": "PRODUCT_NOT_AVAILABLE_FOR_PURCHASE", "transactionEvidence": false, "elapsedMs": 637 } code-block No App Store transaction was created, and therefore RevenueCat received no transaction or webhook for these attempts. Configuration verified I confirmed that: The affected product and the other consumable products are attached to the App Review submission. Product IDs match between the app, App Store Connect, and RevenueCat. Prices and localizations are configured. The products are available in the relevant storefronts. The Paid Apps Agreement is active. Banking and tax information are active. The In-App Purchase capability is present. The distribution build does not use a local StoreKit configuration file. The same build and affected product completed successfully afterward on a physical device using Apple Sandbox. The native purchase sheet opened, the transaction completed, and the consumable content was delivered successfully in my reproduction. The product metadata clearly remained available because its localized name and price were displayed. However, after the initial STORE_PROBLEM, subsequent purchase requests were rejected almost immediately as PRODUCT_NOT_AVAILABLE_FOR_PURCHASE. I do not have the underlying Apple NSError, such as an ASDServerErrorDomain or AMSErrorDomain value, because it was not exposed in my remote diagnostic record. Questions Can a failed sandbox transaction leave the StoreKit account/session or commerce-catalog state temporarily inconsistent, causing subsequent requests for an otherwise loaded product to return storeProductNotAvailable? Does StoreKit use separate metadata and transaction-eligibility services, allowing product information to load while the same product is rejected during purchase()? Are there known sandbox or StoreKit issues on iPadOS 26.6 that could produce this sequence? Could a stale App Review sandbox account token or storefront session explain the transition from STORE_PROBLEM to PRODUCT_NOT_AVAILABLE_FOR_PURCHASE? Is there any developer-side configuration that could explain this when the same product and binary complete successfully using another sandbox session? What additional logging should I capture from RevenueCat’s React Native SDK to preserve the complete underlying Apple error chain?
Replies
3
Boosts
0
Views
1k
Activity
1w
StoreKit Testing on iOS 27.2 Simulator returns the refunded renewal when repurchasing a subscription
I'm testing auto-renewable subscriptions with a local .storekit configuration in Xcode 27.2 (27B52). With the same app and configuration on iPhone 17 simulators, I get different results on iOS 26.2 (23C54) and iOS 27.2 (24B8117). Set SKTestSession.timeRate to .oneRenewalEveryThirtySeconds, then purchase an auto-renewable subscription in the app with StoreKit 2. Wait for the original period to expire and the first automatic renewal to appear. Refund that renewal using SKTestSession.refundTransaction(identifier:) and wait for the app to receive the revocation. While the app is still running, purchase the same product again and inspect the verified transaction returned directly by Product.purchase(). Both runtimes return .success with a verified transaction. On iOS 26.2, the repurchase returns a new transaction ID with revocationDate == nil, and Transaction.currentEntitlements contains it. On iOS 27.2, the result has the same ID, purchaseDate, and non-nil revocationDate as the refunded renewal. The current entitlement check yields no verified unrevoked transaction. This reproduced for both a monthly and a three-month subscription. The monthly case also reproduced when calling Product.purchase() without an appAccountToken option. Is this a known issue in StoreKit Testing on iOS 27.2 Simulator? Is there a supported way to test the repurchase path while preserving the refunded transaction in the test history?
Replies
0
Boosts
0
Views
78
Activity
1w
Title: StoreKit Sandbox: supportsMultiSeatPurchase is true, but pricingTerms contains no seatBased terms
We’re testing an annual multiseat subscription on a physical iPad. StoreKit returns the expected product and reports supportsMultiSeatPurchase == true, but its pricingTerms contains one term and no seatBased terms. Our app therefore cannot calculate a two-seat quote and stops before attempting a purchase. Environment iPad Air 11-inch (M3) iPadOS 27.3 beta (24C5037i) Xcode 27.3 beta (27C5020n) Development-signed app, version 1.0, diagnostic build 44 Physical-device testing with a US Sandbox purchaser App Store Connect configuration Annual auto-renewable subscription Multiseat purchases allowed Invitations provided by Apple Annual upfront availability enabled for the United States at USD 6.99 Subscription status: Prepare for Submission Sandbox purchases and renewals enabled Steps to reproduce Request the subscription using Product.products(for:). Confirm that the expected annual product is returned. Check supportsMultiSeatPurchase, which returns true. Inspect pricingTerms for supported upfront seatBased terms. Attempt to prepare a quote for two total seats. Actual result Total pricing terms: 1 Seat-based pricing terms: 0 Supported group pricing terms: 0 No purchase is attempted. Production sponsorship sales remain disabled. Expected result A supported upfront seat-based pricing term with Apple-provided pricing tiers that can be used to calculate a two-seat quote. Questions Is additional configuration or account eligibility required for Sandbox to return seat-based pricing terms? Must the subscription progress beyond Prepare for Submission before multiseat pricing can be tested? Can supportsMultiSeatPurchase legitimately return true while no seat-based pricing terms are available? If so, what conditions cause this? Is this a known limitation in this beta, and is there a supported workaround or recommended testing configuration? The issue was reproduced again on November 10, 2026, at approximately 9:57 PM Mountain Time. A sysdiagnose captured at 10:03:11 PM Mountain Time was attached privately to FB25451377. DTS directed us to post here under Case-ID: 23369152. We can provide a focused reproduction project if needed.
Replies
0
Boosts
0
Views
88
Activity
1w
StoreKit 2 returns no products for a non-renewing subscription in TestFlight Sandbox (China mainland)
I’m testing the first in-app purchase for an iOS app. It is a non-renewing subscription that grants 12 months of access. On November 9, a physical iPhone running our TestFlight build reproduced the same issue twice in the China mainland Sandbox storefront. Setup checked at the time The annual product was Ready to Submit in App Store Connect, with China mainland availability, a CNY 98 price, and a Simplified Chinese localization. The annual product identifier matched the identifier requested by the app. The explicit Bundle ID matched App Store Connect and had In-App Purchase enabled. The Paid Apps Agreement was active, and banking and tax records were in place. We used a mainland-China Sandbox tester and called the native StoreKit 2 Product.products(for:) API. The request included the configured annual product and an old monthly identifier that has no corresponding product in App Store Connect. Steps and results Install the app from TestFlight on a physical iPhone and open the purchase screen in Sandbox. Refresh the available products. We expect the annual product and its localized price to appear. Product.products(for:) completes with an empty array. Device logs show an HTTP 200 response from the China mainland Sandbox catalog followed by Ignoring empty product response. After the 600-second cache lifetime, the query received a different server correlation key and still returned no products. This occurs during product lookup, before any purchase call. TN3186 says that Sandbox testing can take place before submission for review. Has anyone reproduced this specifically with a non-renewing subscription? Is there another way to verify Sandbox catalog visibility for the configured annual product or diagnose why it is omitted? An annual-only StoreKit query would be a useful follow-up test. We can share the exact app and product identifiers, request correlation keys, and device diagnostics with Apple through Feedback Assistant.
Replies
0
Boosts
0
Views
40
Activity
1w
Question About StoreKit Request Rate Limits and Capacity
Hello, We are looking for information about the capacity limits for requests sent directly to the App Store through the StoreKit SDK when clients make in-app purchases. In our expected usage, we anticipate a peak request volume of approximately 30 transactions per second (TPS) through this communication path. Does anyone know if Apple imposes any rate limits or maximum request processing limits on requests sent directly to the App Store via the StoreKit SDK? If such limits exist, it would be helpful if you could share any details about the applicable thresholds. Thank you!
Replies
0
Boosts
0
Views
86
Activity
1w
StoreKit 2 – AppStore.sync() fails with StoreKitError.unknown (code 2) in TestFlight**
Subject: StoreKit 2 – AppStore.sync() fails with StoreKitError.unknown (code 2) in TestFlight Hello Apple Developer forum We are investigating a reproducible issue with StoreKit 2's AppStore.sync() in our iOS application, Elins Nystan. Environment App: Elins Nystan Bundle Identifier: poworg.ElinsNystan-2 TestFlight version: 1.43 (build 8) Device: iPhone 16 Date: November 10, 2026 Environment: TestFlight / App Store sandbox StoreKit: StoreKit 2 Problem The app correctly recognizes an existing subscription and grants Premium access to the account associated with the original purchase. Premium remains active after restarting the application, and subscription-dependent functionality works correctly. However, when the user selects “Restore Purchases,” the app calls AppStore.sync(). An Apple account authentication dialog appears and the user enters their password. After approximately 26 seconds, AppStore.sync() throws an error. Captured device logs All timestamps below are UTC: 2026-11-10 21:33:10 — restore.started 2026-11-10 21:33:10 — restore.syncStarted 2026-11-10 21:33:36 — restore.syncFailed Error details: Domain: StoreKit.StoreKitError Code: 2 Classification: unknownThe three log events share the same operation identifier. The app reports that Restore could not be completed due to an unknown error. Additional observations Premium was active before Restore. Previous testing confirmed that Premium remained active after a failed Restore. No corresponding backend reconciliation request was observed during an earlier Restore failure. No confirmed application-side cancellation or overlapping Restore request has been identified. AppStore.sync() has been part of the Restore implementation since December 2025. We have not identified a source-code regression that explains the StoreKit error. We have not verified a previously successful Restore under equivalent TestFlight conditions. We are not attempting to change subscription ownership or bypass purchase verification. Questions What conditions can cause AppStore.sync() to throw StoreKitError.unknown (code 2) in TestFlight? Could this be related to the sandbox Apple Account, authentication, or an existing subscription with multiple renewal transactions? Are there additional StoreKit or system diagnostics that would help identify the underlying cause? Is there a recommended way to recover from this error while preserving the existing verified subscription entitlement? Is this a known TestFlight/sandbox issue, or should we investigate a specific application configuration? We can provide redacted device logs and additional technical details if required. Thank you for your assistance.
Replies
0
Boosts
0
Views
57
Activity
1w
First iOS App Stuck in Waiting for Review for Over 30 Days –– No Support Response
Hello Apple App Review Team, My first iOS app, Loopa – Video & Audio Editor (version 1.0.0), has been stuck in "Waiting for Review" for approximately 30 days. I have already contacted Apple Developer Support through the official contact form but have not received a response. Could an Apple representative please investigate whether my submission is progressing normally or whether additional information is required? I would appreciate any assistance. Thank you.
Replies
0
Boosts
0
Views
36
Activity
1w