The guidance provided only explains how to remove the entire app from review, but not how to remove a single subscription. Currently, I have one incorrect subscription that has been rejected due to localisation issues, and it is stuck in the "In Review" status. Unfortunately, I am unable to make changes to it. The correct subscription is in the "Waiting for Review" status, and while I am able to remove it, there is no need to do so. What I would like to do is remove the previous, incorrect subscription.

I'm using StoreKit together with SubscriptionStoreView to show the subscriptions in my app. I also utilize subscriptionStorePolicyDestination to show the terms of service and the privacy policy link on the view: .subscriptionStorePolicyDestination(url: URL(string: "https://www.apple.com/legal/internet-services/itunes/dev/stdeula/")!, for: .termsOfService). Everything was working fine until iOS 18.0.1. After the update, when you tap into the terms of service (or the privacy policy) link on the store view, it opens the web view by rendering the page incorrectly. Besides that, it is not possible to close the web view anymore, you have to kill the app. I already submitted a bug (FB15552274) on Feedback Assistant but I didn't hear anything back for 2 weeks. My apps are getting rejected now, because the store view doesn't have: A functional link to the Terms of Use (EULA) A functional link to the privacy policy This is really frustrating because the API was working fine but now it is broken and neither the Apple developers nor the reviewers really care if the API is broken.

The last line of StoreKit code below generates this parse/decode error in Xcode console; is this benign? Any suggestions how to fix it? [df892a08] Failed to parse status due to error: StoreKit.DecodingContext<StoreKit.Product.SubscriptionInfo.RenewalInfo.Key>.DecodingError.typeMismatch(for: [StoreKit.Product.SubscriptionInfo.RenewalInfo.Key.autoRenewalStatus], expected: Swift.Bool) Type: Error | Timestamp: 2024-11-04 11:00:53.056821-08:00 | Library: StoreKit | Subsystem: com.apple.storekit | Category: Default | TID: 0x77bc77 @Published private(set) var offeredSubscriptions: [Product] = [] // ... do { guard let anyProduct = offeredSubscriptions.first, let subscriptionInfo = anyProduct.subscription else { logger.error("\(#function): ..."); return } let statuses = try await subscriptionInfo.status // ...

I got some crashes on firebase console Fatal Exception: NSInvalidArgumentException -[NSNull length] the code stack show the StoreKit and the systems are all 18.2. I haven't update to storekit2, but it shouldn't crash for storekit1.

For auto-renewable subscriptions, it is necessary to call the transaction completion after the purchase. I understand that this needs to be called at the correct timing. StoreKit v1: https://developer.apple.com/documentation/storekit/in-app_purchase/original_api_for_in-app_purchase/finishing_a_transaction Question If the transaction does not finish for a long period, is the purchase cancelled and a refund issued? If so, how long is this period? For example case1: When I renewed the auto-renewable subscription from the OS settings app but did not open my own app. case2: When there was a malfunction in my own app. Similar forum https://developer.apple.com/forums/thread/656255

Hi, I am trying to build an app where users can upload music and sell it to other users on the app and have the money go straight to their account in such a way where stripe connect would be useful. I am wondering if I can use stripe for this or do I have to use in app purchases? If I have to use in app purchase how can i achieve this?

If I have a monthly subscription offering for an app and also a yearly subscription offering for the same app. And if I set up a win-back offer through App Store Connect on the yearly subscription offering. Will this win-back offer be shown to lapsed subscribers of both the monthly and yearly offerings? Or would it be necessary to create a different win-back offer for each offering if we want lapsed subscribers to see a win-back offer regardless of which subscription they had previously purchased? Thanks so much in advance!

in app purchase: receive a error resoponse ,the error detail is "error= Error Domain=SKErrorDomain Code=2 "无法连接iTunes Store" UserInfo={NSLocalizedDescription=无法连接iTunes Store}" , but the user paid successfullly and received a bill from apple , as a developer ,i cannot confirm the bill is real ，how dose the developer handle this user scenario 。in addition the user initiated a refund request on the app store ,but rejected by apple

App is approved and on App Store but Subscription is in review and localizations rejected. no way to edit. anyone here that go this flow resolved and how?

线上的应用突然出现大量这样的失败案例。我在feedbackassistant有提交案例，但是没有收到回复。确定这个app是已经审核过的app，确定这个商品id是审核通过的商品id，请问有什么解决办法？

Hello Apple Dev Team, I’m seeking guidance on how to ensure full compliance with the App Store Review Guidelines, specifically section 3.1.1 (In-App Purchase). In-App Purchase Mechanisms: I want to verify that my app is correctly using in-app purchases to unlock premium content, rather than alternative mechanisms. The guidelines outline various restrictions on unlocking content (e.g., license keys, QR codes, cryptocurrency). If I follow all of these restrictions, would Apple require anything else specific to prove compliance? Subscription Handling Across Platforms: Our app plans to offer a subscription service where users could subscribe on Android and then access the content on iOS with the same credentials (similar to Netflix). Users should also have the option to manage (including canceling) their subscription directly from their iOS device. Are there any specific requirements or precautions I should take to facilitate this cross-platform subscription access while remaining compliant? Restoring Purchases: I see that in-app purchases must have a restore mechanism. Could you confirm if Apple expects any specific UX or technical standards here, particularly if there are multiple types of IAPs? I’d appreciate any insights or examples from other apps that meet these requirements successfully. Thanks in advance! This should help clarify your approach, ensuring alignment with Apple’s guidelines.

