StoreKit

RSS for tag

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

Posts under StoreKit tag

200 Posts

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 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
455
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
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
304
1d
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
25
1d
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
415
2d
SKPaymentQueue.default().storefront?.countryCode returns "USA" only in TestFlight
Hi everyone, I'm encountering an issue where the storefront country code returns "USA" unexpectedly in TestFlight builds, and I'd appreciate any insights from the community. Issue Description When executing SKPaymentQueue.default().storefront?.countryCode in our TestFlight builds, the property returns USA. However, we expect it to return JPN because both the Sandbox test user account and the Apple Account region configured on the device are set to Japan. Behavior Across Environments Xcode Debug & Ad Hoc Builds: Returns JPN as expected. TestFlight Builds: Returns USA unexpectedly. Related Threads I've noticed several threads reporting similar issues without a clear resolution: https://developer.apple.com/forums/thread/660817 https://developer.apple.com/forums/thread/794932 https://developer.apple.com/forums/thread/800078 https://developer.apple.com/forums/thread/814178 https://developer.apple.com/forums/thread/810860 Questions Is this USA value a known TestFlight/Sandbox-specific limitation or bug? Will production users in Japan correctly receive JPN (and see JPY prices) once the app is approved and published on the App Store? Is there any workaround or project configuration fix required on our side prior to App Store submission? Has anyone experienced this recently or confirmed the behavior in the production environment after release? Thanks!
3
1
667
2d
WKWebView IAP message handler works in Simulator but not TestFlight
Hi, I’m having an issue with an in-app purchase implementation using StoreKit and a WKWebView. The app uses a WKWebView with a WKScriptMessageHandler registered with the name "iap" to communicate between JavaScript and the native Swift code. The implementation works correctly when running the app through Xcode Simulator. The IAP buttons trigger the expected native code and the bridge functions correctly. However, when I install the same/latest build through TestFlight, the IAP functionality does not work as expected. The buttons/JavaScript-to-native communication do not appear to trigger the same way they do in the Simulator. The IAP products and configuration have been set up in App Store Connect. I have already checked the implementation and confirmed that the same code works when running from Xcode. Could there be any difference between Simulator and TestFlight regarding: StoreKit sandbox/TestFlight behaviour Entitlements or signing App Store Connect configuration WKWebView/WKScriptMessageHandler behaviour JavaScript-to-native communication in a TestFlight build Any required configuration for IAP testing through TestFlight I would appreciate any guidance on what I should check to determine why the "iap" WKScriptMessageHandler works in Simulator but not in TestFlight. Thanks.
1
0
499
2d
Same issue: subscription group stuck on "must be submitted with a subscription of the same group" despite correct config
I'm having the exact same issue. My app has 2 subscription groups, each with 2 auto-renewable subscriptions (monthly and yearly duration) — 4 products total, all in "Ready to Submit" status. The error I keep getting when trying to submit the first group together with the app version is: "New subscription groups must be submitted with an auto-renewable subscription of that same group" What I've already verified/tried: Full metadata on each subscription: reference name, pricing, localizations (display name + description) in two languages, review screenshot Added the individual subscription products (not the group) to the submission draft from each product's own page Draft correctly shows the app version + all subscriptions grouped together under "Suscripciones (4)" Set both durations (monthly/annual) to the same subscription level within each group, as suggested in another thread — no change Recreated the subscriptions from scratch with entirely new Product IDs — same error Tried different browsers, incognito mode, hard refresh Paid Applications Agreement is Active, no pending agreements The error persists regardless of what I try. Has anyone found what actually resolved this beyond the subscription level fix? Or is this something only Apple can unblock from their side?
2
0
527
2d
Japan-only External Purchase Link entitlement requires EU tax forms (Alternative Terms Addendum) and blocks submission
We are a Japan-based developer. We were approved for the StoreKit External Purchase Link entitlement for Japan only (com.apple.developer.storekit.custom-purchase-link.allowed-regions = jp). After we enabled "StoreKit External Purchases or Offers" on our App ID, App Store Connect started showing missing tax information for every EU country (agreement type: Alternative Terms Addendum). Any build that includes the entitlement now fails with "Unable to Add for Review – You must provide tax information." Builds without the entitlement submit normally. The EU tax forms ask only for an EU VAT ID. We are a Japanese company and do not have one. We do not use external purchases in the EU, and we have removed all EU countries from the app's distribution. The error remains. We have also set the payee information for the EU. Nothing changed. Questions: Is an EU VAT ID required to use the external purchase entitlement in Japan only? If not, how can we clear the EU tax requirement, or limit the addendum to Japan? We have contacted Developer Support and the Finance team, but the issue is still unresolved. We can share case numbers if needed.
2
0
64
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
2d
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
81
3d
Multiseat Subscriptions: Pricing Flexibility and Enterprise Implementation
I have questions about pricing flexibility and technical implementation. In WWDC26 Session 391, you introduced up to five volume pricing bands that allow developers to offer lower per-seat subscription prices as organizations purchase more seats. For example: 1–20 seats: $39.99/month per seat 21–40 seats: $29.99/month per seat 41+ seats: $19.99/month per seat Volume purchasing and volume discounting provide different benefits. Volume purchasing makes it easier for organizations to buy, deploy, and manage subscriptions. This is valuable independently of discounts. Consider a productivity application deployed to 10,000 employees. Unlike AI services that charge separately for tokens or usage credits, an application offering unlimited, unmetered usage receives no additional revenue beyond its subscription fees. Supporting 10,000 deployments also introduces ongoing responsibilities. Major updates, new capabilities, and performance improvements may require additional testing, deployment coordination, compatibility checks, and technical support. Enterprise customers often have greater requirements for reliability, timely updates, and deployment management. Reducing the fixed subscription price per seat does not reduce these responsibilities or account for the additional value delivered across an organization. My questions for the StoreKit team: Business pricing: Can developers create a separate business subscription with a higher base price than their consumer offering, such as $39.99/month for individuals and $59.99/month per business seat, with independent volume pricing bands? Business-only distribution: Can this subscription be offered exclusively through Apple Business while maintaining the existing consumer subscription? Business features in the same app: Can StoreKit 2 identify whether a user has an individual subscription or an organization-assigned seat, allowing developers to unlock additional business capabilities within the same app binary? Onboarding and deployment: What is the recommended approach for adapting onboarding, subscription unlocking, and access management for organization-assigned users? Are there specific considerations for MDM deployment and managed app configurations? Implementation resources: Are there technical documentation or sample projects covering multiseat purchases, entitlement verification, seat reassignment, subscription changes, and ongoing management after release? The primary opportunity is simplifying organizational purchasing and deployment, while allowing developers to deliver additional business value and price subscriptions according to the ongoing requirements of supporting organizations at scale—not simply discounting additional seats. I’d appreciate clarification on the recommended pricing configuration and StoreKit 2 implementation. Thank you. REF: October 22 Announcement — Offer your subscriptions to businesses and schools
1
0
164
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
520
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
137
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
Padel Tempo iOS 1.0 — Waiting for Review nearly 5 days after metadata-only resubmission
Hello App Review team and fellow developers, Our Padel Tempo: Padel Score iOS 1.0 submission has been in Waiting for Review for nearly five days after a metadata-only resubmission, and I would like to make sure that nothing else is required from our side. App: Padel Tempo: Padel ScoreVersion: iOS 1.0Submission ID: cbc83032-2f7a-4f80-bc2c-e54a5c9f68b3Resubmitted: October 26, 2026 at 5:04 PMCurrent status: Waiting for Review What happened Our initial submission was reviewed on October 26. We received an automated App Review message regarding the auto-renewable subscriptions Premium Monthly and Premium Yearly. The only issue identified was a missing functional link to the standard Apple Terms of Use (EULA) in the App Store metadata. We corrected the issue immediately: added the standard Apple Terms of Use (EULA) link to the App Description; made sure the required metadata was complete; no binary changes were necessary; resubmitted the same app version approximately 12 minutes after receiving the review message. Since then, the submission has remained in Waiting for Review. Why I am posting I understand that review times can vary, and I am not asking to skip the queue. I would simply like to confirm that: the resubmission is correctly queued for App Review; the previous metadata issue is considered resolved; no additional action or information is currently required from us. Since this was a metadata-only correction following an already completed first review, I wanted to make sure the resubmission did not end up waiting because of something we may have missed. If App Review needs any additional information, screenshots, test instructions, or clarification, I can provide it immediately. Thank you for your time, and I would also appreciate hearing from other developers who have recently experienced longer-than-usual Waiting for Review times. Best regards,MykolaPadel Tempo
2
0
275
3d
StoreKit AppTransaction — Server-side paid-app refund and revocation verification
Hello Apple Developer Community, I am preparing the first App Store release of an upfront paid iOS application using StoreKit 2 and backend verification of signed AppTransaction data. The application does not use In-App Purchases or subscriptions. Apple documents AppTransaction.revocationDate for detecting revocation of an app purchase on the device. However, I have not found an equivalent documented revocation field in JWSAppTransactionDecodedPayload or an authoritative server-side mechanism for detecting refunds of the paid application itself. My main question is: What is Apple's officially supported approach for a backend server to independently detect and enforce refunds or revocations of an upfront paid iOS application, without relying on client cooperation? Specifically: Is paid-app revocation information available through any server-verifiable Apple-signed field or App Store Server API endpoint? If AppTransaction.revocationDate is available only through StoreKit on the device, is there an equivalent server-verifiable signal? Do App Store Server Notifications support refunds of upfront paid applications, or only In-App Purchases? Since appTransactionId remains unchanged after refund and repurchase, how should a backend distinguish a legitimate repurchase from previously captured signed acquisition evidence? My concern is that previously issued signed acquisition evidence may remain cryptographically valid after a refund, allowing new protected backend sessions unless an authoritative entitlement-status check is available. I want to ensure that refunded acquisitions cannot regain unauthorized access, while legitimate repurchases can restore access correctly. Any official Apple documentation or recommended implementation approach would be greatly appreciated. Thank you!
1
1
103
4d
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
205
4d
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
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 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
455
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
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
304
Activity
1d
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
25
Activity
1d
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
415
Activity
2d
SKPaymentQueue.default().storefront?.countryCode returns "USA" only in TestFlight
Hi everyone, I'm encountering an issue where the storefront country code returns "USA" unexpectedly in TestFlight builds, and I'd appreciate any insights from the community. Issue Description When executing SKPaymentQueue.default().storefront?.countryCode in our TestFlight builds, the property returns USA. However, we expect it to return JPN because both the Sandbox test user account and the Apple Account region configured on the device are set to Japan. Behavior Across Environments Xcode Debug & Ad Hoc Builds: Returns JPN as expected. TestFlight Builds: Returns USA unexpectedly. Related Threads I've noticed several threads reporting similar issues without a clear resolution: https://developer.apple.com/forums/thread/660817 https://developer.apple.com/forums/thread/794932 https://developer.apple.com/forums/thread/800078 https://developer.apple.com/forums/thread/814178 https://developer.apple.com/forums/thread/810860 Questions Is this USA value a known TestFlight/Sandbox-specific limitation or bug? Will production users in Japan correctly receive JPN (and see JPY prices) once the app is approved and published on the App Store? Is there any workaround or project configuration fix required on our side prior to App Store submission? Has anyone experienced this recently or confirmed the behavior in the production environment after release? Thanks!
Replies
3
Boosts
1
Views
667
Activity
2d
WKWebView IAP message handler works in Simulator but not TestFlight
Hi, I’m having an issue with an in-app purchase implementation using StoreKit and a WKWebView. The app uses a WKWebView with a WKScriptMessageHandler registered with the name "iap" to communicate between JavaScript and the native Swift code. The implementation works correctly when running the app through Xcode Simulator. The IAP buttons trigger the expected native code and the bridge functions correctly. However, when I install the same/latest build through TestFlight, the IAP functionality does not work as expected. The buttons/JavaScript-to-native communication do not appear to trigger the same way they do in the Simulator. The IAP products and configuration have been set up in App Store Connect. I have already checked the implementation and confirmed that the same code works when running from Xcode. Could there be any difference between Simulator and TestFlight regarding: StoreKit sandbox/TestFlight behaviour Entitlements or signing App Store Connect configuration WKWebView/WKScriptMessageHandler behaviour JavaScript-to-native communication in a TestFlight build Any required configuration for IAP testing through TestFlight I would appreciate any guidance on what I should check to determine why the "iap" WKScriptMessageHandler works in Simulator but not in TestFlight. Thanks.
Replies
1
Boosts
0
Views
499
Activity
2d
Same issue: subscription group stuck on "must be submitted with a subscription of the same group" despite correct config
I'm having the exact same issue. My app has 2 subscription groups, each with 2 auto-renewable subscriptions (monthly and yearly duration) — 4 products total, all in "Ready to Submit" status. The error I keep getting when trying to submit the first group together with the app version is: "New subscription groups must be submitted with an auto-renewable subscription of that same group" What I've already verified/tried: Full metadata on each subscription: reference name, pricing, localizations (display name + description) in two languages, review screenshot Added the individual subscription products (not the group) to the submission draft from each product's own page Draft correctly shows the app version + all subscriptions grouped together under "Suscripciones (4)" Set both durations (monthly/annual) to the same subscription level within each group, as suggested in another thread — no change Recreated the subscriptions from scratch with entirely new Product IDs — same error Tried different browsers, incognito mode, hard refresh Paid Applications Agreement is Active, no pending agreements The error persists regardless of what I try. Has anyone found what actually resolved this beyond the subscription level fix? Or is this something only Apple can unblock from their side?
Replies
2
Boosts
0
Views
527
Activity
2d
Japan-only External Purchase Link entitlement requires EU tax forms (Alternative Terms Addendum) and blocks submission
We are a Japan-based developer. We were approved for the StoreKit External Purchase Link entitlement for Japan only (com.apple.developer.storekit.custom-purchase-link.allowed-regions = jp). After we enabled "StoreKit External Purchases or Offers" on our App ID, App Store Connect started showing missing tax information for every EU country (agreement type: Alternative Terms Addendum). Any build that includes the entitlement now fails with "Unable to Add for Review – You must provide tax information." Builds without the entitlement submit normally. The EU tax forms ask only for an EU VAT ID. We are a Japanese company and do not have one. We do not use external purchases in the EU, and we have removed all EU countries from the app's distribution. The error remains. We have also set the payee information for the EU. Nothing changed. Questions: Is an EU VAT ID required to use the external purchase entitlement in Japan only? If not, how can we clear the EU tax requirement, or limit the addendum to Japan? We have contacted Developer Support and the Finance team, but the issue is still unresolved. We can share case numbers if needed.
Replies
2
Boosts
0
Views
64
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
2d
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
81
Activity
3d
Multiseat Subscriptions: Pricing Flexibility and Enterprise Implementation
I have questions about pricing flexibility and technical implementation. In WWDC26 Session 391, you introduced up to five volume pricing bands that allow developers to offer lower per-seat subscription prices as organizations purchase more seats. For example: 1–20 seats: $39.99/month per seat 21–40 seats: $29.99/month per seat 41+ seats: $19.99/month per seat Volume purchasing and volume discounting provide different benefits. Volume purchasing makes it easier for organizations to buy, deploy, and manage subscriptions. This is valuable independently of discounts. Consider a productivity application deployed to 10,000 employees. Unlike AI services that charge separately for tokens or usage credits, an application offering unlimited, unmetered usage receives no additional revenue beyond its subscription fees. Supporting 10,000 deployments also introduces ongoing responsibilities. Major updates, new capabilities, and performance improvements may require additional testing, deployment coordination, compatibility checks, and technical support. Enterprise customers often have greater requirements for reliability, timely updates, and deployment management. Reducing the fixed subscription price per seat does not reduce these responsibilities or account for the additional value delivered across an organization. My questions for the StoreKit team: Business pricing: Can developers create a separate business subscription with a higher base price than their consumer offering, such as $39.99/month for individuals and $59.99/month per business seat, with independent volume pricing bands? Business-only distribution: Can this subscription be offered exclusively through Apple Business while maintaining the existing consumer subscription? Business features in the same app: Can StoreKit 2 identify whether a user has an individual subscription or an organization-assigned seat, allowing developers to unlock additional business capabilities within the same app binary? Onboarding and deployment: What is the recommended approach for adapting onboarding, subscription unlocking, and access management for organization-assigned users? Are there specific considerations for MDM deployment and managed app configurations? Implementation resources: Are there technical documentation or sample projects covering multiseat purchases, entitlement verification, seat reassignment, subscription changes, and ongoing management after release? The primary opportunity is simplifying organizational purchasing and deployment, while allowing developers to deliver additional business value and price subscriptions according to the ongoing requirements of supporting organizations at scale—not simply discounting additional seats. I’d appreciate clarification on the recommended pricing configuration and StoreKit 2 implementation. Thank you. REF: October 22 Announcement — Offer your subscriptions to businesses and schools
Replies
1
Boosts
0
Views
164
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
520
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
137
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
Padel Tempo iOS 1.0 — Waiting for Review nearly 5 days after metadata-only resubmission
Hello App Review team and fellow developers, Our Padel Tempo: Padel Score iOS 1.0 submission has been in Waiting for Review for nearly five days after a metadata-only resubmission, and I would like to make sure that nothing else is required from our side. App: Padel Tempo: Padel ScoreVersion: iOS 1.0Submission ID: cbc83032-2f7a-4f80-bc2c-e54a5c9f68b3Resubmitted: October 26, 2026 at 5:04 PMCurrent status: Waiting for Review What happened Our initial submission was reviewed on October 26. We received an automated App Review message regarding the auto-renewable subscriptions Premium Monthly and Premium Yearly. The only issue identified was a missing functional link to the standard Apple Terms of Use (EULA) in the App Store metadata. We corrected the issue immediately: added the standard Apple Terms of Use (EULA) link to the App Description; made sure the required metadata was complete; no binary changes were necessary; resubmitted the same app version approximately 12 minutes after receiving the review message. Since then, the submission has remained in Waiting for Review. Why I am posting I understand that review times can vary, and I am not asking to skip the queue. I would simply like to confirm that: the resubmission is correctly queued for App Review; the previous metadata issue is considered resolved; no additional action or information is currently required from us. Since this was a metadata-only correction following an already completed first review, I wanted to make sure the resubmission did not end up waiting because of something we may have missed. If App Review needs any additional information, screenshots, test instructions, or clarification, I can provide it immediately. Thank you for your time, and I would also appreciate hearing from other developers who have recently experienced longer-than-usual Waiting for Review times. Best regards,MykolaPadel Tempo
Replies
2
Boosts
0
Views
275
Activity
3d
StoreKit AppTransaction — Server-side paid-app refund and revocation verification
Hello Apple Developer Community, I am preparing the first App Store release of an upfront paid iOS application using StoreKit 2 and backend verification of signed AppTransaction data. The application does not use In-App Purchases or subscriptions. Apple documents AppTransaction.revocationDate for detecting revocation of an app purchase on the device. However, I have not found an equivalent documented revocation field in JWSAppTransactionDecodedPayload or an authoritative server-side mechanism for detecting refunds of the paid application itself. My main question is: What is Apple's officially supported approach for a backend server to independently detect and enforce refunds or revocations of an upfront paid iOS application, without relying on client cooperation? Specifically: Is paid-app revocation information available through any server-verifiable Apple-signed field or App Store Server API endpoint? If AppTransaction.revocationDate is available only through StoreKit on the device, is there an equivalent server-verifiable signal? Do App Store Server Notifications support refunds of upfront paid applications, or only In-App Purchases? Since appTransactionId remains unchanged after refund and repurchase, how should a backend distinguish a legitimate repurchase from previously captured signed acquisition evidence? My concern is that previously issued signed acquisition evidence may remain cryptographically valid after a refund, allowing new protected backend sessions unless an authoritative entitlement-status check is available. I want to ensure that refunded acquisitions cannot regain unauthorized access, while legitimate repurchases can restore access correctly. Any official Apple documentation or recommended implementation approach would be greatly appreciated. Thank you!
Replies
1
Boosts
1
Views
103
Activity
4d
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
205
Activity
4d
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