Can anyone please confirm that Apple-hosted Background Assets still will NOT work unless the app is: Installed from TestFlight, or Installed from the App Store Is it true Xcode-installed builds—Debug or Release—do not receive the App Store’s Background Asset metadata and cannot access the background asset packs? I am getting the error when running the app in Xcode: The asset pack with the ID “VALIDPACKNAME” couldn’t be looked up: No asset pack with the ID “VALIDPACKNAME” was found.

Hello, My app (App ID: 1616628950) is already published on the App Store, but recently we’ve been unable to install the TestFlight build for testing. The TestFlight build shows the green “Testing” status, but whenever we try to install it, we get this message: “Could not install / The requested application is not available or does not exist.” The TestFlight version is the same as the one currently live on the App Store, and the App Store version installs without any issue. I wanted to share this here in case someone from the team could check whether the TestFlight build might be stuck or misconfigured on the backend. Thank you very much for your time and help!

Need iPad Tester to Test App and Take Screenshots- I am in need of someone to willingly sign up to test my app and send me screenshots of their use from their iPad device. Sample screenshots will be provided for them to replicate. Thank you.

When i publish an internal Testflight , the app is showen in the testflight ready to Install, but if i press install , i ll get an error , can not find application . the bundle identifyer is the same. No missing contracts to sign.

When TestFlight was in public beta, the user had a mainland China account and downloaded the app from the mainland China App Store. However, when subscribing, the app displayed the message: "Your account is not available in the US App Store. You must switch to the Chinese App Store before making a purchase." In reality, the user's account region was already mainland China, and the app was downloaded from the mainland China Mac App Store. I've set all countries to be available in Connect. Has anyone encountered a similar issue? testflight公测时，用户是中国大陆的账号，在大陆appstore下载了应用。 但是订阅的时候，app提示：你的账户在美国商店中无法使用，在进行购买之前，你必须切换至中国商店。实际上，用户的账号地区已经是中国大陆，也是在中国大陆的mac appstore下载的应用。 我的在connect 中设置了所有国家可用，有人遇到类似的问题了吗？

Hi! I created a subscription class and a button that starts the purchase flow. In the Xcode environment and Simulator everything works correctly — the purchase sheet appears and the subscription flow works as expected. But when I test the app in TestFlight, the subscription button doesn’t appear at all. I cannot trigger a purchase, and I can’t find a clear tutorial that explains how to make subscriptions work specifically in TestFlight. Here is what I have already done: I created the subscription in App Store Connect I set up a Sandbox account and logged in on the device. StoreKit sync works and the product ID matches the one in App Store Connect. The same code works perfectly in Xcode Debug and Simulator, but the button is missing in TestFlight. I’m totally stuck. Can someone explain how to correctly set up and test subscriptions in TestFlight and why the subscription button would disappear even though everything works in Xcode? Any help or guidance would be greatly appreciated! THIS IS SUB CLASS @Published private(set) var products: [Product] = [] @Published private(set) var activeSubscriptions: Set<StoreKit.Transaction> = [] private var updates: Task<Void, Never>? var hasActiveSubscription: Bool { activeSubscriptions.contains { transaction in guard let expirationDate = transaction.expirationDate else { return false } return expirationDate > Date() && transaction.revocationDate == nil } } init() { updates = Task { for await update in StoreKit.Transaction.updates { if case .verified(let transaction) = update { activeSubscriptions.insert(transaction) await transaction.finish() } } } } deinit { updates?.cancel() } // MARK: PRODUCT LOADING func fetchProducts() async { do { let ids = ["test_name"] products = try await Product.products(for: ids) } catch { print("Failed to load products: \(error)") products = [] } } // MARK: PURCHASE func purchase(_ product: Product) async throws { let result = try await product.purchase() switch result { case let .success(.verified(transaction)): await transaction.finish() case .success(.unverified): break case .pending: break case .userCancelled: break @unknown default: break } } // MARK: ACTIVE SUBSCRIPTIONS func fetchActiveSubsciptions() async { var active: Set<StoreKit.Transaction> = [] for await entitlement in StoreKit.Transaction.currentEntitlements { if case .verified(let transaction) = entitlement { active.insert(transaction) } } self.activeSubscriptions = active } > ``` THIS IS BUTTON ```VStack(spacing: 8) { ForEach(sub.products) { product in PrimaryButtonView(text: mainButtonTitle) { Task { do { try await sub.purchase(product) } catch { print("Purchase error: \(error)") } } } } }```

