Hi, I’m experiencing a TestFlight issue affecting multiple apps in my account. Issue summary: • Several TestFlight builds across all of my apps expired at the same time. • After uploading new replacement builds, neither I nor my testers are able to install them. • Installation fails with the message: “Could not install {App Name}. The requested app is not available or doesn’t exist.” • The build shows as processed and available in App Store Connect. • Testers are already invited and active. • No redeem code is required. I am seeing the same issue on my own device as well. What I’ve tried: • Uploading new builds (incremented version + build number). • Confirmed builds are visible and available in App Store Connect. • Removing and re-adding testers. • Logging out of the app. • Deleting the app from the device. • Restarting the device. • Reinstalling directly from TestFlight. • Restarting TestFlight. Despite this, installation consistently fails with the “requested app is not available or doesn’t exist” error. Expected behavior: • New TestFlight builds should be installable once processed and available. • Testers (and the developer) should be able to install directly from TestFlight. • Expired builds should not block installation of newly uploaded builds. Additional context: • This started immediately after multiple TestFlight builds expired across my apps. • All affected apps were previously installing and testing without issue. • Apple Developer Support has been contacted, but I wanted to check whether others are seeing the same behavior or if there is a known workaround. Has anyone else encountered TestFlight builds becoming unavailable across multiple apps at once, or an install failure after replacing expired builds

Hi, I'm completely blocked from TestFlight. Every attempt returns: "status": "422", "code": "BETA_CONTRACT_MISSING", "title": "Beta contract is missing for the app." This is an older account that has used TestFlight fine before. Nothing changed on my end, no account changes, no agreement updates. What I've already checked: Business > Agreements: Paid Apps and Free Apps both Active Tax forms and bank account Active No pending banners anywhere in App Store Connect or developer.apple.com Test Information complete Export compliance answered Build processes to VALID with no warnings Same error on a brand new app with a fresh build, so it looks like the beta contract is detached on the backend rather than an app-level problem. I've filed a support request and haven't heard back. This is time sensitive, I have a client pilot waiting on an external TestFlight link. Is there any way to get this re-provisioned? Apple Support case ID: 20000118605424 Thanks.

Hello everyone, I’m a small/private developer working on MacPad Mobile, a native plain-text editor for iPhone and iPad. It edits files directly through Apple’s Files interface and requires no account or sign-in. I’m looking for a small number of TestFlight volunteers to help investigate an occasional performance issue. On some devices, the first folder transitions and the first opening of an iCloud Drive file can be noticeably slower than subsequent attempts. If you have approximately 5–10 minutes, I would particularly appreciate results from older iPhones, recent iPhones, and iPads. Suggested test: Leave the app unused for a while before beginning. Open a disposable plain-text file from iCloud Drive. Note whether navigating the first few folders feels slow. Note the delay between selecting the file and seeing its text. Repeat the same route and report whether it becomes faster. If possible, compare it with a file stored under “On My iPhone” or “On My iPad.” Please use disposable test files and avoid including private filenames, document contents, account details, or personal folder information in screenshots or feedback. Feedback can be submitted directly through TestFlight. Including the device model, iOS/iPadOS version, storage location, and whether the first and repeat attempts differed would be especially helpful. TestFlight link: https://testflight.apple.com/join/GhDzjNmj I know many people here have considerably more experience with Apple-platform development, so I’m also grateful for any advice about measuring Files-provider and iCloud latency correctly. I'm not very sure to do that everything correct. Thank you for your time and for any help you’re willing to provide. Best regards Frank

Hello, I am unable to use TestFlight for any app (existing or new), while production uploads work normally. All TestFlight actions fail with: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING There are no pending agreements in App Store Connect. This is an older account that previously used TestFlight successfully. This appears to be a missing or detached TestFlight Beta contract on Apple’s backend. Could this be manually reattached or re-provisioned? This is time-sensitive, as I need a TestFlight external testers link to submit an app for an upcoming hackathon. Apple Support case ID (for reference): 102817552619 Thank you.

