In-App Purchase

RSS for tag

Offer extra content, digital goods, and features directly within your app using in-app purchases.

Posts under In-App Purchase tag

200 Posts

Post

Replies

Boosts

Views

Activity

Locate the In-App Purchases and Subscriptions Section in App Store Connect
App Store Connect displays the In-App Purchases and Subscriptions section on your app's version page when your app has an In-App Purchase or subscription with a Ready to Submit status. To locate the In-App Purchases and Subscriptions section: In Apps, select the app you want to view. In the sidebar, select the app version. On the version page, scroll down to the In-App Purchases and Subscriptions section. For more information, see Submit an In-App Purchase.
0
0
3.1k
Jun ’26
In-App Purchase Resources
General: Forums topic: StoreKit Forums tag: In-App Purchase App Store Pathway Simple and safe In-App Purchases Auto-renewable subscriptions In-App Purchase documentation Getting started with In-App Purchase using StoreKit views documentation Supporting business model changes by using the app transaction documentation Testing at all stages of development with Xcode and the sandbox documentation App Store Server Notifications documentation App Store Server API documentation Simplifying your implementation by using the App Store Server Library documentation TN3185: Troubleshooting In-App Purchases availability in Xcode technote TN3186: Troubleshooting In-App Purchases availability in the sandbox technote TN3188: Troubleshooting In-App Purchases availability in the App Store technote Understanding StoreKit workflows sample code Implementing a store in your app using the StoreKit API sample code What’s new in StoreKit and In-App Purchase video
0
0
2.3k
Jun ’26
StoreKit 2 returns USA storefront and USD price in TestFlight despite Japanese Apple Account
Hello, I'm developing an iOS app that uses StoreKit 2 for an auto-renewable subscription. I'm experiencing an issue where StoreKit returns the US storefront and USD pricing in TestFlight, even though the device's Apple Account and Sandbox Apple Account are configured for Japan. Environment App: YonsanmaruTimer (430タイマー) App version: 1.2.0 (TestFlight build 4) Bundle ID: com.manyouen.YonsanmaruTimer Product ID: com.manyouen.YonsanmaruTimer.plusassist.monthly StoreKit 2 Xcode Archive configuration: Release App Store Connect configuration The subscription is configured with the following prices: Japan: ¥200/month, with a one-month free trial United States: $0.99/month The app is intended for distribution in Japan. Observed behavior When fetching the subscription product using Product.products(for:), I log the current storefront and product price. The result is: Storefront: USA Price: $0.99 Currency: USDAs a result, the subscription price displayed in the app using product.displayPrice is $0.99 instead of ¥200. What I have already checked The device's Apple Account country/region for Media & Purchases is Japan. TestFlight is installed using my regular Japanese Apple Account. I created a new Sandbox Apple Account with Japan as its country/region and signed in through Settings → Developer → Sandbox Apple Account. The storefront still returns USA after restarting the TestFlight app. The app is archived using the Release build configuration. In an earlier subscription purchase test, Apple's native purchase confirmation sheet displayed ¥200, even though the app's product display price was $0.99. Questions Why would Storefront.current return USA in TestFlight under these conditions? Is this expected behavior in the TestFlight sandbox environment? Could this behavior also occur after the app is released on the App Store? Is there any additional account, device, or App Store Connect configuration I should check? I would like to ensure that the subscription price displayed in my app matches the price shown in Apple's purchase confirmation sheet before submitting the app for review. Any guidance would be greatly appreciated. Thank you.
0
0
77
12h
Sandbox IAP: AuthKit succeeds, then AMSServerErrorDomain -5000 (cancel-purchase-batch)
Every sandbox purchase of our auto-renewable subscriptions cancels right after AuthKit sign-in succeeds. It's blocking our 1.0 release. Filed as FB25469063, no reply yet. Capacitor iOS app, bundle io.xrplive.app, 1.0.0 (TestFlight), products io.xrplive.app.pro.monthly / .yearly, iPhone 17 Pro Max on iOS 27.0.1, StoreKit via @capgo/native-purchases. Console on every attempt: (1) AMSAuthKitUpdateTask: "The AuthKit authentication succeeded." (2) Then: Error Domain=AMSServerErrorDomain Code=-5000 UserInfo={failureType=-5000, m-allowed=false, cancel-purchase-batch=true, customerMessage=Check the account information you entered and try again.} Also AMSErrorDomain Code=100 (Authentication Failed), Code=2 ("Password reuse not available for account"), and a 401 from sandbox.itunes.apple.com/commerce/messages/app/inbox. We already fixed a purchase(confirmIn:) presentation issue. This failure is in sandbox verification after a successful sign-in, which we can't fix from the client. Is -5000 with cancel-purchase-batch a known sandbox account or commerce issue? Is there a sandbox tester or storefront state that fixes it when AuthKit succeeds but verification still fails?
1
0
67
12h
Two Apps Facing Review Issues – No Response from Apple. Could There Be an Issue with My Developer Account
Hello everyone, I'm an independent developer, and I'm currently experiencing review issues with two different apps under the same Apple Developer account. I'm starting to worry that there may be something wrong with my account or the review process. App 1 – Rejected Due to an Account Restriction Mistaken for a Bug My first app was rejected because the reviewer couldn't complete an in-app purchase. However, this wasn't a technical bug. My app has an intentional rule that prevents one Apple ID subscription from being linked to multiple app accounts. The sandbox Apple ID used during review had already been linked to another test account, which triggered this restriction. To make testing easier, I updated our server to remove this restriction for sandbox subscriptions while keeping it unchanged for real users. I explained everything to Apple on November 17 and requested another review. I also requested a phone call on November 18 and submitted an appeal. Unfortunately, I have received no response to any of these requests. App 2 – Rejected and Resubmitted, Still Waiting for Review My second app was also rejected because the reviewer reported that nothing happened after completing an in-app purchase. I resubmitted the app for review on November 19, but it is still waiting for review, and I haven't received any further feedback. My Main Concern Both apps are under the same developer account, and I'm having difficulty getting responses or moving the review process forward. I understand that reviews can take time, but I've already taken steps to address the issues and tried contacting Apple through multiple channels. I'm now concerned that there might be an issue with my developer account affecting the review process. Has anyone experienced similar problems with multiple apps under the same developer account? Is there any way to ask Apple to check whether my account has any review-related restrictions or unusual status? And when App Review messages, appeals, and phone call requests go unanswered, what is the best way to escalate the situation? I would really appreciate any advice from developers who have experienced something similar. Thank you!
1
0
145
15h
App Rejected Due to an Account Restriction, Not a Bug – No Response from Apple After Fixing the Issue
Hello everyone, I'm an independent developer, and I'm currently stuck in the App Review process. I'm hoping someone who has experienced something similar can offer some advice. My app was rejected because the reviewer encountered an error message when attempting to make an in-app purchase. However, this was not a technical bug or a StoreKit issue. It was an intentional account protection rule in my app. Here's what happened: My app has a rule that one Apple ID subscription can only be linked to one app account at a time. This prevents other accounts from taking over someone's paid subscription or sharing a single subscription across multiple accounts. During Apple's review, the sandbox Apple ID used by the reviewer had apparently already been linked to another test account. When the reviewer attempted to purchase a subscription using a different account, the app correctly triggered this restriction. Apple interpreted this behavior as a purchase failure and rejected the app. What I've done to resolve it: Although this rule is intentional and designed to protect users, I wanted to make the review process as easy as possible. I updated our server to remove this restriction specifically for sandbox subscriptions. Reviewers can now complete purchases and restore subscriptions even if their sandbox Apple ID was previously linked to another test account. The restriction remains unchanged for real production subscriptions. On November 17, I explained the situation to the App Review team and informed them that the sandbox issue had already been resolved. I asked them to test the purchase flow again. On November 18, I also requested a phone call to clarify the situation. The problem is that nobody has responded. I have not received any acknowledgment of my explanation, no response to my request for another review, and no phone call. I have also tried contacting Apple through the appeal process, but I still haven't received a response. At this point, I don't know what else I can do. The issue encountered during review has already been addressed, and no new app binary is required because the change was made entirely on our server. Has anyone experienced a similar situation where an app was rejected because an intentional business rule was mistaken for a bug? How did you get the App Review team to respond after explaining and resolving the issue? Is there any effective way to escalate this situation when both review messages and appeal requests go unanswered? submission ID 78b8dd94-fd4c-4951-959b-4fdb57a659d7 I would really appreciate any advice. Thank you!
0
0
106
1d
No MAS receipt after exit(173)
App receipt generation is broken (again). I'm getting the message my app is "damaged" on macOS Monterey 12.3.1 with Xcode 13.3.1 when no receipt is delivered after the app quits with exit(173) and I'm prompted for Mac App Store credentials. I tried App Store log out / log in (sandbox and regular account), cleaning derived data as well as reboot to no avail. Being aware of several old postings (and new comments), I decided to start a new thread to increase visibility ... and also filed a bug report FB10014055. Please consider a duplicate report if you're affected to raise Apple's awareness (all system status are reported as "green")...
12
1
4.4k
1d
StoreKit says purchase succeeded but didn't, AppStore.sync() throws error Unable to Complete Request
One user of my app reached out reporting an interesting in-app purchase issue. Has anyone encountered this or have an idea what's going on here? Proceed to purchase the non-consumable IAP in the app downloaded from the App Store iOS shows the price sheet as expected Confirm with the side button iOS shows an alert "You've already purchased this. Would you like to get it again for free?" Tap OK iOS shows an alert "You're all set. Your purchase was successful." Tap OK The app's content remains locked Tap Restore Purchases iOS shows an alert to sign (with the same account shown in step 2) Input the password and tap OK iOS shows an alert "Unable to Complete Request" (which is the error.localizedDescription thrown from AppStore.sync())
4
0
456
1d
All auto-renewable subscriptions returning expirationIntent = 5 after resolving an agreement issue (StoreKit 1 and StoreKit 2)
Hello, We are currently seeing errors when validating receipts for every auto-renewable subscription purchased through both StoreKit 1 and StoreKit 2. Details below. Case 1 — StoreKit 1 Calling https://buy.itunes.apple.com/verifyReceipt with the subscription receipt returns: "status": 21006, "expiration_intent": "5" Case 2 — StoreKit 2 Calling https://api.storekit.itunes.apple.com/inApps/v1/subscriptions and reading the most recent transaction (LastTransactionsItem) returns status 3. Within JWSRenewalInfoDecodedPayload: autoRenewStatus = 1, expirationIntent = 5 Timeline We believe renewals stopped processing for essentially all auto-renewing subscribers of our app as of 2026-09-18 09:30 KST (UTC+9). After resolving an agreement/licensing issue on our side, new purchases and some receipt validations recovered as of 2026-09-21 11:49 KST. However, most existing receipts still return expirationIntent = 5 when we query receipt validation or subscription status. Questions Is any action required on our side — a server-side change, a configuration change in App Store Connect, or a further review of our agreements? Now that the agreement issue is resolved, when are the renewals that were left pending during the outage expected to be processed? Any guidance would be appreciated. Thank you.
1
0
305
1d
Refund requests in the testing environment are never approved, only DECLINE resolves (consumables, non-renewing subscription) – FB25652374
We are testing refunds for consumables and a non-renewing subscription, installed from TestFlight (tester's own Apple Account, storefront VNM, iPhone 15, iOS 27.0.1), with App Store Server Notifications V2 on the sandbox URL. "Testing refund requests" says: "select any refund reason on the refund request sheet, and submit the sheet. The App Store automatically approves the refund request in the testing environment." What we see: DECLINE resolves every time, about 8 minutes after the CONSUMPTION_REQUEST: REFUND_DECLINED arrives whether our server answers refundPreference: DECLINE or the tester types DECLINE under Issue > Other. Nothing else resolves, for up to 43 hours so far (11 requests): no REFUND notification, no revocationDate in Get Transaction Info, empty Get Refund History. This covers: a listed reason with our server answering without refundPreference, answering GRANT_FULL (Send Consumption Information V2, inside the 5-minute window, 202), or not answering; GRANT_PRORATED and GRANT_FULL typed under Issue > Other. Every CONSUMPTION_REQUEST has consumptionRequestReason UNINTENDED_PURCHASE, even when the tester chose Issue > Other. Questions: Should a refund request in the testing environment be approved when the server answers without a preference, answers GRANT_FULL, or does not answer? Is the GRANT_PRORATED keyword still supported? Does refund testing require a Sandbox Apple Account instead of a TestFlight install? Full details, transaction IDs and decoded notification history are in FB25652374. Thread 743381 looks similar.
0
0
26
2d
StoreKit 2 returns USD product metadata in TestFlight while the storefront is FRA/EUR
Hello, We would appreciate some guidance regarding an unexpected StoreKit currency result in a TestFlight build. Our iPhone language and region are both set to France. The Sandbox tester is also configured for France, and our subscription products have French availability and pricing configured in App Store Connect. In the TestFlight build we diagnosed, StoreKit reports the current storefront as France with EUR: storefront=FRA/143442/EUR However, all 10 subscription products are returned with USD product metadata: products=10/10 formatCurrencies=USD localeCurrencies=USD error=NONE Example: formatCurrency=USD locale=fr_US_currency_USD localeCurrency=USD display=1,99 $US price=1.99 We first observed this through Flutter's in_app_purchase integration. To determine whether the Flutter plugin was involved, we added a native StoreKit 2 diagnostic to the same TestFlight build. The native result was identical: receipt=sandboxReceipt storefront before=FRA/143442/EUR storefront after=FRA/143442/EUR products=10/10 formatCurrencies=USD localeCurrencies=USD error=NONE The issue appears specific to the TestFlight distribution. When the application is installed directly from the development computer, prices are returned in euros on the same device. We also tested with the regular Media & Purchases account signed out and a French Sandbox tester connected. Once the products loaded successfully, StoreKit still returned USD metadata. In another configuration, the application displayed the USD price while Apple's purchase sheet displayed the price in euros. We are using the price and formatting information returned directly by StoreKit. We do not want to infer the currency from the device region or perform a client-side currency conversion, because StoreKit should remain the authoritative source. Could you please help us understand: Is it expected for Storefront.current to report FRA/EUR while Product.priceFormatStyle.currencyCode, its locale currency, and Product.displayPrice use USD? Could a TestFlight or App Store Connect configuration cause product metadata to use a different currency from the current storefront? Is there another account, availability, pricing or distribution setting that we should verify? Is there a recommended way to refresh or invalidate the product metadata used by a TestFlight installation? We have already filed Feedback Assistant report FB24723329, which is currently under investigation. Thank you very much for any clarification or additional diagnostic steps you can suggest.
11
1
1.6k
2d
Introductory Offer Start Timing
Hi everyone, I set up an auto-renewable subscription introductory offer in App Store Connect with a scheduled start date of September 7 for the Philippines storefront. According to the documentation App Store pricing and availability start times by country or region, scheduled pricing and offer updates are expected to go live based on local regional times. However, the offer did not show up in the Current Introductory Offers in app store connect portal at the documented start time (14:00 Sep 6th UTC). Instead, it stayed in the Upcoming Offers until 7:00 Sep 7th UTC which is 17 hours after the time in the doc. We met a similar situation a few days later when we launch another introductory offer in Thailand. I would appreciate clarification on the following points: What is the underlying reason for the discrepancy between the documented start time behavior and the actual start time observed in production? Can Apple update the App Store pricing and availability start times by country or region reference documentation so that it accurately reflects the practical start time and propagation window for each region? Any insights or shared experiences with offer scheduling in the APAC region would be greatly appreciated.
1
0
416
2d
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
500
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
528
2d
When IAPs would be available for Apple Watch?
I need someone from Apple to answer my question. I've added French localization to every of my IAP but I can't submit them due to this warning that sayws "In-app purchases and subscriptions are currently not supported on Apple Watch." The app is watchOS-only. Could you tell me please, when Could you tell me please, when IAPs would be supported?
2
0
259
2d
Apple In-App Purchase availability.
Hello, I am a developer based in Somalia and I have recently enrolled in the Apple Developer Program. I am planning to build an iOS app exclusively for users in Somalia. The app will offer premium digital features, and I would like to use WaafiPay, a local Somali payment provider that supports mobile-money payments such as EVC Plus, ZAAD and SAHAL. Somalia does not have an Apple App Store storefront or Apple In-App Purchase availability. Before I start development, I would like to confirm whether an app distributed to users in Somalia can use WaafiPay to process payments for premium digital features directly inside the app. If this is permitted, please let me know whether I need any special entitlement, approval, or implementation requirements. Thank you.
1
0
360
3d
Cannot Re-add Subscriptions and IAPs After Removing Them from Rejected App Submission
Hi, My app, HarpLegend, was rejected under Guidelines 2.3.2 and 2.3.10. The rejection required changes to my promotional images and purchase metadata. However, only the app version was rejected, while my two auto-renewable subscriptions (Monthly and Yearly) and one non-consumable IAP (Lifetime) remained in "Ready for Review" status. As a result, I was unable to edit their promotional images, display names, or descriptions, since these fields were read-only in App Store Connect. To make the corrections, I removed all three products from the existing submission. After successfully updating their metadata and promotional images, I attempted to add them back, but all three now return: "Unable to Add for Review — Something went wrong. Try again." The original submission still shows all three products as "Removed," while the app version and subscription group remain "Ready for Review." I've found several related discussions: Cannot cancel tvOS version In Review — Contains a report of nearly identical behavior after removing subscriptions. Subscriptions stuck in review after withdrawing a rejected submission — Describes subscriptions remaining locked after withdrawal. Cannot attach a first subscription to an app version stuck in a rejected submission — Describes a workaround involving moving the app version into an existing draft. My questions are: Has anyone successfully resolved this issue without removing the app version from the existing submission? If I remove the app version, will I be able to add for review again including the subscription group, both subscriptions, and the Lifetime IAP? Is there a way to resolve this without restarting the review process? I originally submitted my app on October 13, over five weeks ago, I had to cancel and restart the process two times already and would really like to avoid another lengthy wait. I've already replied to my App Review but haven't received a response yet. Any advice would be greatly appreciated. Thanks!
1
0
116
3d
StoreKit Sandbox returns 0 products after TN3186 checks — catalog association issue?
We are testing two auto-renewable subscriptions for a new iOS app. In Apple Sandbox, StoreKit 2 Product.products(for:) always returns an empty array. Legacy SKProductsRequest independently reports both identifiers as invalid. Environment: Physical iPhone, iOS 26.5 Xcode development build with automatic signing Storefront.current = USA (143441) canMakePayments = true No StoreKit Configuration file in the Run scheme Direct native StoreKit 2 diagnostics, without a third-party purchase SDK TN3186 checks completed: Explicit Bundle ID matches the App Store Connect app, installed app, and provisioning profile In-App Purchase is enabled for the App ID Developer membership, Paid Apps Agreement, banking, and tax are active One subscription group with monthly and yearly subscriptions is visible Pricing, localizations, and availability are configured Neither subscription is Rejected or Developer Action Needed The scheme is using real Sandbox data, not local StoreKit testing Results: StoreKit 2 batch query: rawCount = 0 SKProductsRequest: valid = []; both identifiers are invalid StoreKit 2 individual monthly query: 0 StoreKit 2 individual yearly query: 0 No exception; failure occurs during product discovery Related reports: https://developer.apple.com/forums/thread/839313 — TN3186 verified and USA storefront valid, but still 0 products; no replies https://developer.apple.com/forums/thread/841722 — Apple Commerce mentioned Rejected or Developer Action Needed states; ours have neither https://developer.apple.com/forums/thread/820656 — Apple DTS confirmed first subscriptions do not require review before Sandbox testing Apple Developer Support referred us to TN3186, and we verified every applicable item. The individual subscription detail route in App Store Connect also intermittently remains on a loading indicator although the group and both records are visible. Could an App Store Commerce or StoreKit engineer check whether the app-to-IAP catalog association is populated correctly on Apple's side, or advise an official escalation path to have the Sandbox catalog reprocessed? Exact account, app, product, device, email, and support-case identifiers are omitted from this public post and can be supplied privately through Apple Support or Feedback Assistant.
1
0
522
3d
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
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
Locate the In-App Purchases and Subscriptions Section in App Store Connect
App Store Connect displays the In-App Purchases and Subscriptions section on your app's version page when your app has an In-App Purchase or subscription with a Ready to Submit status. To locate the In-App Purchases and Subscriptions section: In Apps, select the app you want to view. In the sidebar, select the app version. On the version page, scroll down to the In-App Purchases and Subscriptions section. For more information, see Submit an In-App Purchase.
Replies
0
Boosts
0
Views
3.1k
Activity
Jun ’26
In-App Purchase Resources
General: Forums topic: StoreKit Forums tag: In-App Purchase App Store Pathway Simple and safe In-App Purchases Auto-renewable subscriptions In-App Purchase documentation Getting started with In-App Purchase using StoreKit views documentation Supporting business model changes by using the app transaction documentation Testing at all stages of development with Xcode and the sandbox documentation App Store Server Notifications documentation App Store Server API documentation Simplifying your implementation by using the App Store Server Library documentation TN3185: Troubleshooting In-App Purchases availability in Xcode technote TN3186: Troubleshooting In-App Purchases availability in the sandbox technote TN3188: Troubleshooting In-App Purchases availability in the App Store technote Understanding StoreKit workflows sample code Implementing a store in your app using the StoreKit API sample code What’s new in StoreKit and In-App Purchase video
Replies
0
Boosts
0
Views
2.3k
Activity
Jun ’26
StoreKit 2 returns USA storefront and USD price in TestFlight despite Japanese Apple Account
Hello, I'm developing an iOS app that uses StoreKit 2 for an auto-renewable subscription. I'm experiencing an issue where StoreKit returns the US storefront and USD pricing in TestFlight, even though the device's Apple Account and Sandbox Apple Account are configured for Japan. Environment App: YonsanmaruTimer (430タイマー) App version: 1.2.0 (TestFlight build 4) Bundle ID: com.manyouen.YonsanmaruTimer Product ID: com.manyouen.YonsanmaruTimer.plusassist.monthly StoreKit 2 Xcode Archive configuration: Release App Store Connect configuration The subscription is configured with the following prices: Japan: ¥200/month, with a one-month free trial United States: $0.99/month The app is intended for distribution in Japan. Observed behavior When fetching the subscription product using Product.products(for:), I log the current storefront and product price. The result is: Storefront: USA Price: $0.99 Currency: USDAs a result, the subscription price displayed in the app using product.displayPrice is $0.99 instead of ¥200. What I have already checked The device's Apple Account country/region for Media & Purchases is Japan. TestFlight is installed using my regular Japanese Apple Account. I created a new Sandbox Apple Account with Japan as its country/region and signed in through Settings → Developer → Sandbox Apple Account. The storefront still returns USA after restarting the TestFlight app. The app is archived using the Release build configuration. In an earlier subscription purchase test, Apple's native purchase confirmation sheet displayed ¥200, even though the app's product display price was $0.99. Questions Why would Storefront.current return USA in TestFlight under these conditions? Is this expected behavior in the TestFlight sandbox environment? Could this behavior also occur after the app is released on the App Store? Is there any additional account, device, or App Store Connect configuration I should check? I would like to ensure that the subscription price displayed in my app matches the price shown in Apple's purchase confirmation sheet before submitting the app for review. Any guidance would be greatly appreciated. Thank you.
Replies
0
Boosts
0
Views
77
Activity
12h
Sandbox IAP: AuthKit succeeds, then AMSServerErrorDomain -5000 (cancel-purchase-batch)
Every sandbox purchase of our auto-renewable subscriptions cancels right after AuthKit sign-in succeeds. It's blocking our 1.0 release. Filed as FB25469063, no reply yet. Capacitor iOS app, bundle io.xrplive.app, 1.0.0 (TestFlight), products io.xrplive.app.pro.monthly / .yearly, iPhone 17 Pro Max on iOS 27.0.1, StoreKit via @capgo/native-purchases. Console on every attempt: (1) AMSAuthKitUpdateTask: "The AuthKit authentication succeeded." (2) Then: Error Domain=AMSServerErrorDomain Code=-5000 UserInfo={failureType=-5000, m-allowed=false, cancel-purchase-batch=true, customerMessage=Check the account information you entered and try again.} Also AMSErrorDomain Code=100 (Authentication Failed), Code=2 ("Password reuse not available for account"), and a 401 from sandbox.itunes.apple.com/commerce/messages/app/inbox. We already fixed a purchase(confirmIn:) presentation issue. This failure is in sandbox verification after a successful sign-in, which we can't fix from the client. Is -5000 with cancel-purchase-batch a known sandbox account or commerce issue? Is there a sandbox tester or storefront state that fixes it when AuthKit succeeds but verification still fails?
Replies
1
Boosts
0
Views
67
Activity
12h
Two Apps Facing Review Issues – No Response from Apple. Could There Be an Issue with My Developer Account
Hello everyone, I'm an independent developer, and I'm currently experiencing review issues with two different apps under the same Apple Developer account. I'm starting to worry that there may be something wrong with my account or the review process. App 1 – Rejected Due to an Account Restriction Mistaken for a Bug My first app was rejected because the reviewer couldn't complete an in-app purchase. However, this wasn't a technical bug. My app has an intentional rule that prevents one Apple ID subscription from being linked to multiple app accounts. The sandbox Apple ID used during review had already been linked to another test account, which triggered this restriction. To make testing easier, I updated our server to remove this restriction for sandbox subscriptions while keeping it unchanged for real users. I explained everything to Apple on November 17 and requested another review. I also requested a phone call on November 18 and submitted an appeal. Unfortunately, I have received no response to any of these requests. App 2 – Rejected and Resubmitted, Still Waiting for Review My second app was also rejected because the reviewer reported that nothing happened after completing an in-app purchase. I resubmitted the app for review on November 19, but it is still waiting for review, and I haven't received any further feedback. My Main Concern Both apps are under the same developer account, and I'm having difficulty getting responses or moving the review process forward. I understand that reviews can take time, but I've already taken steps to address the issues and tried contacting Apple through multiple channels. I'm now concerned that there might be an issue with my developer account affecting the review process. Has anyone experienced similar problems with multiple apps under the same developer account? Is there any way to ask Apple to check whether my account has any review-related restrictions or unusual status? And when App Review messages, appeals, and phone call requests go unanswered, what is the best way to escalate the situation? I would really appreciate any advice from developers who have experienced something similar. Thank you!
Replies
1
Boosts
0
Views
145
Activity
15h
App Rejected Due to an Account Restriction, Not a Bug – No Response from Apple After Fixing the Issue
Hello everyone, I'm an independent developer, and I'm currently stuck in the App Review process. I'm hoping someone who has experienced something similar can offer some advice. My app was rejected because the reviewer encountered an error message when attempting to make an in-app purchase. However, this was not a technical bug or a StoreKit issue. It was an intentional account protection rule in my app. Here's what happened: My app has a rule that one Apple ID subscription can only be linked to one app account at a time. This prevents other accounts from taking over someone's paid subscription or sharing a single subscription across multiple accounts. During Apple's review, the sandbox Apple ID used by the reviewer had apparently already been linked to another test account. When the reviewer attempted to purchase a subscription using a different account, the app correctly triggered this restriction. Apple interpreted this behavior as a purchase failure and rejected the app. What I've done to resolve it: Although this rule is intentional and designed to protect users, I wanted to make the review process as easy as possible. I updated our server to remove this restriction specifically for sandbox subscriptions. Reviewers can now complete purchases and restore subscriptions even if their sandbox Apple ID was previously linked to another test account. The restriction remains unchanged for real production subscriptions. On November 17, I explained the situation to the App Review team and informed them that the sandbox issue had already been resolved. I asked them to test the purchase flow again. On November 18, I also requested a phone call to clarify the situation. The problem is that nobody has responded. I have not received any acknowledgment of my explanation, no response to my request for another review, and no phone call. I have also tried contacting Apple through the appeal process, but I still haven't received a response. At this point, I don't know what else I can do. The issue encountered during review has already been addressed, and no new app binary is required because the change was made entirely on our server. Has anyone experienced a similar situation where an app was rejected because an intentional business rule was mistaken for a bug? How did you get the App Review team to respond after explaining and resolving the issue? Is there any effective way to escalate this situation when both review messages and appeal requests go unanswered? submission ID 78b8dd94-fd4c-4951-959b-4fdb57a659d7 I would really appreciate any advice. Thank you!
Replies
0
Boosts
0
Views
106
Activity
1d
No MAS receipt after exit(173)
App receipt generation is broken (again). I'm getting the message my app is "damaged" on macOS Monterey 12.3.1 with Xcode 13.3.1 when no receipt is delivered after the app quits with exit(173) and I'm prompted for Mac App Store credentials. I tried App Store log out / log in (sandbox and regular account), cleaning derived data as well as reboot to no avail. Being aware of several old postings (and new comments), I decided to start a new thread to increase visibility ... and also filed a bug report FB10014055. Please consider a duplicate report if you're affected to raise Apple's awareness (all system status are reported as "green")...
Replies
12
Boosts
1
Views
4.4k
Activity
1d
StoreKit says purchase succeeded but didn't, AppStore.sync() throws error Unable to Complete Request
One user of my app reached out reporting an interesting in-app purchase issue. Has anyone encountered this or have an idea what's going on here? Proceed to purchase the non-consumable IAP in the app downloaded from the App Store iOS shows the price sheet as expected Confirm with the side button iOS shows an alert "You've already purchased this. Would you like to get it again for free?" Tap OK iOS shows an alert "You're all set. Your purchase was successful." Tap OK The app's content remains locked Tap Restore Purchases iOS shows an alert to sign (with the same account shown in step 2) Input the password and tap OK iOS shows an alert "Unable to Complete Request" (which is the error.localizedDescription thrown from AppStore.sync())
Replies
4
Boosts
0
Views
456
Activity
1d
All auto-renewable subscriptions returning expirationIntent = 5 after resolving an agreement issue (StoreKit 1 and StoreKit 2)
Hello, We are currently seeing errors when validating receipts for every auto-renewable subscription purchased through both StoreKit 1 and StoreKit 2. Details below. Case 1 — StoreKit 1 Calling https://buy.itunes.apple.com/verifyReceipt with the subscription receipt returns: "status": 21006, "expiration_intent": "5" Case 2 — StoreKit 2 Calling https://api.storekit.itunes.apple.com/inApps/v1/subscriptions and reading the most recent transaction (LastTransactionsItem) returns status 3. Within JWSRenewalInfoDecodedPayload: autoRenewStatus = 1, expirationIntent = 5 Timeline We believe renewals stopped processing for essentially all auto-renewing subscribers of our app as of 2026-09-18 09:30 KST (UTC+9). After resolving an agreement/licensing issue on our side, new purchases and some receipt validations recovered as of 2026-09-21 11:49 KST. However, most existing receipts still return expirationIntent = 5 when we query receipt validation or subscription status. Questions Is any action required on our side — a server-side change, a configuration change in App Store Connect, or a further review of our agreements? Now that the agreement issue is resolved, when are the renewals that were left pending during the outage expected to be processed? Any guidance would be appreciated. Thank you.
Replies
1
Boosts
0
Views
305
Activity
1d
Refund requests in the testing environment are never approved, only DECLINE resolves (consumables, non-renewing subscription) – FB25652374
We are testing refunds for consumables and a non-renewing subscription, installed from TestFlight (tester's own Apple Account, storefront VNM, iPhone 15, iOS 27.0.1), with App Store Server Notifications V2 on the sandbox URL. "Testing refund requests" says: "select any refund reason on the refund request sheet, and submit the sheet. The App Store automatically approves the refund request in the testing environment." What we see: DECLINE resolves every time, about 8 minutes after the CONSUMPTION_REQUEST: REFUND_DECLINED arrives whether our server answers refundPreference: DECLINE or the tester types DECLINE under Issue > Other. Nothing else resolves, for up to 43 hours so far (11 requests): no REFUND notification, no revocationDate in Get Transaction Info, empty Get Refund History. This covers: a listed reason with our server answering without refundPreference, answering GRANT_FULL (Send Consumption Information V2, inside the 5-minute window, 202), or not answering; GRANT_PRORATED and GRANT_FULL typed under Issue > Other. Every CONSUMPTION_REQUEST has consumptionRequestReason UNINTENDED_PURCHASE, even when the tester chose Issue > Other. Questions: Should a refund request in the testing environment be approved when the server answers without a preference, answers GRANT_FULL, or does not answer? Is the GRANT_PRORATED keyword still supported? Does refund testing require a Sandbox Apple Account instead of a TestFlight install? Full details, transaction IDs and decoded notification history are in FB25652374. Thread 743381 looks similar.
Replies
0
Boosts
0
Views
26
Activity
2d
StoreKit 2 returns USD product metadata in TestFlight while the storefront is FRA/EUR
Hello, We would appreciate some guidance regarding an unexpected StoreKit currency result in a TestFlight build. Our iPhone language and region are both set to France. The Sandbox tester is also configured for France, and our subscription products have French availability and pricing configured in App Store Connect. In the TestFlight build we diagnosed, StoreKit reports the current storefront as France with EUR: storefront=FRA/143442/EUR However, all 10 subscription products are returned with USD product metadata: products=10/10 formatCurrencies=USD localeCurrencies=USD error=NONE Example: formatCurrency=USD locale=fr_US_currency_USD localeCurrency=USD display=1,99 $US price=1.99 We first observed this through Flutter's in_app_purchase integration. To determine whether the Flutter plugin was involved, we added a native StoreKit 2 diagnostic to the same TestFlight build. The native result was identical: receipt=sandboxReceipt storefront before=FRA/143442/EUR storefront after=FRA/143442/EUR products=10/10 formatCurrencies=USD localeCurrencies=USD error=NONE The issue appears specific to the TestFlight distribution. When the application is installed directly from the development computer, prices are returned in euros on the same device. We also tested with the regular Media & Purchases account signed out and a French Sandbox tester connected. Once the products loaded successfully, StoreKit still returned USD metadata. In another configuration, the application displayed the USD price while Apple's purchase sheet displayed the price in euros. We are using the price and formatting information returned directly by StoreKit. We do not want to infer the currency from the device region or perform a client-side currency conversion, because StoreKit should remain the authoritative source. Could you please help us understand: Is it expected for Storefront.current to report FRA/EUR while Product.priceFormatStyle.currencyCode, its locale currency, and Product.displayPrice use USD? Could a TestFlight or App Store Connect configuration cause product metadata to use a different currency from the current storefront? Is there another account, availability, pricing or distribution setting that we should verify? Is there a recommended way to refresh or invalidate the product metadata used by a TestFlight installation? We have already filed Feedback Assistant report FB24723329, which is currently under investigation. Thank you very much for any clarification or additional diagnostic steps you can suggest.
Replies
11
Boosts
1
Views
1.6k
Activity
2d
Introductory Offer Start Timing
Hi everyone, I set up an auto-renewable subscription introductory offer in App Store Connect with a scheduled start date of September 7 for the Philippines storefront. According to the documentation App Store pricing and availability start times by country or region, scheduled pricing and offer updates are expected to go live based on local regional times. However, the offer did not show up in the Current Introductory Offers in app store connect portal at the documented start time (14:00 Sep 6th UTC). Instead, it stayed in the Upcoming Offers until 7:00 Sep 7th UTC which is 17 hours after the time in the doc. We met a similar situation a few days later when we launch another introductory offer in Thailand. I would appreciate clarification on the following points: What is the underlying reason for the discrepancy between the documented start time behavior and the actual start time observed in production? Can Apple update the App Store pricing and availability start times by country or region reference documentation so that it accurately reflects the practical start time and propagation window for each region? Any insights or shared experiences with offer scheduling in the APAC region would be greatly appreciated.
Replies
1
Boosts
0
Views
416
Activity
2d
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
500
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
528
Activity
2d
When IAPs would be available for Apple Watch?
I need someone from Apple to answer my question. I've added French localization to every of my IAP but I can't submit them due to this warning that sayws "In-app purchases and subscriptions are currently not supported on Apple Watch." The app is watchOS-only. Could you tell me please, when Could you tell me please, when IAPs would be supported?
Replies
2
Boosts
0
Views
259
Activity
2d
Apple In-App Purchase availability.
Hello, I am a developer based in Somalia and I have recently enrolled in the Apple Developer Program. I am planning to build an iOS app exclusively for users in Somalia. The app will offer premium digital features, and I would like to use WaafiPay, a local Somali payment provider that supports mobile-money payments such as EVC Plus, ZAAD and SAHAL. Somalia does not have an Apple App Store storefront or Apple In-App Purchase availability. Before I start development, I would like to confirm whether an app distributed to users in Somalia can use WaafiPay to process payments for premium digital features directly inside the app. If this is permitted, please let me know whether I need any special entitlement, approval, or implementation requirements. Thank you.
Replies
1
Boosts
0
Views
360
Activity
3d
Cannot Re-add Subscriptions and IAPs After Removing Them from Rejected App Submission
Hi, My app, HarpLegend, was rejected under Guidelines 2.3.2 and 2.3.10. The rejection required changes to my promotional images and purchase metadata. However, only the app version was rejected, while my two auto-renewable subscriptions (Monthly and Yearly) and one non-consumable IAP (Lifetime) remained in "Ready for Review" status. As a result, I was unable to edit their promotional images, display names, or descriptions, since these fields were read-only in App Store Connect. To make the corrections, I removed all three products from the existing submission. After successfully updating their metadata and promotional images, I attempted to add them back, but all three now return: "Unable to Add for Review — Something went wrong. Try again." The original submission still shows all three products as "Removed," while the app version and subscription group remain "Ready for Review." I've found several related discussions: Cannot cancel tvOS version In Review — Contains a report of nearly identical behavior after removing subscriptions. Subscriptions stuck in review after withdrawing a rejected submission — Describes subscriptions remaining locked after withdrawal. Cannot attach a first subscription to an app version stuck in a rejected submission — Describes a workaround involving moving the app version into an existing draft. My questions are: Has anyone successfully resolved this issue without removing the app version from the existing submission? If I remove the app version, will I be able to add for review again including the subscription group, both subscriptions, and the Lifetime IAP? Is there a way to resolve this without restarting the review process? I originally submitted my app on October 13, over five weeks ago, I had to cancel and restart the process two times already and would really like to avoid another lengthy wait. I've already replied to my App Review but haven't received a response yet. Any advice would be greatly appreciated. Thanks!
Replies
1
Boosts
0
Views
116
Activity
3d
StoreKit Sandbox returns 0 products after TN3186 checks — catalog association issue?
We are testing two auto-renewable subscriptions for a new iOS app. In Apple Sandbox, StoreKit 2 Product.products(for:) always returns an empty array. Legacy SKProductsRequest independently reports both identifiers as invalid. Environment: Physical iPhone, iOS 26.5 Xcode development build with automatic signing Storefront.current = USA (143441) canMakePayments = true No StoreKit Configuration file in the Run scheme Direct native StoreKit 2 diagnostics, without a third-party purchase SDK TN3186 checks completed: Explicit Bundle ID matches the App Store Connect app, installed app, and provisioning profile In-App Purchase is enabled for the App ID Developer membership, Paid Apps Agreement, banking, and tax are active One subscription group with monthly and yearly subscriptions is visible Pricing, localizations, and availability are configured Neither subscription is Rejected or Developer Action Needed The scheme is using real Sandbox data, not local StoreKit testing Results: StoreKit 2 batch query: rawCount = 0 SKProductsRequest: valid = []; both identifiers are invalid StoreKit 2 individual monthly query: 0 StoreKit 2 individual yearly query: 0 No exception; failure occurs during product discovery Related reports: https://developer.apple.com/forums/thread/839313 — TN3186 verified and USA storefront valid, but still 0 products; no replies https://developer.apple.com/forums/thread/841722 — Apple Commerce mentioned Rejected or Developer Action Needed states; ours have neither https://developer.apple.com/forums/thread/820656 — Apple DTS confirmed first subscriptions do not require review before Sandbox testing Apple Developer Support referred us to TN3186, and we verified every applicable item. The individual subscription detail route in App Store Connect also intermittently remains on a loading indicator although the group and both records are visible. Could an App Store Commerce or StoreKit engineer check whether the app-to-IAP catalog association is populated correctly on Apple's side, or advise an official escalation path to have the Sandbox catalog reprocessed? Exact account, app, product, device, email, and support-case identifiers are omitted from this public post and can be supplied privately through Apple Support or Feedback Assistant.
Replies
1
Boosts
0
Views
522
Activity
3d
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
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