Apple Developer Support case: 103009402078 (opened Oct 26, 2026, no resolution yet) Team ID: AC4JTSND8Z Every app record on my account fails in TestFlight, both for Internal Testing installs and for External Beta App Review submissions. A brand-new app record created after all agreements became active fails in exactly the same way, so this looks like an account-level backend problem. The App Store Connect API returns BETA_CONTRACT_MISSING for the account, which suggests the TestFlight beta contract was never provisioned on the backend. Apps AppApple IDBundle IDBuildVeyra6827206902com.bakiakyol.veyra1.0 (8)Veyra Beta Test (created after all agreements were active)—com.bakiakyol.veyratest1.0 (1)Account status (all active / published) Free Apps Agreement: Active (Oct 22, 2026 – Oct 22, 2027) Paid Apps Agreement: Active (Oct 27, 2026 – Oct 22, 2027) Tax (W-8BEN) and banking: Active Digital Services Act: Active App Privacy: Published Pricing and Availability: 175 countries or regions, free, none stuck in Processing Builds: Validated, symbols included, non-exempt encryption: No Problem 1: Internal Testing install fails In the TestFlight app, tapping Install for both apps fails within 1–2 seconds with: Could not install Veyra. The requested app is not available or doesn't exist. Device: iPhone 17 Pro Max, iOS 27.0.1 and 27.2 Other developers' TestFlight apps install normally on the same device and Apple ID. Already tried: reinstalling TestFlight, signing out and back in to the Apple ID, restarting the iPhone, and installing on another device. Same error every time. Problem 2: External Testing submission fails Adding any validated build to an external group and submitting it for Beta App Review shows: There was an error processing your request. Please try again later. POST https://appstoreconnect.apple.com/iris/v1/betaAppReviewSubmissions returns HTTP 422: { "errors": [{ "id": "ac442947-d2fb-4f3e-b060-36e63e62bfd8", "status": "422", "code": "ENTITY_UNPROCESSABLE", "title": "There was an error processing your request.", "detail": "Please try again later." }] }Request Could an Apple engineer please check the TestFlight beta setup for Team ID AC4JTSND8Z and re-provision it on the backend, or escalate case 103009402078 to App Store Connect / TestFlight Engineering? Thank you.

Hello Apple Developer Team, I am experiencing a serious TestFlight issue affecting multiple applications under my Apple Developer account. The issue started on October 9, 2026. 1. All existing TestFlight builds suddenly expired On October 9, all previously available TestFlight builds across multiple applications unexpectedly changed to "Expired" at the same time. These applications were previously available for testing. 2. Newly uploaded builds cannot be installed I uploaded new builds to replace the expired ones. The uploads completed successfully, and App Store Connect shows the new builds as "Ready for Internal Testing." For example: App: Mai Anh Kiếm Version: 1.0 Build: 135 TestFlight shows approximately 89 days remaining. However, when an internal tester taps Install or Update, TestFlight displays the following error: "Could not install Mai Anh Kiếm. The requested app is not available or doesn't exist." Therefore, even newly uploaded builds cannot be installed through internal testing. 3. External Beta App Review submission fails When I attempt to submit a new build for external TestFlight review, App Store Connect returns HTTP 422 with the following error: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING Error detail: "Beta Contract is missing." 4. Account information I am the Account Holder and Admin. My Free Apps Agreement and Paid Apps Agreement are both Active. New builds can be uploaded and processed successfully. The issue affects multiple applications, not just one app. 5. Apple Developer Support response I contacted Apple Developer Support. Support Case ID: 102990933108 Apple Support confirmed that build 1.0 (135) is ready for internal testing, but this does not resolve the actual problem: internal testers still cannot install the build. My questions: Why did all existing TestFlight builds suddenly expire at the same time? Why are newly uploaded builds unavailable for installation, even for internal testers? What causes BETA_CONTRACT_MISSING when all visible agreements are active? Could this indicate an account-level TestFlight distribution or Beta Contract issue that requires intervention from Apple? Could an Apple TestFlight engineer please investigate this issue or advise how to get it escalated? I can provide screenshots of the installation error and the API response. Thank you for your assistance.

Anyone is experiencing this issue? Today without any reason we can think of, all of our builds were expired on Testflight. Without knowing what happened, then we tried to add a new build, that it it seems to be in good shape on Testflight, even with the mark green meaning is ready to be tested. Even though, by trying to install the app on iOS using TF, we are getting a message saying "The requested app is not available"

my testflight builds got expired for all apps. New builds are not working on testflight either.