My TestFlight uploads are stuck in processing. I tried two different uploads, and both are showing "Processing". The first one was uploaded more than an hour ago 1.1 (39) Processing Nov 17, 2025 6:54 PM 1.1 (37) Processing Nov 17, 2025 6:09 PM

Hi everyone, A new TestFlight build was not automatically updating so we deleted the old version and only have 1 new version available with a new name. This new build didn't show up either, so I stopped testing on the old version and deleted the app. I also deleted the internal testgroup and created a new one (for the new app). Despite all these actions I am not receiving a new invite email and therefor I am unable to download and test the new app. Anyone suggestions or a solution?!

Hi all, I’m currently testing an auto-renewable subscription whose availability is restricted to Japan only (all other territories disabled in App Store Connect). However, when testing in the Sandbox environment, the behavior does not match the availability settings: Sandbox Apple ID storefront: Taiwan Subscription availability: Japan only StoreKit 2 (Product.products(for:)) still returns the product Sandbox purchase succeeds even though it should be unavailable in this region. Questions Is this expected behavior in the Sandbox environment? Does Sandbox not enforce subscription territory availability? Is this a known limitation where Sandbox validates the purchase flow only, without applying real storefront availability rules? Will territory restrictions be enforced correctly in production once the app and subscriptions are “Ready for Sale”? Is there any recommended way to test storefront-based availability before release? Thanks in advance!