Hi Apple Developer Support team, We are encountering a validation failure when uploading an iOS app build to App Store Connect. The upload fails with the following error: Validation failed This bundle is invalid. The value provided for the key MinimumOSVersion '12.0' is not acceptable. (ID: 9a27ff00-bf7c-4c8d-9980-f11f7ea6430f) Additional error details: Error Domain=IrisAPI Code=-19241 "Validation failed" UserInfo={ status=409, detail=This bundle is invalid. The value provided for the key MinimumOSVersion '12.0' is not acceptable., id=9a27ff00-bf7c-4c8d-9980-f11f7ea6430f, code=STATE_ERROR.VALIDATION_ERROR, title=Validation failed, NSLocalizedFailureReason=This bundle is invalid. The value provided for the key MinimumOSVersion '12.0' is not acceptable., NSLocalizedDescription=Validation failed } Our app’s deployment target is set to iOS 12.0, and the generated bundle contains: MinimumOSVersion = 12.0 This value has been accepted in previous uploads, but the latest upload was rejected during validation. Could you please help confirm: Is iOS 12.0 still an acceptable minimum deployment target for newly uploaded iOS app builds? Has there been any recent App Store Connect validation rule change related to MinimumOSVersion? Are there specific bundle types, SDK versions, or build settings that may cause MinimumOSVersion = 12.0 to be considered invalid? Any guidance would be appreciated. Thanks.

Hi, I’m running into a persistent issue in App Store Connect related to TestFlight and app reviews, and I’m hoping someone has seen this before. Around two weeks ago, I started getting the following error when trying to create external TestFlight builds: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING Since then: I cannot create any external TestFlight tests Internal TestFlight builds appear, but cannot be downloaded (“The requested app is not available or doesn’t exist”) My apps do not progress properly through review One app got stuck in “In Review” for ~10 days; I eventually withdrew it and resubmitted it At this point, I cannot update two existing apps, and I can’t start testing a new app at all Important details: This is an individual developer account I am the Account Holder All contracts appear active and valid The issue affects multiple apps, not just one Nothing changed on my side (no contract updates, no account changes) before this started happening. I’ve already reached out to Apple Developer Support multiple times, but unfortunately haven’t received any response so far, which makes it unclear how to proceed. Has anyone experienced this issue or found a resolution? Any insight would be greatly appreciated. Thanks!

I am trying to add testers to External Tester groups for a couple of our iOS apps and after adding them it shows "No Builds Available". This is despite the app being available to that External Tester group with other people having already installed the latest version of the app which is "Available" and not expired. Can someone please fix this? It is so frustrating the number of times I try and release apps to TestFlight and there's some issue blocking me, completely out of my control and I have to rely on someone at Apple fixing something on this terrible AppStoreConnect system.

With reference to this post on the Apple Developer Forums: Apple Developer Forums thread We are extremely disappointed with the way this issue has been handled by Apple Developer Support. For the past 10 days, we have been receiving essentially the same response: “We are checking.” Unfortunately, there has been no meaningful progress or resolution from Apple's side. Our applications are dependent on Apple's services, including TestFlight and App Store Connect, and these issues are directly affecting our ability to test, distribute, and move forward with our applications. Given the critical nature of these platforms for developers and businesses, the apparent lack of urgency and ownership in resolving the issue is highly concerning. What is particularly frustrating is that every 48 hours, we are asked to wait for another 48 hours. This cycle has continued repeatedly without any concrete update, explanation, or progress. We understand that certain technical issues may require time to investigate and resolve. However, after 10 days, repeatedly receiving the same response without transparency, escalation, or a clear timeline is simply unacceptable. We expect this matter to be treated with the seriousness and urgency it deserves. Our business and application delivery are dependent on these services, and the continued delay is causing significant disruption. We sincerely request that this issue be properly escalated and that we receive a clear update on the root cause, the current status of the investigation, and an expected timeline for resolution.

