Hi! I’m facing some difficulties while integrating with Apple external purchase API. I would like to clarify a few points in the documentation. Subscription Events Documentation mentions four subscription events: SUBSCRIPTION_START, SUBSCRIPTION_CHANGE, SUBSCRIPTION_PAYMENT, and RENEWAL. Could you clarify what SUBSCRIPTION_PAYMENT is used for? The examples indicate that we should send the tax and payment amounts in the SUBSCRIPTION_START and RENEWAL events. Should we also send them for SUBSCRIPTION_PAYMENT? 2. Unused Tokens Customers generate ACQUISITION and SERVICE tokens and send them to us. According to the documentation, we must report every token received. If we process balance transactions linked to an ACQUISITION token, should we send the SERVICE token with NO LINE ITEM? Should we continue sending the SERVICE token with NO LINE ITEM status in the following months? 3. Should we send reports only once a month? What should we do if, at the time a transaction is received, the token was active, but by the time the report is due, it has already expired? Do we still need to report it in that case? 4. What should we do if we receive a notification about an unreported token in the middle of the month? Should we send the report immediately, or should we take note of the token and include it in the report at the scheduled time at the beginning of the month? 5. Am I correct in understanding that if a user purchases a monthly subscription and cancels the renewals within the same month, the reports will contain only one event — SUBSCRIPTION_START with subscriptionDaysOfPaidService = 0? If a renewal for a monthly subscription fails and the payment is completed after a 7-day grace period, should we report 37 days or 30 days in subscriptionDaysOfPaidService in the RENEWAL event? Thank you in advance for your guidance!

I'm in the final phase before app approval and I'm struggling to implement store kit for in app purchases. I'm using base 44 and really need help finishing this set up. I have an iOS app (SwiftUI + WKWebView) with auto-renewable subscriptions using StoreKit and SubscriptionStoreView. The app was rejected under Guideline 3.1 because payments were defaulting to Stripe instead of storekit. What’s already done: Subscriptions created in App Store Connect (monthly + annual) SubscriptionStoreView implemented and visible in app WKWebView bridge triggers native StoreKit paywall Sandbox test account created Stripe fully disabled on iOS What I need: Verify StoreKit implementation is App Review compliant Confirm subscriptions are correctly attached to the app version Ensure paywall is discoverable by App Review Help me pass App Review (reply guidance + final checks) This is a short engagement (1–3 hours). Looking for someone with real StoreKit + App Review experience + Base44 knowledge.

Hello, I need guidance on App Store Connect product state vs StoreKit behavior during App Review. Stack: iOS app (Expo / React Native), subscriptions via RevenueCat + StoreKit. Bundle ID matches App Store Connect. RevenueCat API keys — what I’ve verified locally: With the production RevenueCat API key (iOS appl_..., same as the submitted build), everything works on local device but not when I download it from TestFlight. I have also tested with RevenueCat’s sandbox / test API key (the separate key intended for sandbox/testing). That setup works as well — I can load offerings and complete test purchases the same way What RevenueCat (SDK / dashboard health) reports: Product monthly is configured in RevenueCat. Warnings that products aren’t approved in App Store Connect yet and that the default offering has configuration issues. Apple’s product state: WAITING_FOR_REVIEW. The SDK still states that test purchases are possible. What App Review reports: After onboarding a new business account, “Activate subscription” leads to an error (plans don’t load / purchase path fails). Review suggested an app code issue. Why this is confusing: Locally, both RevenueCat key modes I tried (production and sandbox/test) work with Apple Sandbox on the device. The submitted build uses the production RevenueCat key. Review still sees a failure. Questions: For IAP in WAITING_FOR_REVIEW, should App Review always use an Apple Sandbox account to test subscriptions until the product is fully approved? Is it documented that StoreKit may not return products during review without Sandbox while the product remains WAITING_FOR_REVIEW? Has anyone else seen “works locally (prod + sandbox RevenueCat keys + Apple Sandbox) but Review fails” with the same WAITING_FOR_REVIEW state? Thanks for any official documentation or similar threads.

Hello, I have a perplexing issue with apple reviewers not having the same experience as myself regarding the paywall. This is an Expo app and uses RevenueCat and SuperWall integrations. This app is going through its first review - it is not published yet. So the app and its subscriptions are being reviewed for the first time. I should also mention that this is my first time as an app developer, so please pardon my ignorance. When I install the app from TestFlight and launch it, I see the paywall with the product prices shown and I can complete a test purchase. Same for my friends who I've asked to test for me. But the apple reviewer does not see the product prices when the paywall is shown to them. Without being able to replicate the problem I am flying blind. I don't want to re-submit the app for review only to find the same problem exists. I also need to understand what is different between my testing environment and the apple testers. If anyone can point me in the right direction here I would really appreciate the help!

