Hi there, I'm having trouble using this API: https://developer.apple.com/documentation/appstoreserverapi/extend_subscription_renewal_dates_for_all_active_subscribers It is returning a 400 response for all product IDs for my app's subscriptions: (400, 4000023, 'Invalid request. The product id parameter is invalid.') I have verified these productIds in the App Store Server UI, and using the App Store Connect API to retrieve the product IDs for all subscriptions in the subscription group. Any tips would be greatly appreciated!

Apple announced offer codes for macOS apps on June 10 2024 (see press release). However, I don't see "Offer codes" in the relevant App Store Connect subscription prices section, for my macOS-only app. See the attached screenshot. That's the menu where the link is supposed to show up. The offer codes documentation also doesn't make any mention of macOS support. Why? When will it be available, and how do I implement offer codes in my macOS app? Did I miss an announcement elsewhere? Note: I'm not looking to implement Introductory offers or Promotional offers, which are different things that don't meet our needs. .

I’m developing an app similar to Patreon where creators can decide if they want to charge either $5 or $10 a month for users to be able to view their content (each creator can only have one subscription price defined) I came across information that the only way users can subscribe to multiple subscriptions (each from a different creator) in one app, those subscriptions need to be defined in their own Subscription Group. However, it seems that Subscription Groups need to be manually, pre-defined through an online portal and go through an approval process. So the number of Subscription Groups created would have to match the number of creators. This wouldn’t scale because I need the ability for those subscriptions to be created on the fly when new creators sign up. Am I understanding that correctly? If so, how can I get around this?

Hi everyone, I'm currently testing my app's subscription feature in the sandbox environment, but I'm encountering an issue where my subscriptions are not appearing in the StoreView. I've implemented the StoreKit configurations and ensured that the product IDs are correctly set up. However, when I try to display the subscriptions in the StoreView, nothing appears. Here are a few details about my setup: I’m using StoreKit to manage auto-renewable subscriptions. The product IDs are correctly registered and match those in App Store Connect. Testing in the sandbox environment. I’ve confirmed that my internet connection is stable, and there are no apparent issues with the request. Despite this, the StoreView remains empty, and I'm unable to see any subscription options. Has anyone else encountered this problem? If so, how did you resolve it? Any help or suggestions would be greatly appreciated! Thanks in advance!

what can I use direct bank transfer for buying premium account in my app? because I found an application in the App Store that without a marker provides in-app purchases, but when the application is opened, this application offers an upgrade to a premium account to be able to access all features and the purchase process by bank transfer to the application owner's account. so now we can use our bank account directly to process payment in app without using in app purchases system by apple, right?

I'm trying to get a better handle on the user experience for a customer with an active introductory offer who upgrades to a subscription with a promotional offer. To give a contrived example: We have two annual subscription products "Regular" and "Plus" in the same subscription group. Plus is an upgrade of Regular. We offer a free trial (introductory offer) with Regular, and want to try to upsell a user to Plus (with a promotional offer) while they're still in their trial period . The documentation suggests that when the new sub is an upgrade, it triggers an immediate billing event – but in sandbox testing it seems that an existing introductory offer trial doesn't get truncated. My understanding is – if the "plus" sub offers a discounted first year via PO, the timeline would be: User acquires initial Regular subscription with free trial User acquires a Pro subscription with a discounted first year during the trial The trial isn't truncated. The user is billed the discounted "Pro" rate for their first year at the termination of the trial. If the promotional offer includes a free trial it's less clear, but I think: User acquires initial Regular subscription with free trial User acquires a Pro subscription with a second free trial The trials run back-to-back, and the user is billed at the "Pro" rate after the second trial. Is this correct? I feel like this must be documented somewhere, but I haven't found where yet.

I need some clarification from a functionality perspective. For example, in the application, a user can add a post and make it private. If anyone wants to view that post, they must pay an amount specified by the user when adding the post. This is the basic scenario. The main point of concern is price distribution. If the price of the post is $3.99, 10% of this amount goes to the app admin, and the remaining 90% goes to the user who posted the content, after accounting for Stripe's fees. My question is: We believe this functionality cannot be achieved using 'in-app purchases.' Need Assistance on this; whether scenario is achievable with 'in-app purchases'? If so, how can it be implemented?

I have accessed the third-party payment Qonversion, which has been uploaded to testflight, and some phenomena such as purchase failure or purchase waiting time out occurred when the customer used it The Qonversion developer replied that there were too many requests for this account and needed to change the account, is that right Do you need to change your account? How do you return the account? I want to know how testflight can correct the sandbox account instead of its own account

I have accessed the third-party payment Qonversion, which has been uploaded to testflight, and some phenomena such as purchase failure or purchase waiting time out occurred when the customer used it ​The Qonversion developer replied that there were too many requests for this account and needed to change the account, is that right ​Do you need to change your account? How do you return the account? I want to know how testflight can correct the sandbox account instead of its own account

