TestFlight Public Links are a great way to share beta versions of your apps with other members of the Apple Developer Program. With this new channel, you can share your TestFlight Public Links with the developer community, to gather valuable feedback on crucial elements, like technical implementation, user experience, design, and more. To maximize the benefits of posting TestFlight Public Links in the Developer Forums, here are some best practices to keep in mind: Provide details: Give comprehensive information about your app, like new features and test cases, and note specific areas where you seek feedback. The more detailed your post is, the better equipped the community will be to provide insight. Select platforms: Select the platforms that your beta app supports. Enter categories: Enter the App category you’ve selected or plan to select for your app on the App Store. Categories are critical to ensuring your post can be easily found by interested users. Stay connected with notifications: Enable web and push notifications so you’ll know when you receive feedback on your post. Note: The TestFlight app is still the most comprehensive way to gather feedback. This space is meant as a helpful secondary channel.

Hello everyone, We submitted a major update for our social networking app, Yuppi, on October 23, 2026. Both our TestFlight and App Store submissions are still in "Waiting for Review" status. Following a previous consultation with Apple's App Review team, we carefully addressed their feedback, completely redesigned our app, and introduced several new features. We fully understand and respect Apple's review procedures and standard timelines. However, our main priority at this stage is TestFlight. We would love to give our existing users the opportunity to experience and test our new design and features before the official App Store release. We completely understand that the App Store review may take additional time, and we have no concerns about following the standard process. We would sincerely appreciate any guidance from the Apple App Review team regarding whether our TestFlight submission could be reviewed first. We would also love to hear from other developers who have experienced similar TestFlight review delays. How long did your review take, and was there anything that helped move the process forward? Thank you all for your time and support.

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

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, We cannot distribute any build via TestFlight. Both internal and external testing fail. This appears to be a server-side beta contract issue on the account. SYMPTOMS Builds upload and process successfully. All 8 builds show status "Testing" in App Store Connect with 84-90 days remaining. In the TestFlight app on device, the build appears with an Install button. Tapping Install fails immediately with: "Could not install [App]. The requested app is not available or doesn't exist." This happens for INTERNAL testing as well, which does not require Beta App Review — indicating the problem is not in the review pipeline. In App Store Connect, the "What to Test" step fails with: "There was an error processing your request. Please try again later." BROWSER CONSOLE EVIDENCE Repeated failures on the beta review submission endpoint: Failed to load resource: the server responded with a status of 422 https://appstoreconnect.apple.com/iris/v1/betaAppReviewSubmissions Also observed: 404 NOT_FOUND — /iris/v1/appTaxCategories/[app id] "There is no resource of type 'appTaxCategories' with id '...'" ACCOUNT STATUS — all verified Active Free Apps Agreement: Active (Oct 19, 2026) Paid Apps Agreement: Active (Oct 21, 2026) Bank account: Active Tax forms (Certificate of Foreign Status, W-8BEN): Active (Oct 21, 2026) Digital Services Act: Active (Oct 22, 2026) Apple Developer Program membership: current Account Holder accepted the Oct 13, 2026 Developer Program License Agreement This is a newly enrolled account; all agreements became Active Oct 19-22, 2026. BUILD CONFIGURATION Version: 1.0.0, builds 6 through 15, uploaded Oct 22 and Oct 28, 2026 — all AFTER the agreements became Active Processing status: Complete / Ready to Submit App Availability: configured, no territories stuck in "Processing" Encryption: ITSAppUsesNonExemptEncryption set in Info.plist History: First release cycle; app has never been removed from sale ALREADY TRIED Multiple new builds, removing and re-adding testers, new testing groups, reinstalling TestFlight, verifying Apple IDs match invitations, multiple devices and multiple Apple IDs. No change. QUESTION Could the beta contract for this account be re-provisioned on the App Store Connect backend? Per previous threads this appears to require internal action. Apple Support Case ID: 103005208314 Bundle ID: com.tirtik.tirtik This is a server-side issue, not device-side. A sysdiagnose can be provided on request. Thank you.

New organization account. Since accepting the Free Apps Agreement on Oct 27, 2026, TestFlight stopped working for all our apps: All builds are marked Expired within days of upload, without anyone expiring them. Internal testers get "The requested app is not available or doesn't exist" when installing. External submission returns HTTP 422 ENTITY_UNPROCESSABLE (no sub-code) from /iris/v1/betaAppReviewSubmissions. TestFlight worked on Oct 21–22 (builds installed by testers). Membership and agreements are active; app metadata, privacy and export compliance are complete. App Apple ID: 6825263720 Developer Support case: 103012517274 Feedback: FB25359930 Could someone from Apple check whether our team's TestFlight beta contract needs to be re-linked? Thank you.

Does Xcode 27 or TestFlight support installing a watch-only beta on an Apple Watch For Your Kids device? I want to test my watch only standalone app on my kids apple watch as that is the only device I have. Is it possible to use that watch for testing standalone apple watch application. The watch is setup as kids watch on my iphone.

To Apple Engineers, I don't seem to get any updates or responses so I will keep trying to reach out here. Please work with me on what is needed to get my app approved. it is truly important to get it deployed as soon as we can so I can begin to launch and promote the app in App Store. It has already been live on the Google Play Store for a couple weeks. My app: XmasMaps has been going from "Waiting for Review" to "Rejected". I would fix the mistakes right away which would put XmasMaps back into "Waiting for Review". This App would be a useless App after November. Our app, XmasMaps, has been stuck in "Waiting for Review" since September 29th, 2026 (Submission ID: 1ced2377-575b-4bdd-812f-2852a23c2ffc). 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. Oct 28, 2026: As of today, I opened multiple app requests for an update and update the forum multiple times until I can try to get a response. Submission ID: 1ced2377-575b-4bdd-812f-2852a23c2ffc Support Case ID: 102982950152 / 103008467960 Team ID: 34WAQXFJHP I ask, please assist and review my app. I really need it live on both platforms to promote it. Please let me know if any additional information is needed from my side. Thank you.

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...