I’m trying to submit my app for review, but I’m currently blocked due to a recurring issue with in-app subscriptions. Both of my auto-renewable subscriptions (premium_monthly and premium_yearly) are marked as “Waiting for Review”. However, I am still seeing the blue box stating that “your first subscription must be submitted with a new app version.” Despite creating a new version (1.0.1) and uploading/selecting a new build , I am not seeing the “In-App Purchases and Subscriptions” section on the version page, and I therefore cannot link the subscriptions before submitting. This issue is blocking my ability to submit the app for review. Any help to resolve this would be greatly appreciated.

Hello, We are a Russian developer attempting to enable the StoreKit External Purchase Link Entitlement for our app. According to Apple’s documentation, this entitlement is required to provide external purchase links in Russia. However, the official request page consistently returns a 500 Internal Server Error: https://developer.apple.com/contact/request/storekit-external-entitlement-ru Steps we tried: Different browsers (Safari, Chrome, Edge) Different networks and VPNs Multiple developer accounts The error persists in all cases. We have already opened a support case (Case #102864703080), but Developer Support advised us to post here for technical guidance. Questions: Is there an alternative way to submit the entitlement request while the page is unavailable? Can Apple confirm whether this is a known issue and if a fix is in progress? Are manual submissions via the general Contact Us form accepted for this entitlement? Screenshots of the error are attached. Thank you in advance for any guidance.

Hello, We are facing an issue with In-App Purchases (subscriptions) in two iOS apps built with React Native + react-native-iap. Issue Some users receive the error: E_CONNECTION_CLOSED during the purchase flow. However: The payment is successfully deducted via the App Store. The subscription appears in the user's Apple ID subscription list. But on our side: The app does not receive the StoreKit transaction callback No receipt or transaction ID is delivered Our backend cannot validate the purchase. Restore Purchases When affected users try Restore Purchases, StoreKit returns: No purchases found even though the subscription is visible in their Apple ID. Most affected users are from India, and many payments are made via UPI through App Store billing. Has anyone experienced a case where: *the user is charged *the subscription exists in Apple ID *but StoreKit never returns the transaction or receipt? Any suggestions on how to recover these transactions would be greatly appreciated. Thanks!

I hope you are doing well. I am reaching out to inquire about a few aspects of implementing non-renewing subscriptions in our app. Firstly, we have encountered a limitation in App Store Connect where the maximum price tier available for non-renewing subscriptions in Euros is €1199. However, our product is priced at €1799. Could anyone please advise how we can handle this scenario? Is there a way to request custom pricing beyond the available tiers, or is there an alternative approach you would recommend? Additionally, we would like clarification on the following: Promo Codes: Are promo codes supported for each non-renewing subscription product? If so, how can we configure and distribute them? Installment Payments: Is it possible to enable installment-based payments for non-renewing subscriptions? If yes, could you guide us on how to set this up or if there are any prerequisites?

Submitted my app and it was approved by Apple. I then downloaded it from the app store and went through onboarding however when I tried to complete a purchase it failed. Went back to app store connect and saw that there is an issue with my subscriptions. Says localization is rejected but does not provide any reason why. Any ideas?? Everything worked fine with sandbox account.

Hello Apple team, We would like to access the user's available purchases from the keyboard extension. Making purchases directly from the keyboard is a great benefit, but we assume it is intentionally disabled to prevent abuse or fraudulent purchase attempts. What we care about the most is determining if the user has an item that contains a discount or a free trial to personalize messaging when we suggest the user go to the app and make a purchase. We hope you'd consider revising your policy around StoreKit usage.

Hi, I’ve been invited to an Apple Developer account with the Developer role. I’ve already created a subscription in App Store Connect, but when I try to fetch available subscriptions in Xcode for in-app purchase, nothing appears to be available for purchase.

Since January 28, 2026, we’ve noticed an increase in StoreKit-related errors during purchase flows. Specifically, we’re seeing a spike in errors reported as “Unable to Complete Request”, categorized as unknown StoreKit errors. This correlates with a noticeable drop in the overall purchase success rate. A few observations: The issue is not limited to the latest app version, it also affects older versions. It appears to occur only on iOS 17+. The impact seems country-specific: some regions are affected more heavily, while others show no significant change compared to previous days. At the moment, there are no related incidents reported on Apple’s System Status page. Given these symptoms, this looks like a potential StoreKit / Apple API issue, but we haven’t found any official confirmation yet. Has anyone else observed similar StoreKit behavior recently on iOS 17+? Any insights or known issues would be greatly appreciated.

Why is this rejection coming? I don't understand.I can't see anything in my mailbox.