Hi everyone, I’m looking for external TestFlight testers for Personal Finance, a SwiftUI app for managing accounts, payment cards, investments, and personal budgets in one place. The app does not connect to banks. Users enter and manage their financial information manually, and the data remains on the device. The current beta includes: • Account, card, and investment balance tracking • Personal budget calculations with recurring and one-time items • Automatic balance updates for card payments • Home Screen widgets for balances and budgets • Direct links from widgets to the relevant editing views • Optimized layouts for both iPhone and iPad • Finnish and English language support I would especially appreciate feedback on: • Overall usability and clarity • Calculation accuracy • Adding and editing financial information • Widget installation and behavior • iPad layouts in portrait, landscape, and Split View • Missing features or confusing workflows • Crashes, data issues, and visual bugs Public TestFlight link: https://testflight.apple.com/join/BZgZNnhn Feedback can be submitted directly through TestFlight. Thank you to anyone willing to try it and share their experience.

Hi — I’m getting Burden ready for its first App Store release and could use a few outside testers. Burden is for the moment when a purchase looks affordable, but you still want to know what it leaves you before payday. You can run a quick check to see the real cost over time, or a full check using upcoming bills, essentials, and the balance you want to protect. It then gives a pressure score from 0 (least strain) to 100 (most strain) and shows the numbers behind the recommendation. I’d especially appreciate feedback on: • whether the first-use tutorial is clear • whether the score direction makes sense • whether the recommendation matches the numbers entered • confusing wording, layout problems, or bugs • whether you would open it again for another purchase Burden does not connect to your bank. Detailed cash and bill inputs stay on your iPhone. TestFlight: https://testflight.apple.com/join/ze5Bhrkc Feedback here or through TestFlight is welcome. Thank you.

Developer here, sharing a public TestFlight link for feedback. Rückenwind is a bike navigation app for iPhone. The idea: show what's ahead, not just where to turn. The route is coloured by gradient — green flat through to red steep — and while riding you tap or swipe between four cards: turn instruction, elevation profile with your position, next climb (category, metres left, avg/max gradient) and wind relative to your heading. Other things worth testing: Offroad button — one tap mid-ride reroutes onto tracks and forest paths from your current position Surface breakdown before you start (tarmac, gravel, sand) Arrival times learnt from your own recorded rides instead of a flat assumption Service points announced by voice: "in 700 metres, drinking water" Power-saving mode: map off, screen dimmed, guidance keeps running Offline maps saved automatically along the route Live Activity on Lock Screen and Dynamic Island, plus an Apple Watch app German and English, follows the system language Technical side, in case it's of interest: SwiftUI and MapKit with custom tile overlays, BRouter for routing and elevation, ActivityKit for the Live Activity, WatchConnectivity for the watch app, and a small tile proxy so no API key ships in the binary. TestFlight: https://testflight.apple.com/join/QJcbg3s9 More: https://rueckenwind.piepgras.de/en.html What I'd like feedback on: does the turn card stay readable at a glance while moving? Is the Live Activity useful or noisy? Anything that feels off in the watch app? Requires iOS 17.

People have been abusing TestFlight's trusted distribution to distribute apps. Apple needs to improve their automated testing and maybe get human reviewers involved. Even a glance at the name or logo would raise flags. This comes from official Apple's testflight email, the logo, name is all Trademark ripoff.

Am same facing Storekit issue 0 product returns in Product identifier Array. Even i test on device it returns invalid product identifier due to 0 product array. Issue Description Step 1 Create a new Auto-Renewable Subscription from the App Information page in App Store Connect. Step 2 Complete all the required fields for the Auto-Renewable Subscription and click the "Save" button. Expected Result After saving, the subscription status should change from "Prepare for Submission" to "Ready to Submit". Actual Result The subscription status remains "Prepare for Submission" and does not change to "Ready to Submit", even though all required information has been completed and the subscription has been saved. I am currently facing a critical issue while creating an Auto-Renewable Subscription in "App Store Connect". I have already completed all the required subscription details. However, whenever I click the "Save" button, the subscription status does not change from "Prepare for Submission" to "Ready to Submit", as expected. Because the subscription never reaches the "Ready to Submit" state, every purchase attempt in the Sandbox environment fails with the following error: SKErrorDomain Code = 3 "Invalid Product Identifier" To troubleshoot the issue, I have already: Created multiple new Product Identifiers, but every identifier is reported as "invalid" in the Sandbox environment. Verified that my "Banking, Tax, and Paid Applications Agreement" is complete and active. Confirmed that all required fields for the Auto-Renewable Subscription have been filled in before saving. Since I am unable to submit the subscription for review and all Product Identifiers remain invalid, I believe there may be an issue with my App Store Connect configuration or account. I would appreciate it if you could investigate this issue and help resolve it as soon as possible, as it is currently blocking the implementation and testing of in-app purchases.

