I've been trying to make my app available on the App Store for a month now, but I can't because the signatures I created don't appear in the sandbox app. I did all the configuration in the store and in the app. I tested the same code in another app with signatures and it was loaded, but the signature for that specific app doesn't appear. I've tried contacting Apple support, but they can't help me. It almost seems like it's on purpose. I'm treated like crap and they don't even give me an explanation about what's happening. Can anyone help me?

Our app is getting rejected because they can not find our lifetime offering in app purchase. We added it as a test, but now would like to remove it from App Store connect, but in the UI on the website, I see no option to remove it. It has been "In Review" for a while. We marked it as "Remove from Sale", but we are still getting rejected. Any advice?

I just want to add a in-app purchase project to my app, steps: 1.i create a product in App Store Connect ,the product id is "com.buy.once.me" 2.in Xcode,i create " SubscriptionStoreView(productIDs:["com.buy.once.me"])" in a view 3. the view show "subscription unavailable the subscription is unavailable in the current storefront" I don't know what the problem is ,anyone help me,thanks

Hi everyone!, I would love your help with this please as I have been stuck for days with no solution. Issue: I'm trying to enable In-App Purchases (IAP) in my app, but my provisioning profile does not include the com.apple.developer.in-app-purchase entitlement. When I attempt to build in Xcode, I see the following error: Provisioning profile "iOS Team Provisioning Profile: org.thewhiteowl.mindflow" doesn't include the com.apple.developer.in-app-purchase entitlement. I've already verified my Apple Developer account, and Apple Support confirmed that everything looks correct from their end. Steps Taken So Far: Verified In-App Purchases is Enabled in the Apple Developer Portal under Certificates, Identifiers & Profiles → Identifiers. Accepted All Agreements in App Store Connect → Agreements, Tax, and Banking (everything is marked Active). Created a New Provisioning Profile Manually: . Go to developer.apple.com . Navigate to Certificates, Identifiers & Profiles . Click "+" to register a new provisioning profile . Choose App Store Connect → Click Continue . Select App ID → MindFlow App (PM7JVFLCVC.org.thewhiteowl.mindflow) → Click Continue . Select Certificate → The White Owl LLC (iOS Distribution) (Valid until Feb 22, 2026) → Click Continue . Enter Provisioning Profile Name: "MindFlow Distribution" → Click Generate . Download the profile and inspect the Entitlements section ❌ The In-App Purchase entitlement is missing (com.apple.developer.in-app-purchase does not appear). Additional Troubleshooting: . Tried regenerating the provisioning profile multiple times . Deleted & reinstalled Xcode completely .Ensured App ID is Explicit (not Wildcard) . Tried refreshing App ID capabilities by toggling other entitlements . Checked for misconfigurations in Expo and EAS (using Expo.dev for deployment) Questions: Why is the In-App Purchase entitlement missing from the generated provisioning profile? Is there a way to force the entitlement to appear? Could this be an issue with the Apple Developer Portal, and if so, is there a workaround? Any help or insights would be greatly appreciated! 🚀

Some of my users reported they can not completed the purchase . According to the logs and screen captures . Their purchase progress's last status are "purchasing" func paymentQueue(_ queue: SKPaymentQueue, updatedTransactions transactions: [SKPaymentTransaction]) { .... .... case .purchasing: // 处理正在购买的情况 //print("购买中"); AppDelegate.log.debug("paymentQueue purchasing"); LoadingAlert.shared.setText(text: "购买中".localized()) .... After this ，It neither entered any error branch nor prompted the user to confirm the purchase or enter a password, but simply stopped here. There are no other purchase-related logs, and the program is still running normally. At the same time, other users are able to complete their purchases without any issues. However, there have been 4-5 users recently who reported problems with purchasing. What could be the possible reasons? In my local environment, I repeated the test many times, including using sandbox users from different regions and real Apple IDs, and everything worked fine. // // Payment.swift // RadialMenu // // Created by pat on 2023/6/26. // import Foundation import StoreKit class Payment:NSObject,SKProductsRequestDelegate,SKPaymentTransactionObserver{ func paymentQueue(_ queue: SKPaymentQueue, updatedTransactions transactions: [SKPaymentTransaction]) { for transaction in transactions { AppDelegate.log.debug("paymentQueue transaction product = \(transaction.payment.productIdentifier) state = \(transaction.transactionState)"); //let productID = transaction.payment.productIdentifier switch transaction.transactionState { case .purchased,.restored: if(transaction.transactionState == .purchased){ AppDelegate.log.debug("paymentQueue purchased"); LoadingAlert.shared.setText(text: "已购买".localized()) } if(transaction.transactionState == .restored){ LoadingAlert.shared.setText(text: "已恢复".localized()) AppDelegate.log.debug("paymentQueue restored"); } //} break; case .failed: AppDelegate.log.debug("paymentQueue failed "); if let error = transaction.error as? NSError { // 获取错误代码和描述 let errorCode = error.code let errorDescription = error.localizedDescription AppDelegate.log.debug("paymentQueue Transaction failed with error code: \(errorCode), description: \(errorDescription)") } queue.finishTransaction(transaction) LoadingAlert.shared.hideModal(); // 处理购买失败的情况 // 提供错误信息给用户 //print("购买失败"); alertRetry(); break; case .deferred: AppDelegate.log.debug("paymentQueue deferred"); LoadingAlert.shared.setText(text: "购买延迟".localized()) // 处理交易延迟的情况（仅限家庭共享） break; case .purchasing: // 处理正在购买的情况 //print("购买中"); AppDelegate.log.debug("paymentQueue purchasing"); LoadingAlert.shared.setText(text: "购买中".localized()) break; @unknown default: AppDelegate.log.debug("paymentQueue nknown default\(transaction.transactionState)"); break } } }