My team recently implemented In-App Purchases for Non-Renewing Subscriptions and is currently testing in production. We successfully made a purchase from our app but did not receive any callback from the App Store server. Additionally, the transaction is not visible on the App Store Connect dashboard. I understand it might take a day for transactions to appear there. When we checked the transaction status via API, the "inAppOwnershipType" is "PURCHASED" and the values for other fields are as expected, except for "price." The price should be 599000, and the charged payment on the credit card is also 599000, but it appears as 599000000 in the transaction data. Any idea what could be causing this discrepancy, and is it the reason for the unsent callback? How can we fix it? Thank you.

I'm developing an iOS app that supports in-app purchases and I'm using StoreKit2 for handling transactions. While purchase, promotion, and restore purchase functionalities are working fine, I'm facing an issue with offer code redemption. When I present the offer code redemption sheet using: ``SKPaymentQueue.default().presentCodeRedemptionSheet()`` I am able to redeem the offer code in App Store sheet. It's showing success. But after offer code redeem SKPaymentTransactionObserver does not seem to receive any updates or notifications. Specifically, the paymentQueue(_:updatedTransactions:) method is not being called. public func paymentQueue(_ queue: SKPaymentQueue, updatedTransactions transactions: [SKPaymentTransaction]) import StoreKit `class YourClass: NSObject, SKPaymentTransactionObserver { override init() { super.init() SKPaymentQueue.default().add(self) } deinit { SKPaymentQueue.default().remove(self) } public func paymentQueue(_ queue: SKPaymentQueue, updatedTransactions transactions: [SKPaymentTransaction]) { for transaction in transactions { switch transaction.transactionState { case .purchased: print("Transaction Purchased") SKPaymentQueue.default().finishTransaction(transaction) case .failed: print("Transaction Failed") SKPaymentQueue.default().finishTransaction(transaction) case .restored: print("Transaction Restored") SKPaymentQueue.default().finishTransaction(transaction) case .deferred: print("Transaction Deferred") case .purchasing: print("Transaction Purchasing") @unknown default: print("Unknown Transaction State") } } } } ` So I am not able to update the UI and also not able to send the details to server. Steps I’ve Taken: Verified that the observer is added to the SKPaymentQueue in the initializer and removed in deinit. Tested on a real device, not just the simulator. Checked that the offer code is valid and properly set up in App Store Connect. Verified that the latest version of Xcode is being used. Questions: Is there a known issue with offer code redemption in StoreKit2 that might cause the observer not to receive notifications? Are there additional steps or configurations required to ensure that the transaction observer is notified about offer code redemptions? Are there any common pitfalls or troubleshooting tips for dealing with this issue? Any assistance or insights would be greatly appreciated!

how to present manage subscriptions controller like this image? this apple service controller is in-app but I used code try await AppStore.showManageSubscriptions(in: scene) but note like the image

{ "errors": [{ "status": "500", "code": "UNEXPECTED_ERROR", "title": "An unexpected error occurred.", "detail": "An unexpected error occurred on the server side. If this issue continues, contact us at https://developer.apple.com/contact/." }] }

This is the first subscription submission for this existing/distributed app. This is the rejection message: Specifically, your app did not load any subscription offers at launch and no further content could be accessed. The app works correctly in simulator, on device and TestFlight. I am using a sync'd StoreKit configuration file. The app has no functionality at all without the subscription being available to the app. It seems the app is being tested independently of the subscription upon first launch. Or said differently, the app is being tested without a subscription being available because the subscription has not been approved and available at the time the app is first launched for testing. It seems the reviewers aren't making the subscription available at the time of launching the app for testing as is the case in XCode, on device and within TestFlight - the subscription is always available in those environs. Is my analysis correct, close, a mile off or ...? Thanks for your help and insight.

I would like to implement in-app auto-renewing subscriptions to open up "Pro" options for my app if a user chooses to subscribe. The user would be able to choose from a monthly or yearly subscription version. I have looked at hours and hours of countless videos, documents, tutorials, Apple examples (Backyard Birds, etc.), and posts on all of this but I'm still not sure that I understand the correct way to do this via the "new" StoreKit 2 framework additions. From various WWDC videos, it would seem that it's now as simple as using SubscriptionStoreView and then utilizing the modifiers .onInAppPurchaseCompletion, .subscriptionStatusTask, and .manageSubscriptionsSheet. It sounded to me like everything, including purchases and verifying transactions, is handled automatically for auto-renewing subscriptions. When testing my app, I can bring up my store view with no problem and make purchases with the simulator. That being said however, I am finding it fairly difficult to understand exactly what I need to do in order to make this all work correctly. The following are questions that I need answered in order to proceed: For in-app auto renewable subscriptions, should we just be using: SubscriptionStoreView, .onInAppPurchaseCompletion, .subscriptionStatusTask, and .manageSubscriptionSheet? Does .subscriptionStatusTask automatically and continually check for subscription status changes so that views dependent on that status will know whether or not a user has a valid subscription? Do I also need to set up a task when opening my app that checks for current entitlements? Do I still need to explicitly verify transactions or devices? What is supposed to happen with the logic flow? Is it suppose to be: Check to see if user EVER had a subscription... ---- if NOT -> present the paywall/store ---- else -> present the manageSubscriptionSheet Note: When I've tested variations of this, if the user didn't have a previous subscription at some point, the manageSubscriptionSheet will not be presented. It just "clocks" with a blank screen. Sorry for so many questions. I submitted a code-level support request to get help with this but the email I received back said to just post in the forum. I'm hoping someone here can help. I have other questions also but I'll make a separate post for them. TIA.