Hi everyone! I’m looking for external TestFlight testers for Kauppalista, a simple iPhone shopping list app that I’m currently preparing for its first public release. The app is available in English and Finnish. Kauppalista is designed to make everyday grocery shopping easier. You can: Save frequently purchased products and their preferred stores Organize your shopping list automatically by store Change quantities and stores while shopping Mark individual items or all items in a store as purchased Quickly add recently and frequently purchased products Get suggestions based on your actual purchase rhythm Reorder stores and products to match your usual shopping route Share your shopping list Use the app in English or Finnish I’m especially interested in feedback from people who are willing to use the app during a real shopping trip, rather than only trying it for a few minutes. I’d particularly like to know: Is anything confusing or difficult to discover? Does anything require too many taps? Are the shopping suggestions useful? Does organizing products by store work naturally for you? Did you encounter any bugs or unexpected behavior? Is there something you expected the app to do but couldn’t? Are there any problems with the English translations? The app does not require an account or sign-in. TestFlight: https://testflight.apple.com/join/HN5mehXp This is my first public beta, so feedback about the overall usability is particularly valuable. Thanks for testing! Feedback through TestFlight or here on the forum is very welcome.

Hello, I cannot submit a build for TestFlight external (Beta App Review). The UI shows a generic error; the API returns 422 ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING. There is no pending agreement I can accept. App / account App: Siteopya Bundle ID: com.siteopya.mobile Version / build: 1.0.0 (15) — processing Complete, status Ready to Submit Platform: iOS Team ID: 6L5F59LRS7 Enrollment: Individual (I am the Account Holder) Membership: Active, renewal 25 Aug 2027, auto-renew On Agreements (all accepted / Active) Apple Developer Program License Agreement — accepted 24 Aug 2026 Apple Developer Agreement — accepted 23 Aug 2026 Free Apps Agreement — Active Paid Apps Agreement — Active Bank account — Active Tax forms (W-8BEN) — Active No yellow “Review Agreement” banner on developer.apple.com/account What works Uploading builds (12–15) completes normally Build 15 appears in TestFlight as Ready to Submit Build 15 is already assigned to the internal group What fails External group → Select build 15 → Submit for Review POST https://appstoreconnect.apple.com/iris/v1/betaAppReviewSubmissions 422: { "errors": [{ "id": "c1bcfddb-7bc5-4a17-a5c7-5363928b2afe", "status": "422", "code": "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title": "Beta contract is missing for the app.", "detail": "Beta Contract is missing." }] } Internal testers: install fails in the TestFlight app “Couldn't install Siteopya. Try again later.” “Couldn't install Siteopya. The requested app is not available or doesn't exist.” Support cases (no reply yet) Case ID: 20000151012553 Case ID: 102951050062 Opened: 1 Sep 2026 Could an Apple engineer please re-attach / re-provision the TestFlight Beta Contract for this app? There is nothing pending on my side. Thank you.