Hello, My first iOS app, Textout (version 1.0.0, build 46), has been in "Waiting for Review" since October 14, 2026, and has never moved to "In Review". There are no messages from Apple in App Store Connect, and no requests for additional information. Details App ID: 6793842235 Version / build: 1.0.0 (46) Submitted: Oct 14, 2026 at 2:37 AM (IST) Submission ID: 4b32b67c-ee72-4d8d-9351-3d09e284e9b1 Support case ID (App Review Status): 103005845026, opened Oct 23 What I've already done Requested expedited review twice Opened a support case with App Review, with no reply so far Not edited, withdrawn or resubmitted the build, so I don't lose my place in the queue I've seen other developers report long "Waiting for Review" times this month. Is anyone else still seeing this, and did your app move without any further action? Any guidance from App Review would be appreciated. Thank you.

Hey everybody, I enrolled in the Apple Developer Program and my membership is active. Xcode recognizes my team, code signing works, and I can archive my app successfully. The problem is that App Store Connect itself says: “Your Apple Account isn't enabled for App Store Connect.” Xcode gives the same kind of issue when I try to upload through Organizer. It says it can't authenticate with App Store Connect and that I don't have App Store Connect access for my team. What's weird is that everything else seems to work. My developer account is active, the team shows up correctly in Xcode, and the archive builds without any issues. I've tried signing out and back into Xcode, removing and re-adding my Apple ID, restarting everything, and waiting more than 24 hours since my membership became active. I already contacted Apple Support and they escalated the case to their senior support team, but I wanted to ask if anyone here has seen this before. Has anyone had App Store Connect take a while to become enabled after joining the Developer Program? Or is there something else I should be checking? Thanks.

Hello App team, Please respond and assist. i have paid for the Developer program but if my app doesn't go into production, it will be a useless app after November as it is a Christmas APP. Our app, XmasMaps, has been stuck in "Waiting for Review" since October 14, 2026 (Submission ID: 5f1bb173-1f5d-40b5-a67a-2078db01f541). Timeline of previous actions: Sept 29, 2026: Initial submission Oct 8 & Oct 11, 2026: Resubmitted fixes following rejections Oct 14, 2026: new build resubmitted, currently stuck in "Waiting for Review" Oct 16, 2026: Expedited review request submitted Oct 19, 2026: Support customer inquiry submitted Android is already live, and we are hoping to clear iOS review so users can access the platform ahead of the upcoming holiday season. Oct 24, 2026: Rejected again for something already built into my latest build. i resubmitted right away and now put back into "waiting for review" when I would expect that the engineer who rejected it would take it back and finalize my app. Submission ID: 5f1bb173-1f5d-40b5-a67a-2078db01f541 Support Case ID: 102982950152 Team ID: 34WAQXFJHP I ask, please assist and review my app. It is already live on Google and i really need it live on both platforms to promote it. Could you please let me know if any additional information is needed from my side? I have paid the Developer fee of $99 per year and putting my own money for this Christmas App. Please! I beg for assistance to finally approve my app. Thank you.

Hello App team, Please respond and assist. i have paid for the Developer program but if my app doesn't go into production, it will be a useless app after November as it is a Christmas APP. Our app, XmasMaps, has been stuck in "Waiting for Review" since October 14, 2026 (Submission ID: 5f1bb173-1f5d-40b5-a67a-2078db01f541). Timeline of previous actions: Sept 29, 2026: Initial submission Oct 8 & Oct 11, 2026: Resubmitted fixes following rejections Oct 14, 2026: new build resubmitted, currently stuck in "Waiting for Review" Oct 16, 2026: Expedited review request submitted Oct 19, 2026: Support customer inquiry submitted Android is already live, and we are hoping to clear iOS review so users can access the platform ahead of the upcoming holiday season. Submission ID: 5f1bb173-1f5d-40b5-a67a-2078db01f541 Support Case ID: 102982950152 Team ID: 34WAQXFJHP I ask, please assist and review my app. It is already live on Google and i really need it live on both platforms to promote it. Could you please let me know if any additional information is needed from my side? Thank you.