User Initiated a Single Consumable Purchase but Was Charged Twice A user initiated a single in-app purchase for a consumable item, but they were charged twice. Both transactions have the same purchase token. Additional details: After the user successfully completed the in-app purchase, the completeTransactions callback was triggered again. This was called at app launch using SwiftyStoreKit.completeTransactions to finish any pending transactions. Could this be causing the duplicate charge? Any insights would be appreciated.

Hi everyone, I’m developing an app for managing internet services, which includes features like controlling modems, paying internet bills, purchasing internet packages, buying cameras, subscribing to FSafety (modem management), UltraFast (boosting internet speed for gaming), and selling health-related devices like blood glucose monitors, as well as other telecom-related products. I have some questions about Apple’s review process and payment policies: Do features like paying internet bills, buying internet packages, purchasing cameras, subscribing to FSafety and UltraFast violate any of Apple’s policies (App Store Review Guidelines)? If my app doesn’t violate any policies, how would Apple charge for these transactions, and what is the fee structure? If I use an external payment gateway (not Apple’s) for transactions like paying bills or buying products, would I need to provide additional documentation for my app to be approved on the App Store? What is the review process for apps with external payment features? Is there anything special I need to do when submitting the app to the App Store? I would appreciate any insights from those who have experience with developing apps that include payment functionality. Thanks so much!

users download app with Streamlined Purchasing ,but the logic of checking subscription doesn't work. there the code: func checkSubscriptionStatus() async { for await entitlement in Transaction.currentEntitlements { guard case .verified(let transaction) = entitlement else { continue } if transaction.productID == monthlyProductID || transaction.productID == yearlyProductID { if transaction.revocationDate == nil && !transaction.isUpgraded { let activeSubscribed = transaction.expirationDate ?? .distantFuture > .now if activeSubscribed { hasActiveSubscription = activeSubscribed // other operation } } } } }

Having a hard time understanding what to use to setup membership plans for a social app (think tinder) that has 3 and 5 years access for one-time use (or even if we allow multi-use but one at a time). The maximum subscription length I see is 1 year so that is out. For non-consumable it says that is lifelong which is problem as plan lengths are 3 and 5 years access only. We are not giving life long access with these plans. So consumable seems to allow the time duration IPA needed. Is this correct? An if it matters this is multi-platform app where users login with their email/pass to android / iOS / our website.

有人遇到这个问题吗,在支付的时候提示未知错误,具体的错误信息如下: 交易失败,outTradeNo:2025022631999900326, productId:com.f6car.p0001, error:Err-or -Domain=SKErrorDomain Code=0 "发生未知错误" UserInfo={NSLocalizedDescription=发生未知错误, NSUnderlyingError=0x302f50120 {Error Domain=ASDServerErrorDomain Code=3512 "无效的应用程序外部版本。" UserInfo={NSLocalizedFailureReason=无效的应用程序外部版本。}}} 寻求解决方案,感谢.

I am working on a banking application (includes iPhone and iPad) which includes add to wallet feature. During the implementation I saw one document it is mentioned that for iPad app, the app must be extended to support Apple pay functionality. Details from document says "Card Issuers with an iOS mobile banking app must support Card Issuer iOS Wallet extension functionality to enable Card issuer mobile app customers to provision new cards directly from the iOS Wallet app with all eligible Apple iOS devices. If the Card Issuer has a dedicated iPad App, that App must be extended to support Apple Pay functionality. " Is wallet extension implementation required for Apple pay to work in iPhone and iPad? Is wallet extension a mandatory implementation for Add to Apple Wallet feature to work and approved by Apple? I am little confused in this. Anyone who integrated Apple pay or done add to Apple Wallet feature recently without wallet extension faced any rejection? Any help would be much appreciated.

Hello, I recently received feedback from two users that they charged twice after entering their password when trying to initiate payment on the app. I checked my front-end and back-end codes, both of which only initiate one order, but I don't know why the user deducts two payments after entering the password. I hope everyone can help me analyze this problem and how it came about? Additionally, I wonder if there is a possibility that the system may prompt the user to enter their password again due to network issues, resulting in the deduction of two payments. But the user told us that they only entered the password once (I don't know if the user lied). I am unable to find how the problem arose. I hope you can help me analyze how to solve this problem? If you also encounter such a problem, can you teach me how to solve it?

I am trying to implement in-app purchases in Apple TV. I added a "non-consumable" product and started testing in Sandbox, but it did not work properly. While I am trying to fetch the product from the appstore, it won't give any responses like success or failure. So that our app gets rejected in the App Store. Please provide me the steps to implement in-app purhcase in Apple tvos using Swift. Note: The same code is working fine in iOS.

I read the documentation and it told I had to prepare the product on App Store connect and once it is at the state "Ready to submit" I could access it on a phone where I am connected with an Icloud account in the developper list of the apple development account. This is what I've done but when I try to fetch in my flutter code the product with the id I set in App Store connect it says "No product found" Here is where I fetch the product: Future purchaseProduct(String productId) async { try { Set<String> _pIds = {productId}; final ProductDetailsResponse response = await _iap.queryProductDetails(_pIds); if (response.productDetails.isEmpty) { throw 'Product not found'; } final ProductDetails productDetails = response.productDetails.first; final PurchaseParam purchaseParam = PurchaseParam(productDetails: productDetails); _iap.buyConsumable(purchaseParam: purchaseParam); } catch (e) { Services.debugLog('Error purchasing product: $e'); throw e; } } I checked the product ID and it does not seems to be the problem. Is there some other steps I need to do ?