One of our apps has 85% stuck in Billing Retry -- We are so confused. All the users are from the US, and have a one-week free trial. We had 1,000 subscriptions expire from this issue. So any help would be so appreciated.

We got Advanced Commerce API and the generic product identifiers approved. When I was try to migrate a sandbox subscription to ACA enabled subscription I hit an error Request payload (Hid some info but the requestReferenceId is the real) { "descriptors": { "description": "Migrated", "displayName": "Migration" }, "items": [ { "sku": "product_1mo_999", "description": "description", "displayName": "Product" } ], "requestInfo": { "requestReferenceId": "3b0b8e67-d8a0-45f4-8f6d-06bffa9a2c08" }, "storefront": "USA", "targetProductId": "com.company.generic.subscription", "taxCode": "C003-00-1" } Response { "errorCode": 5000000, "errorMessage": "An unknown error occurred." }

I’m trying to find out whether anyone has seen this kind of App Store Connect issue remain unresolved for this long. This is for a first auto-renewable subscription. Timeline: Original support case opened: Feb 27, 2026 Support initially repeated the normal guidance that the first subscription must be submitted with the app version I explained that the issue was not the process itself, but a stuck review state On Mar 25, 2026, I was told the case had been escalated to the appropriate internal team Since then, I have sent follow-up emails asking for status / owner / ETA As of Apr 12, 2026 (KST), there has still been no meaningful update Current state in App Store Connect: App version 1.0.10 is still “Prepare for Submission” Previous 1.0.10 submissions show as “Deleted” There is no active app review submission for 1.0.10 The subscription previously showed “Waiting for Review” Now the subscription itself shows “In Review” But its localization still shows “Waiting for Review” So the state looks inconsistent: no active app review submission app version still draft subscription partially moved into review anyway At this point I’m not asking about the normal first-subscription submission flow. I already understand that. What I’m trying to understand is: Has anyone seen a case like this stay stuck for 6+ weeks? Has anyone had Apple say it was escalated internally and then go silent for weeks? Did Apple eventually fix it manually? Is this something that can remain stuck indefinitely unless the internal team intervenes? Any comparable experience would be helpful.

Hello I have buy new developepr membership and i have get email for purchase confirmation but when ihave go to developer account i have seen this. Purchase your membership. To continue your enrollment, complete your purchase now. Your purchase may take up to 48 hours to process. Please help me why it will show this if i have already buy the membership and i itune i have check and see the member is active and valid for 1 year. Please help me to solve this issue.

Good afternoon, I‘m currently disputing over (8) applications on the App Store for legal (intellectual property right infringement) and for fraud. The mobile applications I created were hijacked from me and even submitted an FBI report. I’m wondering how long for Apple to recover these mobile applications? And how does the original financials work for the mobile apps I created since they were uploaded using API keys? I submitted legal intellectual property rights infringement, reported the apps to Fraud. All mobile applications should be listed under my Apple Developer Account. Furthermore, where do I go if I need assistance with these apps? I submitted the complaints about two weeks ago. Also when will Apple side legal be able to resolve these issues. The banking information for all mobile applications should also be freezed. Can someone from Apple help me get this resolved? All mobile applications banking and financials should be frozen due to the fraud I reported.

I am submitting a new app, so the subscription has to be submitted as part of the overall app review at first, I can't submit it directly on its own. I didn't know this at first, and submitted the subscription directly. It obviously got rejected with the status "developer action needed". Now no matter what I change I cannot seem to get the status to update from "Developer Action Needed" to a more favorable status. This is obviously a problem because until I can get the status to update, I cannot attach it to submit with my app. Any ideas on how to get the status on my subscription to update to "Ready to submit" so that I can attach it with my binary and submit it with my overall app submission?

Has anyone experienced something similar with App Review / App Store Connect? We ran into a very frustrating situation that is now seriously affecting our release and iteration plan. What happened: One of our subscription products was initially rejected on “value” grounds. Although we disagreed with that assessment, we removed that subscription from the latest build in order to move the review process forward. The problem is that the subscription product remained stuck in “In Review” status in App Store Connect. Because of that state, we were unable to edit, remove, or modify it from our side. App Review then rejected the app again under Guideline 2.1(b), saying the IAP attached to the submission could not be found in the binary. So the issue is basically: we already removed the product from the app as requested, but App Store Connect still keeps that product attached to review, and we have no way to remove it ourselves. Then the app gets rejected for exactly that mismatch. We explained this multiple times, attached recordings and backend screenshots, but the responses mostly repeated the same review language and pointed us to contact support. Questions: Has anyone had a subscription get stuck in “In Review” and become impossible to remove? How was it finally resolved? Did Apple manually remove it from the submission, reset the review state, or require you to withdraw and resubmit everything? This has already caused major delays to our release cycle, so any similar experience or practical advice would be greatly appreciated.