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
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
490
2m
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
505
12m
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
243
1h
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
352
6h
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
95
20h
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
511
22h
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
83
1d
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
190
2d
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
131
2d
StoreKit 2 returns USA/USD in TestFlight but DEU/EUR in local Release build on the same device
Hi everyone, We are currently preparing the release of our Flutter-based iOS application and are experiencing an unusual StoreKit 2 storefront issue that only occurs when the app is installed through TestFlight. The problem When our application is installed through TestFlight, StoreKit 2 consistently returns the United States storefront (USA), and all six auto-renewable subscription products are displayed with USD prices. However, both the regular Apple Account and the Sandbox Apple Account are configured for Germany. We have verified the following: All six subscription products are correctly configured in App Store Connect with EUR prices for Germany. The subscriptions are available in Germany, Austria, and Switzerland. We created a completely new Sandbox tester with Germany selected during account creation, using an email address that had never previously been used for sandbox testing. The issue occurs on two different physical devices (iPhone and iPad). No local StoreKit configuration file is used. Our application does not override the storefront, modify localized prices, or contain any hardcoded USD fallback. Controlled comparison We performed additional tests using the same application code on the same iPhone. The results were: Installation method Storefront Currency Local Debug build via Xcode/Flutter DEU EUR Local development-signed Release build via Flutter DEU EUR TestFlight Release build USA USD The locally installed Release build successfully retrieves all six subscription products with their correct German prices. For example, StoreKit returns the following values for one of our subscriptions: Local Release build: Storefront.current.countryCode = DEU Product currencyCode = EUR Product.displayPrice = 6,99 € TestFlight build: Storefront.current.countryCode = USA Product currencyCode = USD Both builds use the same StoreKit 2 integration and product identifiers. Technical environment Framework: Flutter StoreKit integration: StoreKit 2 Flutter plugin: in_app_purchase_storekit 0.4.11+2 Devices: Physical iPhone and iPad iOS/iPadOS: 26.6.2 Subscription products: Six auto-renewable subscriptions Expected storefront: Germany (DEU) Actual TestFlight storefront: United States (USA) We have traced the storefront country code directly to StoreKit 2’s Storefront.current.countryCode and the localized prices to the product information returned by Product.products(for:). There is no application-level storefront override or price conversion. Questions Why would StoreKit 2 return a different storefront in TestFlight compared with a locally installed development-signed Release build on the same physical device? Could TestFlight use a different sandbox storefront or Apple Account context than a locally installed build? Is there a recommended way to diagnose or reset the storefront association used by TestFlight? Has anyone experienced similar behavior where TestFlight consistently returns USA despite using a German Apple Account and newly created German sandbox testers? We have already contacted Apple Developer Support and followed their recommendation to create a completely new German sandbox tester, but the issue persists. Any guidance from Apple engineers or developers who have encountered similar behavior would be greatly appreciated. Thank you!
1
0
73
3d
First iOS submission stuck in “Waiting for Review” for over two weeks
Our first app submission (Tupair, version 1.0, build 66, with one in-app purchase and a subscription group with two auto-renewable subscriptions) has been in “Waiting for Review” since 30 October. 28 October: App Review asked us to confirm our subscription prices. We confirmed the same day in the App Review thread. 30 October: resubmitted. It stayed in Waiting for Review for 12 days. 4 November: requested an expedited review. No response. 9 November: sent a message through Contact Us. No response. 11 November: cancelled and resubmitted, with the price explanation added to the review notes. Still in Waiting for Review today, 16 November, for all five items. Is something blocking this submission, or is there anything else we should do? Our Android version is already approved and our team is ready to launch.
1
0
57
3d
Developer account suspended, 550+ subscriptions affected — how can we help paying users during an unanswered review?
Hello, I’m posting to ask how developers are supposed to support existing paying subscribers when their Apple Developer account is suspended and the team handling the review does not respond. On September 23, I received a notification from Apple and submitted all the information requested. Since then, I have received no response from provider_review@apple.com. Apple Support initially replied to my inquiries, but my recent follow-ups have also gone unanswered. At the time of the suspension, my apps had more than 550 active subscriptions. Users are contacting me because they can no longer access the features or content they paid for. Some purchased their subscriptions shortly before the suspension and lost access almost immediately afterward. These customers have already paid, yet they cannot use their subscriptions, and I cannot even give them an estimated resolution date because I have no update from Apple. I understand that individual account reviews cannot be resolved publicly on this forum. However, there is a broader developer support question here: what should we do for paying customers while an account review remains unresolved? Specifically: Is there an escalation channel for cases where existing paying subscribers have lost access? What guidance should developers give affected customers about their subscriptions, remaining paid time, and refund requests? How can we obtain confirmation that our submitted information has been received and whether anything else is required? I have found other developers describing similar situations: https://developer.apple.com/forums/thread/848935 https://developer.apple.com/forums/thread/851172 https://developer.apple.com/forums/thread/853802 Has anyone in a similar situation received a substantive response or reached a resolution? If so, which support channel helped? I am available to provide any additional information Apple needs. My immediate concern is helping the customers who have already paid and are now left without access or a clear explanation of what happens next. Thank you.
0
0
144
4d
Storefront.current.countryCode returns USA despite Apple ID, device region, and sandbox tester all set to Spain
We have an app in TestFlight with a subscription group and an introductory offer (7-day free trial) configured only for Spain. When testing a sandbox purchase, no free trial is offered and prices display in USD. We confirmed via Purchases.storefront (RevenueCat SDK, which wraps Storefront.current.countryCode from StoreKit natively) that the resolved storefront is consistently USA, not ESP. Steps taken to troubleshoot, all showing Spain, with no change to the result: Real Apple ID's country/region (Settings > Name > Media & Purchases > View Account): Spain, locked/non-editable. 3 different sandbox tester accounts (App Store Connect > Sandbox): all set to Spain. Device Language & Region (Settings > General): Spain. No VPN active. Fully deleted and reinstalled the app (not just relaunched). Fully signed out and back in to the real Apple ID on the device, and changed/reverted device Region. Checked billing address on file for the payment method: Spain. Checked carrier/SIM: Orange España. App-level Pricing and Availability in App Store Connect was never configured before (base country defaulted to United States) — we corrected it to Spain and waited 24+ hours. No change. Unchecked "Pause subscription renewals for this tester" (an Apple sandbox testing flag meant to simulate a Terms & Conditions interruption) — no change. In every case, storefront.countryCode continues to return "USA". Question: What else determines the resolved StoreKit storefront for a given Apple ID/device combination, given that every visible setting indicates Spain? Is there a known cache that needs to be cleared on Apple's side? (We also have an open Apple Developer Support case, #30000007050484, still awaiting a first response after 6 days.)
2
0
106
5d
Subscriptions load in TestFlight sandbox but not during App Review — 2.1(b), third rejection
Our first submission has now been rejected under Guideline 2.1(b), with the message: "the in-app purchases do not load successfully." Each review was performed on an iPad Air 11-inch (M3) running iPadOS 26.6. The app sells only auto-renewable subscriptions. We cannot reproduce the failure, and we have verified every part of the configuration we can think of. WHAT WE VERIFIED (via the App Store Connect API, not just the UI) Two subscriptions in one group, state READY_TO_SUBMIT Product IDs exactly match what the app requests Available in 175 territories, including the United States Prices set, en-US localizations present for both products and for the group App review screenshots attached to both, state COMPLETE Both subscriptions are included in the review submission (READY_FOR_REVIEW) Paid Apps Agreement: Active. Bank account: Active. Tax forms: Active. WHAT WORKS On our own devices, installed via TestFlight (sandbox environment), the products load correctly and a purchase completes and activates as expected. This works on both a real Apple ID and a Sandbox Tester account. WHAT WE OBSERVED FROM THE REVIEW SESSION We use RevenueCat. Their server-side API returns our offering with both packages and the correct product identifiers, so the offering metadata is fine. Our backend also shows that the reviewer's session reached our servers and signed in successfully at the review timestamp, so the device had working network connectivity. That leaves StoreKit itself returning no products on the reviewer's device, which is what empties the offering. QUESTIONS Are there known conditions under which StoreKit returns no products in the App Review sandbox for subscriptions that are in "Ready to Submit" and are attached to the same submission as the binary? For an app that has never been approved, is product loading during review handled differently from a normal sandbox session on a released app? Is there any way to obtain diagnostics from a review session, or to ask the reviewer for a screenshot of the failing screen? Replies in Resolution Center so far have only repeated the original rejection text. Is there anything specific to iPadOS 26.6 that could affect StoreKit 2 product lookups? For the next submission we have added a timeout and automatic retries around the product lookup, plus a visible retry control instead of a spinner, in case the failure is a transient cold-start timeout. But we would rather understand the actual cause than keep guessing. Any pointers appreciated.
3
1
576
6d
StoreKit 2: Does Transaction.currentEntitlements get updated when my app isn't running?
TL;DR: Does iOS automatically receive App Store transaction updates in the background when internet connection is available so the backing storage state of Transaction.currentEntitlements gets synced even when my app is not running? Or does iOS update Transaction.currentEntitlements only when my app is running? The long version: Imagine the following situation: A user has purchased a non-consumable IAP in my app and is granted the locked premium content. The IAP transaction is now present in Transaction.currentEntitlements (it's also cached locally). The user blocks internet access every time before my app gets opened (either enables the Airplane mode and/or disconnects from the Wi-Fi before launching my app). So from this point on, my app never gets a chance to connect to the internet. The user gets refunded for the IAP. The user uses their iPhone to browse the internet via Safari, checks emails, etc. Then, before launching my app, the user blocks internet access. My app gets is launched (without internet access) and reads entitlements from Transaction.currentEntitlements. The question is: does the StoreKit service know that the IAP has been refunded? Did iOS update the local cached storage of Transaction.currentEntitlements while the user was connected to the internet in step 4? Or will Transaction.currentEntitlements contain the old state from step 1 so the app won't know about the refund and the user will be able to use my app's premium content which has been refunded by now? Is the behavior the same for auto-renewable subscriptions as it is for non-consumable IAPs?
1
0
620
6d
Title: StoreKit Sandbox: supportsMultiSeatPurchase is true, but pricingTerms contains no seatBased terms
We’re testing an annual multiseat subscription on a physical iPad. StoreKit returns the expected product and reports supportsMultiSeatPurchase == true, but its pricingTerms contains one term and no seatBased terms. Our app therefore cannot calculate a two-seat quote and stops before attempting a purchase. Environment iPad Air 11-inch (M3) iPadOS 27.3 beta (24C5037i) Xcode 27.3 beta (27C5020n) Development-signed app, version 1.0, diagnostic build 44 Physical-device testing with a US Sandbox purchaser App Store Connect configuration Annual auto-renewable subscription Multiseat purchases allowed Invitations provided by Apple Annual upfront availability enabled for the United States at USD 6.99 Subscription status: Prepare for Submission Sandbox purchases and renewals enabled Steps to reproduce Request the subscription using Product.products(for:). Confirm that the expected annual product is returned. Check supportsMultiSeatPurchase, which returns true. Inspect pricingTerms for supported upfront seatBased terms. Attempt to prepare a quote for two total seats. Actual result Total pricing terms: 1 Seat-based pricing terms: 0 Supported group pricing terms: 0 No purchase is attempted. Production sponsorship sales remain disabled. Expected result A supported upfront seat-based pricing term with Apple-provided pricing tiers that can be used to calculate a two-seat quote. Questions Is additional configuration or account eligibility required for Sandbox to return seat-based pricing terms? Must the subscription progress beyond Prepare for Submission before multiseat pricing can be tested? Can supportsMultiSeatPurchase legitimately return true while no seat-based pricing terms are available? If so, what conditions cause this? Is this a known limitation in this beta, and is there a supported workaround or recommended testing configuration? The issue was reproduced again on November 10, 2026, at approximately 9:57 PM Mountain Time. A sysdiagnose captured at 10:03:11 PM Mountain Time was attached privately to FB25451377. DTS directed us to post here under Case-ID: 23369152. We can provide a focused reproduction project if needed.
0
0
85
1w
Finance case unanswered since Nov 1: App Store Connect only offers W-9 for foreign-owned single-member LLC, Paid Apps Agreement blocked (Case-ID 23250875)
Hello, Our Apple Developer account is enrolled as an organization: a single-member US LLC (Wyoming), owned by one Israeli resident who is not a US person. The account has to remain an organization, since we distribute a VPN app and App Store Review Guideline 5.4 requires VPN apps to be offered by organizations. App Store Connect, however, only offers Form W-9 for the Paid Apps Agreement. For US tax purposes, the LLC is a disregarded entity and has not elected to be taxed as a corporation, so the IRS treats the foreign owner as the beneficial owner of the income. Per the IRS instructions, a foreign person may not provide a W-9, and the owner should provide a W-8BEN. W-8BEN-E doesn't fit either, because the LLC is a US entity, not a foreign one. Apple's help page says to contact Apple if the needed tax form isn't available, so we did: Nov 1: Contacted Apple Media Services Finance Support and received Case-ID 23250875. No reply since. Nov 12: Followed up on the Finance case and opened Developer Support case 30000012677969. Our tax information still shows as missing, the Paid Apps Agreement is pending, and in-app purchases can't go live. Questions: Could someone at Apple check the status of Finance Case-ID 23250875 (Developer Support case 30000012677969) or route it to the right Finance/Tax specialist? Has anyone with a foreign-owned single-member US LLC, enrolled as an organization, had W-8BEN enabled in App Store Connect? How long did it take, and what did Finance ask for? I'm not asking for tax advice, only for help with the support process. I can share account details privately with Apple. Thank you.
0
0
116
1w
StoreKit 2 returns no products for a non-renewing subscription in TestFlight Sandbox (China mainland)
I’m testing the first in-app purchase for an iOS app. It is a non-renewing subscription that grants 12 months of access. On November 9, a physical iPhone running our TestFlight build reproduced the same issue twice in the China mainland Sandbox storefront. Setup checked at the time The annual product was Ready to Submit in App Store Connect, with China mainland availability, a CNY 98 price, and a Simplified Chinese localization. The annual product identifier matched the identifier requested by the app. The explicit Bundle ID matched App Store Connect and had In-App Purchase enabled. The Paid Apps Agreement was active, and banking and tax records were in place. We used a mainland-China Sandbox tester and called the native StoreKit 2 Product.products(for:) API. The request included the configured annual product and an old monthly identifier that has no corresponding product in App Store Connect. Steps and results Install the app from TestFlight on a physical iPhone and open the purchase screen in Sandbox. Refresh the available products. We expect the annual product and its localized price to appear. Product.products(for:) completes with an empty array. Device logs show an HTTP 200 response from the China mainland Sandbox catalog followed by Ignoring empty product response. After the 600-second cache lifetime, the query received a different server correlation key and still returned no products. This occurs during product lookup, before any purchase call. TN3186 says that Sandbox testing can take place before submission for review. Has anyone reproduced this specifically with a non-renewing subscription? Is there another way to verify Sandbox catalog visibility for the configured annual product or diagnose why it is omitted? An annual-only StoreKit query would be a useful follow-up test. We can share the exact app and product identifiers, request correlation keys, and device diagnostics with Apple through Feedback Assistant.
0
0
37
1w
[IAP Review Delay] App Build Approved, but Important Update Blocked by Pending In-App Purchase Review
Hello Apple App Review Team and Developer Community, We are currently unable to release an approved app update due to delays in the In-App Purchase (IAP) review process. We would like to ask if anyone has experienced a similar situation or knows of a possible solution. App Information App ID: 6449141384 App Bundle ID: com.DetailGames.HungryAliens Timeline On November 3, 2026, we submitted a total of 38 items, including IAP products, for review. The submission is still in "Waiting for Review" status, and the review has not yet started. Meanwhile, our latest app build (iOS 1576), submitted on November 6, 2026, has already been approved. Impact of the Review Delay This update includes a limited-time event scheduled to begin on November 9, 2026, and run for approximately four weeks. However, the pending IAP review is preventing us from releasing the approved app build. As a result, we may be unable to deliver the event content to players as scheduled, potentially affecting their opportunity to participate in the event. Questions Has anyone experienced a situation where an app build was approved, but separately submitted IAP products remained in "Waiting for Review" status, preventing the update from being released? If you have successfully resolved a similar issue, we would appreciate hearing what steps you took. If Apple Developer Support does not respond or the issue remains unresolved, is there an official escalation process to request further assistance or review by a higher-level support team? We would greatly appreciate any guidance from an Apple App Review team member or developers who have encountered a similar situation. Thank you for your time and assistance.
2
6
272
1w
Retention Messaging in App Store Connect
I reached out to Apple Developer Support and they directed me to the forums. This video "Explore Retention Messaging in App Store Connect" shows a "Retention Messaging" section at the 3:21 timestamp of the video, within "Subscriptions" below the "Billing Grace Period" section. For the apps in our account, there is no "Retention Messaging" section available within the Subscriptions area. I am not asking about the API. I do not believe the API is required in order to have the Retention Messaging section show up in App Store Connect. In the video, the speaker says “I'll share an overview of Retention Messaging, and how to set it up in App Store Connect” and she shows how to navigate there. While she explains that “Real-time Retention Messaging is powered by the Retention Messaging API” - she also says that you can “create the same views using real-time Retention Messaging as you can when using retention messages in App Store Connect.” Is there something that we need to do in order to get access to this area of App Store Connect so we can set up Retention Messaging? Thank you so much.
1
3
486
1w
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
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
490
Activity
2m
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
505
Activity
12m
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
243
Activity
1h
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
352
Activity
6h
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
95
Activity
20h
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
511
Activity
22h
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
83
Activity
1d
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
190
Activity
2d
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
131
Activity
2d
StoreKit 2 returns USA/USD in TestFlight but DEU/EUR in local Release build on the same device
Hi everyone, We are currently preparing the release of our Flutter-based iOS application and are experiencing an unusual StoreKit 2 storefront issue that only occurs when the app is installed through TestFlight. The problem When our application is installed through TestFlight, StoreKit 2 consistently returns the United States storefront (USA), and all six auto-renewable subscription products are displayed with USD prices. However, both the regular Apple Account and the Sandbox Apple Account are configured for Germany. We have verified the following: All six subscription products are correctly configured in App Store Connect with EUR prices for Germany. The subscriptions are available in Germany, Austria, and Switzerland. We created a completely new Sandbox tester with Germany selected during account creation, using an email address that had never previously been used for sandbox testing. The issue occurs on two different physical devices (iPhone and iPad). No local StoreKit configuration file is used. Our application does not override the storefront, modify localized prices, or contain any hardcoded USD fallback. Controlled comparison We performed additional tests using the same application code on the same iPhone. The results were: Installation method Storefront Currency Local Debug build via Xcode/Flutter DEU EUR Local development-signed Release build via Flutter DEU EUR TestFlight Release build USA USD The locally installed Release build successfully retrieves all six subscription products with their correct German prices. For example, StoreKit returns the following values for one of our subscriptions: Local Release build: Storefront.current.countryCode = DEU Product currencyCode = EUR Product.displayPrice = 6,99 € TestFlight build: Storefront.current.countryCode = USA Product currencyCode = USD Both builds use the same StoreKit 2 integration and product identifiers. Technical environment Framework: Flutter StoreKit integration: StoreKit 2 Flutter plugin: in_app_purchase_storekit 0.4.11+2 Devices: Physical iPhone and iPad iOS/iPadOS: 26.6.2 Subscription products: Six auto-renewable subscriptions Expected storefront: Germany (DEU) Actual TestFlight storefront: United States (USA) We have traced the storefront country code directly to StoreKit 2’s Storefront.current.countryCode and the localized prices to the product information returned by Product.products(for:). There is no application-level storefront override or price conversion. Questions Why would StoreKit 2 return a different storefront in TestFlight compared with a locally installed development-signed Release build on the same physical device? Could TestFlight use a different sandbox storefront or Apple Account context than a locally installed build? Is there a recommended way to diagnose or reset the storefront association used by TestFlight? Has anyone experienced similar behavior where TestFlight consistently returns USA despite using a German Apple Account and newly created German sandbox testers? We have already contacted Apple Developer Support and followed their recommendation to create a completely new German sandbox tester, but the issue persists. Any guidance from Apple engineers or developers who have encountered similar behavior would be greatly appreciated. Thank you!
Replies
1
Boosts
0
Views
73
Activity
3d
First iOS submission stuck in “Waiting for Review” for over two weeks
Our first app submission (Tupair, version 1.0, build 66, with one in-app purchase and a subscription group with two auto-renewable subscriptions) has been in “Waiting for Review” since 30 October. 28 October: App Review asked us to confirm our subscription prices. We confirmed the same day in the App Review thread. 30 October: resubmitted. It stayed in Waiting for Review for 12 days. 4 November: requested an expedited review. No response. 9 November: sent a message through Contact Us. No response. 11 November: cancelled and resubmitted, with the price explanation added to the review notes. Still in Waiting for Review today, 16 November, for all five items. Is something blocking this submission, or is there anything else we should do? Our Android version is already approved and our team is ready to launch.
Replies
1
Boosts
0
Views
57
Activity
3d
Developer account suspended, 550+ subscriptions affected — how can we help paying users during an unanswered review?
Hello, I’m posting to ask how developers are supposed to support existing paying subscribers when their Apple Developer account is suspended and the team handling the review does not respond. On September 23, I received a notification from Apple and submitted all the information requested. Since then, I have received no response from provider_review@apple.com. Apple Support initially replied to my inquiries, but my recent follow-ups have also gone unanswered. At the time of the suspension, my apps had more than 550 active subscriptions. Users are contacting me because they can no longer access the features or content they paid for. Some purchased their subscriptions shortly before the suspension and lost access almost immediately afterward. These customers have already paid, yet they cannot use their subscriptions, and I cannot even give them an estimated resolution date because I have no update from Apple. I understand that individual account reviews cannot be resolved publicly on this forum. However, there is a broader developer support question here: what should we do for paying customers while an account review remains unresolved? Specifically: Is there an escalation channel for cases where existing paying subscribers have lost access? What guidance should developers give affected customers about their subscriptions, remaining paid time, and refund requests? How can we obtain confirmation that our submitted information has been received and whether anything else is required? I have found other developers describing similar situations: https://developer.apple.com/forums/thread/848935 https://developer.apple.com/forums/thread/851172 https://developer.apple.com/forums/thread/853802 Has anyone in a similar situation received a substantive response or reached a resolution? If so, which support channel helped? I am available to provide any additional information Apple needs. My immediate concern is helping the customers who have already paid and are now left without access or a clear explanation of what happens next. Thank you.
Replies
0
Boosts
0
Views
144
Activity
4d
Storefront.current.countryCode returns USA despite Apple ID, device region, and sandbox tester all set to Spain
We have an app in TestFlight with a subscription group and an introductory offer (7-day free trial) configured only for Spain. When testing a sandbox purchase, no free trial is offered and prices display in USD. We confirmed via Purchases.storefront (RevenueCat SDK, which wraps Storefront.current.countryCode from StoreKit natively) that the resolved storefront is consistently USA, not ESP. Steps taken to troubleshoot, all showing Spain, with no change to the result: Real Apple ID's country/region (Settings > Name > Media & Purchases > View Account): Spain, locked/non-editable. 3 different sandbox tester accounts (App Store Connect > Sandbox): all set to Spain. Device Language & Region (Settings > General): Spain. No VPN active. Fully deleted and reinstalled the app (not just relaunched). Fully signed out and back in to the real Apple ID on the device, and changed/reverted device Region. Checked billing address on file for the payment method: Spain. Checked carrier/SIM: Orange España. App-level Pricing and Availability in App Store Connect was never configured before (base country defaulted to United States) — we corrected it to Spain and waited 24+ hours. No change. Unchecked "Pause subscription renewals for this tester" (an Apple sandbox testing flag meant to simulate a Terms & Conditions interruption) — no change. In every case, storefront.countryCode continues to return "USA". Question: What else determines the resolved StoreKit storefront for a given Apple ID/device combination, given that every visible setting indicates Spain? Is there a known cache that needs to be cleared on Apple's side? (We also have an open Apple Developer Support case, #30000007050484, still awaiting a first response after 6 days.)
Replies
2
Boosts
0
Views
106
Activity
5d
Subscriptions load in TestFlight sandbox but not during App Review — 2.1(b), third rejection
Our first submission has now been rejected under Guideline 2.1(b), with the message: "the in-app purchases do not load successfully." Each review was performed on an iPad Air 11-inch (M3) running iPadOS 26.6. The app sells only auto-renewable subscriptions. We cannot reproduce the failure, and we have verified every part of the configuration we can think of. WHAT WE VERIFIED (via the App Store Connect API, not just the UI) Two subscriptions in one group, state READY_TO_SUBMIT Product IDs exactly match what the app requests Available in 175 territories, including the United States Prices set, en-US localizations present for both products and for the group App review screenshots attached to both, state COMPLETE Both subscriptions are included in the review submission (READY_FOR_REVIEW) Paid Apps Agreement: Active. Bank account: Active. Tax forms: Active. WHAT WORKS On our own devices, installed via TestFlight (sandbox environment), the products load correctly and a purchase completes and activates as expected. This works on both a real Apple ID and a Sandbox Tester account. WHAT WE OBSERVED FROM THE REVIEW SESSION We use RevenueCat. Their server-side API returns our offering with both packages and the correct product identifiers, so the offering metadata is fine. Our backend also shows that the reviewer's session reached our servers and signed in successfully at the review timestamp, so the device had working network connectivity. That leaves StoreKit itself returning no products on the reviewer's device, which is what empties the offering. QUESTIONS Are there known conditions under which StoreKit returns no products in the App Review sandbox for subscriptions that are in "Ready to Submit" and are attached to the same submission as the binary? For an app that has never been approved, is product loading during review handled differently from a normal sandbox session on a released app? Is there any way to obtain diagnostics from a review session, or to ask the reviewer for a screenshot of the failing screen? Replies in Resolution Center so far have only repeated the original rejection text. Is there anything specific to iPadOS 26.6 that could affect StoreKit 2 product lookups? For the next submission we have added a timeout and automatic retries around the product lookup, plus a visible retry control instead of a spinner, in case the failure is a transient cold-start timeout. But we would rather understand the actual cause than keep guessing. Any pointers appreciated.
Replies
3
Boosts
1
Views
576
Activity
6d
StoreKit 2: Does Transaction.currentEntitlements get updated when my app isn't running?
TL;DR: Does iOS automatically receive App Store transaction updates in the background when internet connection is available so the backing storage state of Transaction.currentEntitlements gets synced even when my app is not running? Or does iOS update Transaction.currentEntitlements only when my app is running? The long version: Imagine the following situation: A user has purchased a non-consumable IAP in my app and is granted the locked premium content. The IAP transaction is now present in Transaction.currentEntitlements (it's also cached locally). The user blocks internet access every time before my app gets opened (either enables the Airplane mode and/or disconnects from the Wi-Fi before launching my app). So from this point on, my app never gets a chance to connect to the internet. The user gets refunded for the IAP. The user uses their iPhone to browse the internet via Safari, checks emails, etc. Then, before launching my app, the user blocks internet access. My app gets is launched (without internet access) and reads entitlements from Transaction.currentEntitlements. The question is: does the StoreKit service know that the IAP has been refunded? Did iOS update the local cached storage of Transaction.currentEntitlements while the user was connected to the internet in step 4? Or will Transaction.currentEntitlements contain the old state from step 1 so the app won't know about the refund and the user will be able to use my app's premium content which has been refunded by now? Is the behavior the same for auto-renewable subscriptions as it is for non-consumable IAPs?
Replies
1
Boosts
0
Views
620
Activity
6d
Title: StoreKit Sandbox: supportsMultiSeatPurchase is true, but pricingTerms contains no seatBased terms
We’re testing an annual multiseat subscription on a physical iPad. StoreKit returns the expected product and reports supportsMultiSeatPurchase == true, but its pricingTerms contains one term and no seatBased terms. Our app therefore cannot calculate a two-seat quote and stops before attempting a purchase. Environment iPad Air 11-inch (M3) iPadOS 27.3 beta (24C5037i) Xcode 27.3 beta (27C5020n) Development-signed app, version 1.0, diagnostic build 44 Physical-device testing with a US Sandbox purchaser App Store Connect configuration Annual auto-renewable subscription Multiseat purchases allowed Invitations provided by Apple Annual upfront availability enabled for the United States at USD 6.99 Subscription status: Prepare for Submission Sandbox purchases and renewals enabled Steps to reproduce Request the subscription using Product.products(for:). Confirm that the expected annual product is returned. Check supportsMultiSeatPurchase, which returns true. Inspect pricingTerms for supported upfront seatBased terms. Attempt to prepare a quote for two total seats. Actual result Total pricing terms: 1 Seat-based pricing terms: 0 Supported group pricing terms: 0 No purchase is attempted. Production sponsorship sales remain disabled. Expected result A supported upfront seat-based pricing term with Apple-provided pricing tiers that can be used to calculate a two-seat quote. Questions Is additional configuration or account eligibility required for Sandbox to return seat-based pricing terms? Must the subscription progress beyond Prepare for Submission before multiseat pricing can be tested? Can supportsMultiSeatPurchase legitimately return true while no seat-based pricing terms are available? If so, what conditions cause this? Is this a known limitation in this beta, and is there a supported workaround or recommended testing configuration? The issue was reproduced again on November 10, 2026, at approximately 9:57 PM Mountain Time. A sysdiagnose captured at 10:03:11 PM Mountain Time was attached privately to FB25451377. DTS directed us to post here under Case-ID: 23369152. We can provide a focused reproduction project if needed.
Replies
0
Boosts
0
Views
85
Activity
1w
Finance case unanswered since Nov 1: App Store Connect only offers W-9 for foreign-owned single-member LLC, Paid Apps Agreement blocked (Case-ID 23250875)
Hello, Our Apple Developer account is enrolled as an organization: a single-member US LLC (Wyoming), owned by one Israeli resident who is not a US person. The account has to remain an organization, since we distribute a VPN app and App Store Review Guideline 5.4 requires VPN apps to be offered by organizations. App Store Connect, however, only offers Form W-9 for the Paid Apps Agreement. For US tax purposes, the LLC is a disregarded entity and has not elected to be taxed as a corporation, so the IRS treats the foreign owner as the beneficial owner of the income. Per the IRS instructions, a foreign person may not provide a W-9, and the owner should provide a W-8BEN. W-8BEN-E doesn't fit either, because the LLC is a US entity, not a foreign one. Apple's help page says to contact Apple if the needed tax form isn't available, so we did: Nov 1: Contacted Apple Media Services Finance Support and received Case-ID 23250875. No reply since. Nov 12: Followed up on the Finance case and opened Developer Support case 30000012677969. Our tax information still shows as missing, the Paid Apps Agreement is pending, and in-app purchases can't go live. Questions: Could someone at Apple check the status of Finance Case-ID 23250875 (Developer Support case 30000012677969) or route it to the right Finance/Tax specialist? Has anyone with a foreign-owned single-member US LLC, enrolled as an organization, had W-8BEN enabled in App Store Connect? How long did it take, and what did Finance ask for? I'm not asking for tax advice, only for help with the support process. I can share account details privately with Apple. Thank you.
Replies
0
Boosts
0
Views
116
Activity
1w
StoreKit 2 returns no products for a non-renewing subscription in TestFlight Sandbox (China mainland)
I’m testing the first in-app purchase for an iOS app. It is a non-renewing subscription that grants 12 months of access. On November 9, a physical iPhone running our TestFlight build reproduced the same issue twice in the China mainland Sandbox storefront. Setup checked at the time The annual product was Ready to Submit in App Store Connect, with China mainland availability, a CNY 98 price, and a Simplified Chinese localization. The annual product identifier matched the identifier requested by the app. The explicit Bundle ID matched App Store Connect and had In-App Purchase enabled. The Paid Apps Agreement was active, and banking and tax records were in place. We used a mainland-China Sandbox tester and called the native StoreKit 2 Product.products(for:) API. The request included the configured annual product and an old monthly identifier that has no corresponding product in App Store Connect. Steps and results Install the app from TestFlight on a physical iPhone and open the purchase screen in Sandbox. Refresh the available products. We expect the annual product and its localized price to appear. Product.products(for:) completes with an empty array. Device logs show an HTTP 200 response from the China mainland Sandbox catalog followed by Ignoring empty product response. After the 600-second cache lifetime, the query received a different server correlation key and still returned no products. This occurs during product lookup, before any purchase call. TN3186 says that Sandbox testing can take place before submission for review. Has anyone reproduced this specifically with a non-renewing subscription? Is there another way to verify Sandbox catalog visibility for the configured annual product or diagnose why it is omitted? An annual-only StoreKit query would be a useful follow-up test. We can share the exact app and product identifiers, request correlation keys, and device diagnostics with Apple through Feedback Assistant.
Replies
0
Boosts
0
Views
37
Activity
1w
[IAP Review Delay] App Build Approved, but Important Update Blocked by Pending In-App Purchase Review
Hello Apple App Review Team and Developer Community, We are currently unable to release an approved app update due to delays in the In-App Purchase (IAP) review process. We would like to ask if anyone has experienced a similar situation or knows of a possible solution. App Information App ID: 6449141384 App Bundle ID: com.DetailGames.HungryAliens Timeline On November 3, 2026, we submitted a total of 38 items, including IAP products, for review. The submission is still in "Waiting for Review" status, and the review has not yet started. Meanwhile, our latest app build (iOS 1576), submitted on November 6, 2026, has already been approved. Impact of the Review Delay This update includes a limited-time event scheduled to begin on November 9, 2026, and run for approximately four weeks. However, the pending IAP review is preventing us from releasing the approved app build. As a result, we may be unable to deliver the event content to players as scheduled, potentially affecting their opportunity to participate in the event. Questions Has anyone experienced a situation where an app build was approved, but separately submitted IAP products remained in "Waiting for Review" status, preventing the update from being released? If you have successfully resolved a similar issue, we would appreciate hearing what steps you took. If Apple Developer Support does not respond or the issue remains unresolved, is there an official escalation process to request further assistance or review by a higher-level support team? We would greatly appreciate any guidance from an Apple App Review team member or developers who have encountered a similar situation. Thank you for your time and assistance.
Replies
2
Boosts
6
Views
272
Activity
1w
Retention Messaging in App Store Connect
I reached out to Apple Developer Support and they directed me to the forums. This video "Explore Retention Messaging in App Store Connect" shows a "Retention Messaging" section at the 3:21 timestamp of the video, within "Subscriptions" below the "Billing Grace Period" section. For the apps in our account, there is no "Retention Messaging" section available within the Subscriptions area. I am not asking about the API. I do not believe the API is required in order to have the Retention Messaging section show up in App Store Connect. In the video, the speaker says “I'll share an overview of Retention Messaging, and how to set it up in App Store Connect” and she shows how to navigate there. While she explains that “Real-time Retention Messaging is powered by the Retention Messaging API” - she also says that you can “create the same views using real-time Retention Messaging as you can when using retention messages in App Store Connect.” Is there something that we need to do in order to get access to this area of App Store Connect so we can set up Retention Messaging? Thank you so much.
Replies
1
Boosts
3
Views
486
Activity
1w