We're testing In-App Purchases for our app distributed via TestFlight, using Sandbox Apple Accounts. We observe two device-dependent behaviors and have two questions. (App-specific details, including the bundle ID, are in our Feedback report FB24632077.) Observation 1 — Consumable second purchase fails with DuplicateTransaction on some devices The first purchase of a consumable succeeds and the transaction is finished. A second purchase of the same consumable then fails with PurchaseFailureReason.DuplicateTransaction ("This In-App Purchase has already been bought") on some devices. It correlates with sandbox session persistence: on devices where the purchase prompts for password only (e.g., iOS 26.x, iPadOS 18.4.1) the second purchase succeeds; on devices where it prompts for the account (email) + password every time (e.g., iOS 18.3.2, iPadAir2 15.6), the second purchase fails. The same Sandbox Apple Account behaves differently on different devices. An Ad Hoc (development-signed) build with the same account succeeds. Observation 2 — Product price sometimes returns USD instead of the storefront currency With the same Sandbox account (region: Japan), prices are shown in JPY on iOS 26.2 but in USD on iOS 18.3.2. The App Store app shows JPY, but SKProductsRequest / StoreKit 2 Product metadata returns USD. Question 1: Are these known Sandbox/TestFlight limitations? If so, what is the recommended way to reliably test repeat consumable purchases (and to get the correct storefront currency) in TestFlight across many devices and OS versions? Question 2: For TestFlight IAP testing, are there environmental differences between (A) using the device's real Apple ID (signed into Media & Purchases; automatic sandbox) and (B) signing out of Media & Purchases and using a Sandbox Apple Account — with respect to: reliability of repeat consumable purchases, authentication / session persistence (password-only vs account + password each purchase), storefront / currency resolution for product metadata, ability to clear purchase history? Which approach do you recommend for a consistent, reliable TestFlight IAP QA environment? Environment: TestFlight (App Store distribution), Sandbox tester region = Japan. (App-specific identifiers such as bundle ID are in our Feedback report FB24632077.) Repro: buy a consumable once (succeeds, finished) → buy the same product again → DuplicateTransaction on affected devices. Thanks!

Looking for iPhone beta testers: EachTime — Life Playbooks EachTime helps recurring situations get better. Prepare using what worked before, follow a simple Playbook, and save one useful lesson for next time. I’m looking for testers willing to try this short flow: Add a situation you want to handle better. Review the suggested Playbook and preparation steps. Correct the Playbook match if necessary. Finish the experience and save one lesson. No account is required. Calendar and Reminders access are optional—you can test everything using manual entry. I’d especially appreciate feedback about: Whether the app’s purpose is immediately clear Incorrect Playbook matches Confusing language or navigation Anything that feels unnecessary or difficult TestFlight link: https://testflight.apple.com/join/7fTHt1Te You can submit screenshots and comments directly through TestFlight. Thank you for helping improve EachTime.

When testing the iOS app on TestFlight, the subscription button always flashes briefly, or the subscription click doesn't respond. Could you please tell me what the reason is and how to solve it?

I cannot deliver my build to TestFlight. Every attempt fails with this error: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING Details: App Apple ID: 6805220594 Version / build: 1.0.2 (102) Platform: iOS What happens: I archive the app in Xcode and upload build 1.0.2 (102) to App Store Connect. The build finishes processing and shows up in App Store Connect. When I try to distribute it to TestFlight (enable it for testing / add it to a tester group), the request fails with ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING. Retrying gives the same result, so no build reaches TestFlight testers. The error suggests the beta (TestFlight) contract is missing or not active on the account, but I do not see any pending agreement I can accept myself in App Store Connect. I have also opened a support case for this (Case ID: 102951424291). I'm waiting for your help. Any pointers appreciated.

Hi everyone, I'm encountering an issue where the storefront country code returns "USA" unexpectedly in TestFlight builds, and I'd appreciate any insights from the community. Issue Description When executing SKPaymentQueue.default().storefront?.countryCode in our TestFlight builds, the property returns USA. However, we expect it to return JPN because both the Sandbox test user account and the Apple Account region configured on the device are set to Japan. Behavior Across Environments Xcode Debug & Ad Hoc Builds: Returns JPN as expected. TestFlight Builds: Returns USA unexpectedly. Related Threads I've noticed several threads reporting similar issues without a clear resolution: https://developer.apple.com/forums/thread/660817 https://developer.apple.com/forums/thread/794932 https://developer.apple.com/forums/thread/800078 https://developer.apple.com/forums/thread/814178 https://developer.apple.com/forums/thread/810860 Questions Is this USA value a known TestFlight/Sandbox-specific limitation or bug? Will production users in Japan correctly receive JPN (and see JPY prices) once the app is approved and published on the App Store? Is there any workaround or project configuration fix required on our side prior to App Store submission? Has anyone experienced this recently or confirmed the behavior in the production environment after release? Thanks!