I’m trying to test a crossgrade on a subscription plan that has the same duration and price. When running tests with renewal intervals shorter than one hour, and managing or modifying the subscription, I see a payment confirmation message that says “You’ll pay X euros today.” This message is confusing because it sounds like an immediate charge, whereas my understanding is that the payment actually occurs at the next renewal, which in the test environment happens “today” due to the accelerated renewal frequency (1 hour or less). To make sure this works as expected, according to the official documentation, when testing in TestFlight the renewal frequency is 1 day. Therefore, when managing and modifying the subscription to perform the crossgrade, I would expect the UI to indicate that the payment will occur tomorrow. However, when I manage the subscription from the device’s Developer section, it indicates that the subscription will renew today, and as a result, during the crossgrade flow it again shows that I will pay X euros today. Is there any way to properly test this scenario? Or should I assume that in production the crossgrade behavior will match the documented explanation?

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)") } } } } }```

I’m having an issue installing my TestFlight build on a Mac. The build (v1.0 build 1) uploads successfully and shows as “Complete” in App Store Connect. I can also open the build details page, and my Apple ID / tester access / group setup looks correct. However, on TestFlight (macOS), when I tap Install/Load, I get this error: Unable to install. The requested app isn’t available or can’t be found. Notes: The app is an iOS app (iPhone + iPad), and I enabled availability for Mac (Designed for iPad) in App Store Connect. The Mac is Apple Silicon, running macOS Tahoe 26.1. Could you help me understand why TestFlight shows this message on Mac, and what I should change in Xcode/App Store Connect to make the build compatible?

Hi guys, I need some help with an issue. When I submit my testing app to TestFlight, it gets uploaded successfully, but I'm not able to download it from TestFlight. I'm getting this error: SDK version issue: This app was built with the iOS 18.2 SDK. Starting April 2026, all iOS and iPadOS apps must be built with the iOS 26 SDK or later, included in Xcode 26 or later, in order to be uploaded to App Store Connect or submitted for distribution. It’s obvious that we all need to update to the iOS 26 SDK before April 2026, but my question is: Why is TestFlight already blocking builds 3 months before the actual enforcement date? Is anyone else facing this issue, and is there any known resolution or workaround? Your help or suggestions would be appreciated.

please help. i've tired every solution i can find online, and believe they may be outdated in most recent version of Xcode: https://forums.developer.apple.com/forums/thread/92638 https://stackoverflow.com/questions/46216718/missing-cfbundleiconname-in-xcode9-ios11-app-release Here is the error when distributing the build to testflight -> Asset validation failed Missing Info.plist value. A value for the Info.plist key 'CFBundleIconName' is missing in the bundle 'lucaspfeiffer.sun'. Apps built with iOS 11 or later SDK must supply app icons in an asset catalog and must also provide a value for this Info.plist key. For more information see http://help.apple.com/xcode/mac/current/#/dev10510b1f7. (ID: 47b317ae-c06a-425b-9fc7-3c9e6ac9c001) Asset validation failed Missing required icon file. The bundle does not contain an app icon for iPhone / iPod Touch of exactly '120x120' pixels, in .png format for iOS versions >= 10.0. To support older versions of iOS, the icon may be required in the bundle outside of an asset catalog. Make sure the Info.plist file includes appropriate entries referencing the file. See https://developer.apple.com/documentation/bundleresources/information_property_list/user_interface (ID: 362522bf-f96c-4cf2-99b6-8d984ef546b8) Asset validation failed Missing required icon file. The bundle does not contain an app icon for iPad of exactly '152x152' pixels, in .png format for iOS versions >= 10.0. To support older operating systems, the icon may be required in the bundle outside of an asset catalog. Make sure the Info.plist file includes appropriate entries referencing the file. See https://developer.apple.com/documentation/bundleresources/information_property_list/user_interface (ID: 9c5a2bcf-36ae-42bf-80fe-705dbe6e85d7)

I am unable to install my app via TestFlight.When I tap Install in TestFlight, I receive the following error message: “Could not install xxx. The requested app is not available or doesn’t exist.” The app is visible in TestFlight, but installation always fails. I would appreciate your help in identifying the cause.

tried all sorts of things and lots of recommendations from "ChatGPT" (boo... yeah sure it is going to take all of our jobs by just guessing at wrong answers... we can do that ourselves, haha) which yielded no answer. we are trying to change the app name but it keeps showing the old name in Test Flight. app shows proper name when installed on device from test flight. yes we are changing the "cf bundle display name" ... i did try deleting test flight and re-installing it, and also deleting app and re-installing it from test flight. still shows old name in test flight. this is a branding issue, the client wants to see the new name. how to fix this?

Hello, I was just installing an app from TestFlight that has an Essential Asset Pack that's a few GBs in size. It appears the Call To Action inside of TestFlight doesn't take into consideration the Background Asset download status before it changes from Installing to Open. I can't test if this is also the case for apps on the App Store, but I'd expect that it is.

On my latest build I have 15 "pannes" French word for crash with ZERO session. It was the same for the previous build (2 days before): zero session and 498 "pannes" (crash). How is that possible ? And in Xcode/Organizer : No crash logs since 2 weeks. Who can it be possible ?