I want to test in-app purchase in Sandbox environment but the SKProductsRequest method is returning invalidProductIdentifiers. When I build the app on simulator or real device including the StoreKit config file, I'm able to see the products. But, when I test after excluding the config file or from the test flight build, I'm not able to see any products. Can someone help, do we need to Sign up for Paid Apps Agreement with all the bank info and Tax forms even if we have to conduct the tests in Sandbox environment?

当verifyReceipt API被标记为Deprecated后，我尝试通过调用Get Transaction Info API查询订单信息，对用户的内购订单做校验，但是响应结果中没有支付状态，APP服务端如何才能确认用户是否已经成功支付？还有附带的问题是如何做参数透传（即用户支付时APP调用Apple服务端将开发者自定义的参数带过去，然后APP服务端调用Apple服务端API时拿到这个参数），类似google内购的developerPayload参数

In this case, I used my project project to export the ipa to testflght. The tester installed the app on the test device, started the app, and received the payment voucher information pushed by storekit. At this time, the test device did not log in to the sandbox account. Of course, The test device has previously logged into the sandbox account and successfully paid for the subscription. When I used the same test device, connected to Xcode, clicked run, and ran the app, I did not receive the payment voucher information pushed by storekit. I am very confused, why does testflight receive the certificate information pushed by storekit?

I have problems with review process for new app. Review team getting error "SKErrorDomain Code=0 unknown error" while purchase subscription. They using iPad/iPhone with iOS 17/18. Problem is not reproducible on my devices. Also on devices of testers team. I have tested debug builds from Xcode and production builds from TestFlight. So strange that same purchase code was reviewed successfully on 2 other my apps. Review team getting error only on one new app. On screenshots from review I can see product prices. I loading it via StoreKit on fly. It is mean that app found products for purchase but can't purchase. "SKErrorDomain Code=0 unknown error" how I see is not app error. It is StoreKit error. Most popular advice in internet is just resubmit build. I tried it but get back same message from review team. That should I do in this case?

Hi, I have a project in React Native, and I am using react-native-iap to load subscription products. When I use Xcode to run my app in debug mode, it lists all my subscriptions, and I am able to subscribe successfully. However, the receipt I receive is not getting validated. When I release the app on TestFlight, it does not list my subscriptions, and I am getting an empty array. I am using the useIAP hook from react-native-iap to fetch the list of subscriptions. Additionally, my app and subscriptions are not yet approved because the subscriptions are not being listed correctly.

Hello, About a month ago me and my team allocated a sprint to migrate the App Store Server Notifications service and the StoreKit library from v1 to v2. Once the implementation was completed, we started testing using the sandbox environment (which was supposed to provide greater stability and maturity in v2). The testing session went well, we managed to test various scenarios without noticing any issue (successful payment, failed payment, renewal etc). This week, before doing the production deployment, a final testing session was scheduled. Out of nowhere, we started to encounter all kinds of strange behaviours such as: StoreKit2 error (in Xcode) Received error that does not have a corresponding StoreKit Error: Error Domain=ASDErrorDomain Code=825 "No transactions in response" UserInfo={NSDebugDescription=No transactions in response} Purchase did not return a transaction: Error Domain=ASDErrorDomain Code=825 "No transactions in response" UserInfo={NSDebugDescription=No transactions in response} In some cases the transaction id resulting from the payment was retuned "" or nil, causing our server to raise an exception. Newly created sandbox account that was raising an error that says "there is already a subscription made on this apple id". Delays in the payment processing Today, without doing any code changes, we managed to test all the scenarios without encountering any issue. Due to the oscillating experience we had in the sandbox environment, we are considering postponing the release and maintaining StoreKit 1 for now, but even in this case, the fact that App Store Connect does not offer the possibility of rolling back the Notification Service to v1, causes inconvenience. Has anyone encountered something similar? Is migrating to v2 a good choice?

I'm using my sandbox account to subscribed to something. I am now trying to open the subscribed item in Settings > Apple ID > Subscriptions > Click on the active sandbox subscription > Cannot Connect. Has anyone else encountered this? How were you able to get around it?

In my app, I need the user to redeem a code outside the app and then capture the transaction in the callback/response from the App Store. How can I test this process? Here's my function for opening a URL: if UIApplication.shared.canOpenURL(url) { UIApplication.shared.open(url, options: [:], completionHandler: nil) } } I am trying to get the transaction object in the TransactionObserver class: // Implementation details... } Here is the link to this class. However, I am not receiving the expected callback in this observer. I am testing on a TestFlight build. My question is: Is it possible to test offer codes in TestFlight? Or is there something wrong with my implementation?

I'm testing subscription downgrade and upgrade cycles in sandbox, and seeing a behavior I can't explain. Code is generally similar to WWDC sample code for StoreKit2, including listening to incoming transactions. Three entitlement levels, say, Standard, Plus, Pro Corresponding subscription plans all same duration (quarterly) I go through this purchase sequence quickly, Purchase the Pro plan Before the Pro plan expires, purchase the Standard plan Still before the Pro plan expires, purchase the Plus plan Transaction.currentEntitlements after each of the purchases (logged in transaction listener), After step 1: { Pro plan } After Step 2: { (only) Pro plan } After Step 3: { Plus plan , Pro plan } I was expecting to see {Standard, Pro } in entitlements after step 2 (user entitlement calculated from the set is still correct -- Pro). If that's not the case then why after step 3 entitlements includes both Plus and Pro plans?