Hello! I'm encountering a weird issue on TestFlight/AppStoreConnect. I've builds that are in the "Processing" state since the 19th (that's 5 days ago from the date of this post). I've tried to generate new builds to see if it was just a fluke during those days, but new builds generated today also get stuck at processing. It's starting to become an issue because everybody on our team that's not a developer can't test the latest changes... Is there any way that I can get them unstuck? Thanks!

Hello, Apple Developer Community! I am attempting to test a user upgrade scenario from an existing monthly subscription to a yearly subscription, applying a Promotional Offer within the sandbox environment. When trying to process the transaction, I consistently receive the following errors from StoreKit: <SKPaymentQueue: 0x...>: Payment completed with error: Error Domain=ASDServerErrorDomain Code=3903 "Unable to Purchase" UserInfo={NSLocalizedFailureReason=Unable to Purchase, client-environment-type=Sandbox, AMSServerErrorCode=3903, storefront-country-code=USA} [...]: Finishing transaction <SKPaymentTransaction: 0x...> with no identifier Additionally, the standard dialog shown to the user displays: Unable to Purchase Contact the developer for more information. [Environment: Sandbox] My Implementation Details: Scenario: The user has an active monthly subscription and attempts to upgrade to a yearly subscription with a Promotional Offer (discount). Signature Generation: I use a custom backend written in Go to generate the signature, nonce, and timestamp. The code follows Apple’s documentation requirements, including proper encoding and formatting. Client (iOS): On the Swift side, I correctly initialize the SKPaymentDiscount and add it to the SKMutablePayment before adding the payment to the queue. The applicationUsername property is used and matches on both server and client sides. What I Have Already Verified and Ruled Out: New Test Accounts: I have created multiple fresh sandbox tester accounts in different regions (USA, Canada, Germany) and used them. Time Synchronization: The time on my server and the test device is synchronized. Parameters: Bundle ID, Product ID, and Offer ID match exactly with the configurations in App Store Connect. App Store Connect Agreements: The Paid Applications Agreement is active. Testing Environment: Testing is conducted on a physical device (iPhone), not a simulator. It seems the issue may not be related to my code but rather a potential glitch within the Apple sandbox environment itself when processing complex upgrade requests with a promotional offer. Has anyone encountered a similar issue when testing Promotional Offers? I would appreciate any help or guidance.

Hi everyone, I’m preparing an updated version of my older game Plum Nut so I can eventually return it to the App Store. I’ve uploaded a new build (1.1 build 8) and it shows up correctly in TestFlight for beta testing. However, when I try to install it on a supported device (iPad Pro 2020, iOS), I get this popup: “Could not install Plum Nut. The requested app is not available or doesn’t exist.” The build is processed and available in TestFlight, but installation always fails with this message. I have several games that install fine on TestFlight. This is the first and only case and time where I have encountered this. Details: Platform: iOS Build: 1.1 (8) TestFlight status: Available for testing Issue first occurred: Nov 18, 2025 I contacted Apple Developer Support, but they directed me to the forums for technical guidance. If anyone has encountered this issue or has suggestions on what might cause it, I would be very grateful for any insight. Thank you! — Rob / Protopop Games

I am encountering an issue where I am unable to install the app from TestFlight. The installation fails or does not proceed as expected. Please advise on how this can be resolved. I have tried restarting the device and reinstalling TestFlight and reinvite the users but the problem persists.

90714: Invalid binary. The app contains one or more corrupted binaries. Please rebuild the app and resubmit. Xcode Version 16.4 (16F6), minimum operating system iOS 17.6. 按照给出的终端命令，执行之后给出如下输出。但是我并不知道该如何进行下一步操作，代码中全局搜索也没有搜到类似@interface AUChangeSkinShell的代码或者framework，烦请您指导。 According to the given terminal command, the following output is given after execution. But I don't know how to proceed with the next steps regarding this information, We did not find any code or framework similar to '@ interface AUChangeSkinShell' in the global search of the code. Please guide us. % xcrun dyld_info -objc /Library/Developer/Xcode/Playload/EBCampus-ios.app/EBCampus-ios | grep "(null)" @interface AUUtils : (null) @interface (null) : (null) ... ... @interface (null) : (null) @interface (null) : (null) @interface AUChangeSkinShell : (null) @interface SSPBaseFormatMethod : (null)

I am experiencing a critical issue with my TestFlight builds and the App Store Connect submission process. I need urgent assistance as all my testing builds are currently expired. To fix the expiration, I increased the build number to Build 5 (Version 1.0.3) and uploaded it. I then tried to Submit for Review. The submission process failed, and I received an error message Has anyone experienced a widespread issue like this recently? What steps can I take to troubleshoot the submission error, and why would all my builds expire simultaneously, just days after a new upload? Thank you for your help!

we have uploaded only 1 app a day to testflight for the past 12 days, however for past 2 days I am unable to upload any files via transporter app, and getting the below error iOS issue : Validation failed (409) Upload limit reached. The upload limit for your account has been reached. Please wait 1 day and try again.

For the past 5 days, myself and all TestFlight users with my app have been unable to access TestFlight. When opening the TestFlight app, it immediately displays "Couldn't Load Apps" "TestFlight is currently unavailable. Try Again." If you press "Try Again" over and over for several minutes it will sometimes let you access the main install page on iPhone devices, but generally it just stays locked on "Couldn't Load Apps". On iPad, it is not possible to get to the install page. This is happening across all devices (iPad and iPhone) and OS (iOS 15 to iOS 26). User who are TestFlight testers on multiple apps are unable to access their other apps because of this issue. I've uploaded a new build and version and the issue persists. I filed a feedback assistant report: FB20901217. Has anyone else experienced a similar issue?

Hello, I created an app using the latest version of Xcode (16.2), and I'm having a problem testing this app on my iPhones. I created this app just like all the others I've made for my clients, including one on (03/24/25), but when I went to upload another App to App Store Connect on (03/26/25) I couldn't test it on my phone. Points to consider: The app runs perfectly on the Emulator. All my terms and agreements with Apple are up to date. I tried to download the apps through Testflight on 2 different devices, iPhone 7 Plus (iOS 15.8.1) and iPhone 15 Pro Max (iOS 18.3.2), and I was unsuccessful in neither attempt. I can send my app to the internal testers, but when I click download, the following message appears: Could not install [APP NAME]. The requested App is not available or doesn't exist. I imagine this problem is with Apple itself, I have already contacted support, but I need to resolve this urgently for my customers. Has anyone experienced this and resolved it?

Hi there, I am trying to publish my first app (VisionOS 2.0) via TestFlight for internal testing via XCode 16.0 beta 2. I have tried clicking both 'Distribute App' and 'Validate App', but either way receive the following error: "DVTAppStoreConnect.ServiceBackendError error 1" I am a bit stuck for now, any feedback would be gratefully received! Many thanks

I have a MacCatalyst app that is published on the Mac AppStore. All seems fine and dandy on the released version. However, when I try to test a build on my Intel based Macbook using the TestFlight app it says it's not compatible. I've looked at the build on AppStore connect and I can see that it's a universal build with x86_64, arm64 architectures. I'm at a loss as to why Test Flight reports it as incompatible yet the Mac App Store says it is compatible.