Hello, New individual developer account (enrolled October 2026). My first iOS app cannot be tested via TestFlight. 1) Internal testing: builds 1.1.2 (16), (17), (18) and (19) all show "Testing" in my internal group. Two different internal testers (Account Holder and a Marketing-role user) on two different iPhones (iOS 26) get: "Could not install. The requested app is not available or doesn't exist." App Store Connect shows 2 invites but 0 installs for every build. 2) External testing: when I add build 19 to an external group and press "Submit for Review", App Store Connect says: "There was an error processing your request. Please try again later." Already checked: membership active, Free Apps Agreement active, export compliance answered, build metadata "Validated" (SDK 23F81a, min iOS 15.0), pricing Free and available in Türkiye, testers accepted the invitations, TestFlight reinstalled, devices restarted. Developer Support case: 102998773608 (opened October 16, no reply yet) Feedback: FB25298826 Screenshots attached: (1) the install error on iPhone (Turkish UI: "Could not install ASG – Afyon Scooter Derneği. The requested app is not available or doesn't exist."), (2) the App Store Connect error when submitting build 19 to the external group. I don't have a Mac, so I can't attach Xcode device logs; builds are made with Codemagic. Could someone from Apple please check whether a TestFlight/beta setting is missing on my account? Thank you.

Hello, I sent this in as a feedback several weeks ago about watchOS 26.2 beta 2 but since the issue is still active now that watchOS 26.2 is in production I'm reposting here for the community. I would also like to submit a DTS about this issue but honestly don't know the best way to go about it and would appreciate advice about that. There seems to be an issue with VPP distribution for our app on watchOS 26.2. When our watchOS companion app is launched after being installed through VPP to a supervised iPhone, it encounters a dyld error before main() or any application code is even called. The same app launches correctly in every other circumstance we could imagine and test: – Installed through VPP on supervised devices running watchOS 26.1. – Installed from the app store (using an apple id) on a supervised iPhone and paired watch running iOS 26.2 / watchOS 26.2. – Installed through Testflight on a supervised iPhone and paired watch running iOS 26.2 / watchOS 26.2. – Installed through the app store on unsupervised devices running watchOS 26.1 and 26.2. This strongly appears to be a VPP signing issue because we even did the following experiment: Install iPhone and Watch apps through the App Store on a supervised device pair running public iOS 26.2 beta 2 / watchOS 26.2 beta 2. Verify that both apps launch successfully. Use an MDM command to install from VPP over the existing installations Verify that the watch app fails to launch (the iOS app is unaffected) My feedback included some crash logs which I won't be reposting publicly here. Any feedback or ideas appreciated.

Since 19 Oct 2026, TestFlight is blocked for my whole team, not for a single app. Account Team ID: 95MF867832 (individual account, I am the Account Holder) Apps: 6819072253 and 6748716751 What happened On 19 Oct 2026 at 06:13 PDT every TestFlight build on the team expired at the same second, including builds that still had weeks left. A new build uploaded on 20 Oct is VALID (expires Jan 2027), but submitting it to Beta App Review fails: App Store Connect web: "There was an error processing your request. Please try again later." API POST /v1/betaAppReviewSubmissions: 422 ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING ("Beta contract is missing for the app"). Internal testers cannot install either: "The requested app is not available or doesn't exist". Retried hourly through 23 Oct: still 422. Already checked All agreements are Active, nothing pending. The Paid Apps Agreement was activated on 13 Oct 2026. A fresh build did not help. App Store review submission itself works (an App Store version was submitted on 23 Oct); only TestFlight is affected. Reported Feedback Assistant: FB25290077 Developer Support case: 103005423668 Other developers report the same error in thread 813703, which suggests a backend issue with the TestFlight beta contract after an agreement change. Could someone from Apple please route this to the TestFlight team to re-attach the beta contract? Thank you.

WHY IS TESTFLIGHT REVEIW NOT INSTANT THIS IS COMPLETE BS SHIP MY APP NOW I AM LOSING TIME WAIT FOR THIS BS WALLED GARDEN TO MOVE

Why is TestFlight review taking so long!!! This shoulld be instantly approved what kinda BS is this...

Hi everyone, I'm an independent developer and designer, and I've just opened my first public TestFlight beta for an app called Paddock. It's an iOS 26 app to keep track of your cars: maintenance, fuel costs, wheel sets and history, with the data stored on the device. I'm still learning how to run a beta well, so I'd really value advice from people who've been through this: Testers. What worked best for you to find real testers (public link, groups, communities)? How did you keep them engaged after the first install? Feedback. How do you collect it so it's useful? Do you rely on TestFlight feedback, a form, email? Is there something you wish you had asked from the start? What to Test and onboarding. What do you put in the beta description and the test notes so testers know what to try without feeling like it's homework? Builds. Any tips for pacing builds and keeping the 90-day expiry from catching you off guard? Beta App Review. Anything that tends to trip up first-time submissions? If you'd like to try it and tell me what feels off, the beta is here: https://testflight.apple.com/join/qup6rF31 It needs iOS 26. Honest criticism is the most useful thing you can give me. Thanks for reading, and for any advice. Arturo