Hi Everyone, I seem to be stuck, my app was approved and in the status of Pending Developer Release. However the subscriptions / localizations submitted along with the release, were rejected. Now the app store connect is not allowing any changes to the subscriptions or the subscription group. I have now developer rejected the release in order to try to clear the issue, but nothing I do seems to clear issue. I have tried raising tickets and calls with, App Review Support team and the Apple Developer Program Support, but was offer generic advice or told to seek help on the dev forums. I keep getting the error, "There was an error with editing your App Store localization. Try again later." and it has not been days. Can anyone please shed any light on how I can unblock the subscriptions on the App Store Connect portal.

I'm developing a multi-platform e-learning app in React Native where teachers create courses by uploading various types of content, such as videos, PDFs, Zoom meeting links, or simply by chatting with students. Students can purchase these courses via the app. However, our app has been repeatedly rejected by the App Store because digital content for mobile must be purchased through the App Store. This presents a challenge since the content our teachers upload is dynamic and varied, making it impractical to predefine all possible subscription packages. From my understanding, subscriptions or products need to be created in our App Store account first, and only then can they be fetched in our app. Is there a way for Apple to support dynamic subscription packages that can be uploaded through the app ? Any guidance on how to manage this within the App Store guidelines would be greatly appreciated.

I'm developing a multi-platform e-learning app in React Native where teachers create courses by uploading various types of content, such as videos, PDFs, Zoom meeting links, or simply by chatting with students. Students can purchase these courses via the app. However, our app has been repeatedly rejected by the App Store because digital content for mobile must be purchased through the App Store. This presents a challenge since the content our teachers upload is dynamic and varied, making it impractical to predefine all possible subscription packages. From my understanding, subscriptions or products need to be created in our App Store account first, and only then can they be fetched in our app. Is there a way for Apple to support dynamic subscription packages that can be uploaded through the app, Any guidance on how to manage this within the App Store guidelines would be greatly appreciated.

Our app is available both on the App Store and Testflight. We have a working subscription system with subscriptions that are linked to user accounts in our app. We would like to disable subscription purchases for Testflight releases. So users with an active subscription can use this subscription in Testflight, but users cannot sign up for a subscription in Testflight. Premium features would only be accessible to users with an active subscription. I think we can do this technically using something like this: let isTestFlight = Bundle.main.appStoreReceiptURL?.lastPathComponent == "sandboxReceipt" We are wondering if this is: a) Allowed by Testflight guidelines? b) Allowed by App Review guidelines? c) If there is even a better way to do this?

Hello, My app has been published and distributed on the App Store on 2024/07/24. There are four available subscriptions from within the app, belonging to the same subscription group. All four subscriptions are approved. To display the subscriptions to the users, I use the SubscriptionStoreView(groupID: String) view provided by StoreKit 2. The groupID used in my app is the same as in App Store Connect. My app has the in-app purchase capability. Everything worked perfectly during the development phase, and the team in charge of reviewing subscriptions on Apple’s side managed to view the storefront with all four subscriptions. No new build has been submitted since 2024/07/24. However, when accessing the storefront (i.e. when the SubscriptionStoreView is displayed) from the distributed app in the App Store, subscriptions are not properly shown. As per the screenshots: On 2024/07/26 @ 01:56 PM (GMT+2), there were two available subscriptions out of four when opening the store front from my iPad, and one available subscription on my iPhone, On 2024/07/26 in the afternoon, all four subscriptions were available (iPhone & iPad), but I didn’t take screenshots thinking the issue was solved…, On 2024/07/26 @ 06:25 PM, there were no available subscriptions anymore (checked on my iPhone: “Subscription Unavailable - The subscription is unavailable in the current storefront”) On 2024/07/26 @ 08:54 PM, there was a single available subscription (iPhone) On 2024/07/27 @ 08:54 AM, there were three available subscriptions (iPhone), On 2024/07/27 @ 09:43 AM, there were no available subscriptions anymore (iPhone), As of now, there still isn’t any available subscription anymore (iPhone + iPad)… I have submitted two cases to Apple Support: The first one on 2024/07/25 around 06:12 PM (GMT+2), The second one on 2024/07/26 around 06:53 PM (GMT+2), referencing the first one. No answer as of today. Because of this issue which seems to impact many other developers: I cannot communicate about the app, You cannot mend a first impression; users interested by the app who stumble across cannot subscribe, and will most likely consider the app to have some bugs, meaning they might lose trust because of an issue on which we cannot even intervene. To put it in a nutshell, this issue is seriously hindering the launching phase of the app. What is a temporary but quick solution that those of you who have (had) the same issue put in place? Is there any official answer regarding this issue? Regards, Ibi