I’m hitting a persistent conflict between my Business (Managed) Apple ID and my personal Apple ID when trying to use TestFlight. My Business ID is correctly tied to App Store Connect, but the device always forces TestFlight to associate with my personal Apple ID. When I try to “Review” the Business ID in the App Store, I get the endless loop: “This Apple ID has not been used in the iTunes Store.” The review flow never completes. What I’ve already confirmed: Business/Managed Apple IDs cannot be activated for the App Store -Signing out of Media & Purchases doesn’t fix it -Tried on multiple devices - sign out - same behaviour -TestFlight still forces a personal Apple ID login even when everything else is configured correctly This looks like a reproducible conflict introduced by recent Apple updates, and it’s affecting Managed/Business Apple IDs across the board. Developer Support hasn’t provided a single actionable response despite multiple tickets which is unacceptable for a paid service. Has anyone found a reliable workaround solution for this problem ? THANK YOU in advance !!

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, I uploaded two builds to App Store Connect today, but they have been stuck in "Processing" status for 10 hours now: Build 1.0 (10): Uploaded at Jan 14, 2026 5:03 AM - still Processing Build 1.0 (9): Uploaded at Jan 14, 2026 4:23 AM(UTC+8) - still Processing Usually my builds complete processing within 10-30 minutes. Is there a known issue with build processing today, or is there something I should check on my end? Any help would be appreciated. Thanks!

Based on the status page, the servers seem to be operating as they should... this has never been an issue before. It is usually uploaded in minutes. Need help. This is supposed to be my final step before being ready for release.. arghh

Hi all, We can’t install our app from TestFlight. The app is visible in TestFlight for invited internal testers, but tapping Install fails immediately with: “The requested app is not available or doesn’t exist.” --Setup-- Distribution: TestFlight – Internal Testing Internal group created and testers added (invite accepted) Build processing status in App Store Connect: Complete TestFlight build status shows: Ready to Submit / Prepare for Submission Minimum iOS deployment target: iOS 15.0 Version/Build: 1.0.0 (1) What we tried Confirmed tester is signed into TestFlight with the same Apple ID email that was invited Removed/added testers to the internal group and resent invites Reinstalled TestFlight, signed out/in Verified build is assigned to the internal group Set and saved Monetization → Pricing and Availability → App Availability (All Countries/Regions) Question Has anyone resolved this issue? Is there a known TestFlight/App Store Connect stuck state that causes this error even for internal testing? Any recommended steps (new build number, group reset, availability/pricing settings, etc.)? Screenshots available (TestFlight error + App Store Connect build/group view). Thanks.

Keep getting an error saying the tester has 'an invalid name or email address and wasn't added'. Never had this problem until maybe 1 - 2 days ago. Please fix I am unable to publish new builds to my early access users.

Hi everyone, I'm experiencing an issue with TestFlight where internal testers are not receiving build invitations, even though the builds have successfully completed processing in App Store Connect. Builds Status: • Multiple builds (Build 10, 11, 12) show "Ready to Submit" status in App Store Connect • Build 9 is in "Waiting for Review" status • All builds show "2 Invites" sent • However, the new builds (9, 10, 11, 12) are not appearing in TestFlight for the internal testing group Internal Testing Group: • Group name: "Test" (Internal Group) • 2 Testers configured • 7 Builds total in the group • The group shows builds 1.0 (2) through 1.0 (8) as "Testing" status • New builds (9, 10, 11, 12) are missing from TestFlight What I've Tried: Manually adding the internal group to the new builds using the "Add Group" dialog(the Add button is inactive) The system shows "2 Invites" sent in App Store Connect Checked TestFlight app on testers' devices - no new builds visible Waited more than 1 hour after builds completed processing Expected Behavior When adding an internal testing group to a build in App Store Connect, testers should: Receive push notifications about the new build See the new build available in their TestFlight app Be able to install and test the build immediately Actual Behavior • App Store Connect shows invitations were sent (2 invites) • TestFlight does not show the new builds (9, 10, 11, 12) • Internal testers have not received any notifications • Only older builds (2-8) are visible in TestFlight Additional Context • This issue started occurring today (January 15, 2026) • Yesterday, I experienced extended build processing times (builds stuck in "Processing" for several hours), which appears to have been a widespread issue affecting multiple developers • Once processing completed, the builds moved to "Ready to Submit" status normally • The internal testing group worked fine for previous builds (2-8) Questions Has anyone else experienced this issue with TestFlight internal testing today? Is there a known delay between adding a group in App Store Connect and builds appearing in TestFlight? Could this be related to the processing delays that occurred yesterday? Is there a way to manually trigger the invitation/notification system? Any insights or suggestions would be greatly appreciated. This is blocking our internal testing workflow. Thanks in advance!

今天上午开始TestFlight一直都是processing。

Hello, My TestFlight build (version 1.0.4, build 10) shows as "Complete" in App Store Connect but does not appear in TestFlight. here is the link: https://drive.google.com/file/d/1su6cXk35X4bx2uzLW7aXIliAKKNfDYAe/view?usp=sharing Multiple uploads were attempted, and earlier builds processed successfully. Thank you.

Have had issues all day with the delayed Processing times as seen by other posts on this forum. But after my app has completed Processing (took 4 hours, usually takes 10 minutes), the build doesn't show up for Internal Tester. Internal tester usually gets all app updates, but when I try to add Group to build, the internal tester group is greyed out. If I try to add individual tester to build I get "An error has occurred. Try again later."

Hello everyone, I successfully submitted my iOS app build to App Store Connect via EAS(expo.dev). The submission logs confirm successful upload, but the build is not visible in App store connect TestFlight → Builds after several hours. Submission was successful according to logs: "Successfully uploaded package to App Store Connect" and "The app has been submitted successfully." Has anyone experienced a problem with this? Can I get some information? Thank you.