I submitted my app for TestFlight review about 3 weeks ago and it is still "waiting for review". How can it be? I think something wrong is going on. Please advise.

Hello App Review team, Our app, XmasMaps, has been stuck in "Waiting for Review" since October 14, 2026 (Submission ID: 5f1bb173-1f5d-40b5-a67a-2078db01f541). Timeline of previous actions: Sept 29, 2026: Initial submission Oct 8 & Oct 11, 2026: Resubmitted fixes following rejections Oct 14, 2026: new build resubmitted, currently stuck in "Waiting for Review" Oct 16, 2026: Expedited review request submitted Oct 19, 2026: Support customer inquiry submitted Android is already live, and we are hoping to clear iOS review so users can access the platform ahead of the upcoming holiday season. Submission ID: 5f1bb173-1f5d-40b5-a67a-2078db01f541 Support Case ID: 102982950152 Team ID: 34WAQXFJHP Could you please confirm if this submission is correctly queued or if any additional information is needed from our side? Thank you.

Hello, We would appreciate some guidance regarding an unexpected StoreKit currency result in a TestFlight build. Our iPhone language and region are both set to France. The Sandbox tester is also configured for France, and our subscription products have French availability and pricing configured in App Store Connect. In the TestFlight build we diagnosed, StoreKit reports the current storefront as France with EUR: storefront=FRA/143442/EUR However, all 10 subscription products are returned with USD product metadata: products=10/10 formatCurrencies=USD localeCurrencies=USD error=NONE Example: formatCurrency=USD locale=fr_US_currency_USD localeCurrency=USD display=1,99 $US price=1.99 We first observed this through Flutter's in_app_purchase integration. To determine whether the Flutter plugin was involved, we added a native StoreKit 2 diagnostic to the same TestFlight build. The native result was identical: receipt=sandboxReceipt storefront before=FRA/143442/EUR storefront after=FRA/143442/EUR products=10/10 formatCurrencies=USD localeCurrencies=USD error=NONE The issue appears specific to the TestFlight distribution. When the application is installed directly from the development computer, prices are returned in euros on the same device. We also tested with the regular Media & Purchases account signed out and a French Sandbox tester connected. Once the products loaded successfully, StoreKit still returned USD metadata. In another configuration, the application displayed the USD price while Apple's purchase sheet displayed the price in euros. We are using the price and formatting information returned directly by StoreKit. We do not want to infer the currency from the device region or perform a client-side currency conversion, because StoreKit should remain the authoritative source. Could you please help us understand: Is it expected for Storefront.current to report FRA/EUR while Product.priceFormatStyle.currencyCode, its locale currency, and Product.displayPrice use USD? Could a TestFlight or App Store Connect configuration cause product metadata to use a different currency from the current storefront? Is there another account, availability, pricing or distribution setting that we should verify? Is there a recommended way to refresh or invalidate the product metadata used by a TestFlight installation? We have already filed Feedback Assistant report FB24723329, which is currently under investigation. Thank you very much for any clarification or additional diagnostic steps you can suggest.

Hello, Our team is completely blocked from distributing builds via TestFlight due to the following backend API error: { "errors" : [ { "status" : "422", "code" : "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title" : "Beta contract is missing for the app.", "detail" : "Beta Contract is missing." } ] } Account & App Details: • App ID: 6817838147 • Existing Case IDs: 102986964055, 102986683221 • Agreements, Tax, and Banking: All Active and signed This appears to be a known backend desync where the TestFlight Beta contract is detached from our account/app. Could an Apple engineer or moderator please help escalate this to internal App Store Connect engineering to re-provision/re-attach our TestFlight beta contract? Thank you.

I cant install app from testflight, i get the error Could not install APP. The requested app is not available or doesnt exist. and also i cant add external testers, i get the error "errors" : [ { "id" : "512439fe-9892-4dc1-a260-22ff0908e15d", "status" : "422", "code" : "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title" : "Beta contract is missing for the app.", "detail" : "Beta Contract is missing." } ] } Sample app with apple ID 6821153194

I purged my DerivedData folder then did a clean build of my app using Xcode 27.2 RC. I then submitted my build through the Organizer window. I then logged into App Store Connect. When I try to submit the build for external testing, App Store Connect is giving me an error that beta tools can't be used. I'm not using beta tools. I'm using release candidate tools. Less important but I thought beta tools could be used for testing. Anyway, is this an AppStore Connect issue or am I doing something wrong?