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, I’m experiencing two issues which I believe may be related to a single root cause: TestFlight Installation Error When I try to install my app via TestFlight for testing purposes, I receive the following error message: “Could not install app. The requested app is not available or doesn’t exist.” Unable to Add Build to External Testers When I attempt to add a build to an external testers group, I see the following error in the network tab after submission: { "errors" : [ { "id" : "95d240bd-94bd-4653-8d60-8dc691d6e3dc", "status" : "422", "code" : "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title" : "Beta contract is missing for the app.", "detail" : "Beta Contract is missing." } ] } I have reviewed and completed all required forms under Business → Agreements, and there are currently no pending alerts or agreements requiring action. At this point, I’m unable to proceed with testing my application and would greatly appreciate any guidance or suggestions. Additionally, I have an open support case that has not yet received a response: Case ID: 102855791526 Area: Distribution / TestFlight Thank you in advance for your help.

I'm unable to submit builds to TestFlight or install them on my device for my app "TalkBee" (Bundle ID: com.talkbee.app). Error when submitting for beta review: { "status": "422", "code": "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title": "Beta contract is missing for the app." } When trying to install via TestFlight app on iPhone, I get: "The requested app is not available or doesn't exist." What I have verified: All agreements (Free Apps + Paid Apps) are Active Bank account is Active (SAR) Tax forms (W-8BEN) are Active Build uploads successfully via Transporter Individual developer account, I am the Account Holder Existing Apple Support Case: 102857454011 (no resolution yet) This is blocking my app release. Any help would be appreciated.

Same scenario described here: https://forums.developer.apple.com/forums/thread/738942 User clicked accept for an internal tester invitation sent to their work apple id on their personal device which was signed in with their personal apple id. This seems to have redeemed the code to the users personal account. However, the user has removed themselves from testing the app and we're trying to get their work apple id registered but the invite code that keeps being sent is coming back saying invalid. Things we've tried: We located the last build the user installed on their device and expired the builds deleted / readded the work apple id to internal testing group It's still sending the same invitation code from TestFlight and saying that the code cannot be redeemed.

My app targets iOS 12.0 and crashes immediately on launch when installed via TestFlight on an iPad running iOS 12.x. The same archive works perfectly when installed via Ad Hoc distribution or directly from Xcode. This is a regression — the exact same source code, compiled with the same Xcode version, was successfully distributed via TestFlight and the App Store last month (March 2026) without issues. No changes were made to the code, Xcode version, or signing configuration. Steps to reproduce: Archive an app with IPHONEOS_DEPLOYMENT_TARGET = 12.0 using Xcode 16.4 Upload to App Store Connect Install via TestFlight on an iPad running iOS 12.x App crashes immediately on launch (pre-main, no crash log generated) Expected: App launches normally (as it did last month) Actual: App is killed immediately, process exits with reason: (none) Console.app shows the process never transitions from xpcproxy to the actual binary — it dies within ~260ms of bootstrap, indicating a dyld or app thinning issue. Environment: Xcode: 16.4 Deployment target: iOS 12.0 ENABLE_BITCODE: NO Device: iOS 12.x Ad Hoc install: WORKS Xcode direct install: WORKS TestFlight install: CRASHES App Store install: CRASHES Anyone else seeing this?

Hi, I’m new here and trying to upload my first two apps to the App Store, but I’m getting stuck in TestFlight. I’ve tried several different ways to export my apps, both with Expo and Xcode, but it makes no difference. My apps get stuck in Ready to Submit. When I add Internal Testing (my self) I receive an email saying I can start testing the app, and I can see it in TestFlight, but when I tap on it I get the following error: Unable to install AppName. The requested app is not available or does not exist. I contacted Apple Support over a week ago, but I haven’t received any response. Any suggenstions? Thanks, Jonas

Hi, I’m looking for clarification on TN3134: Network Extension provider deployment, specifically iOS deployment requirements for: packet tunnel provider DNS proxy provider From the documentation: Packet Tunnel Provider App extension (min iOS 9.0): per-app mode requires a managed device DNS Proxy Provider App extension (min iOS 11.0): supervised devices only App extension (min iOS 11.0): per-app mode requires managed devices Issue I implemented a DNS proxy using NEDNSProxyManager. Works as expected in debug builds on a local device Fails to configure when distributed via TestFlight Console Output (TestFlight build) error 10:05:39.872258-0500 nehelper The production version of *** is not allowed to create DNS proxy configurations. Use MDM to create DNS Proxy configurations for the production version of ***. Question Is it possible to distribute a DNS proxy provider for use on non-MDM / non-supervised devices? If not: Is the limitation strictly enforced at distribution/runtime? Is a packet tunnel provider the only viable alternative for App Store distribution? There is a lot of different VPN apps on the App Store that appear to work out of the box without MDM or supervision, which suggests they are using a different deployment model. Thank you for any clarification or guidance!

We submitted our test flight build Thursday night, it's been over 60 hours. Does anyone have any suggestions on how to expedite this? I contacted support by going through Distribution -> TestFlight although it might be seen as a generic testflight question. The expedited app review route seems like it's only for AppStore.

Please help! Apple Support Support is MIA Every app that I have in TestFlight returns with this message, I have attempted to contact developer account support that they have not returned any messages. It’s been over a week. “The requested app is not available or doesn't exist”

We are having trouble analyzing our app's size. When we evaluate the app size locally, it might show a decrease, but after uploading it to TestFlight, we sometimes see the exact opposite result. Evaluating this is very complex. We suspect this discrepancy is due to server-side optimizations by Apple, but there is a lack of clear documentation and articles explaining the process. Can anyone help clarify why this happens and how to measure it accurately?

Hi everyone I recently build an app and deployed it through app store connect and testet it on TestFlight. Everything worked fine up until build 1.0.3. Since then I have not been able to install the app on my phone through TestFlight - even though build and submission runs through successfully on eas, expo and app store. I have tried deleting and reinstalling the TestFlight from my phone. removing and adding back myself as tester. checking logs and commits from the shift from build 1.0.3 to build 1.0.4. I can see I changed "name" and "slug", so I tried removing the app from app store connect and added a new one with new build and submission. Ran through successfully but still could not install the app through TestFlight on my iPhone. I have also tried reaching out to Apple Developer Support, but I have not heard from them. Has anyone tried something similar?

I have an existing app in App Store Connect. I added the SharedWithYou functionality to the app code and tested it on several devices. Everything is working as expected. One of the first steps was to add the com.apple.developer.shared-with-you entitlement to the Entitlements.plist file. This required a round of updates for app identifiers and provisioning profiles. When I upload the production build for testing in TestFlight I receive the following error: 90919: Invalid entitlement. The “” bundle has the com.apple.developer.shared-with-you entitlement, but it doesn’t use the Shared with You framework. Please remove the entitlement and upload a new build. I'm using SWHighlight, SWHighlightCenter, and SWAttributionView in several places throughout my app... I filed an issue in the Feedback Assistant but so far, have not received any response.

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!

When I submit the app to TestFlight beta review I get the error show on UI. (I filled all filed info in Beta Infomation) There was an error processing your request. Please try again later I was inspected Safari to see the detailed error and I got the below error. Failed to load resource: the server responded with a status of 422 () and the detailed javascript error componentStack: undefined errorCode: undefined message: "API Response Error: TF_BETA_APP_REVIEW_RESPONSE" stackTrace: "status code: 422 --- api correlation key: NZEKCTWMNANXDZVTRD3V4GNE3U" Anyone can tell me the problem and how to fix it. Many Thanks.

Hello, I am experiencing a persistent TestFlight installation issue affecting multiple unrelated apps under the same Apple Developer account. For all affected apps: Builds upload successfully to App Store Connect Processing completes normally Builds appear in TestFlight Internal and external testing can be enabled Public links generate correctly However, when attempting to install the app via TestFlight, the installation fails with the error: “The requested app is not available or doesn’t exist.” This occurs: For internal testers For external testers Across different Apple IDs Across different devices With newly created apps After incrementing build numbers After re-uploading builds After signing out/in of TestFlight After regenerating provisioning profiles After creating entirely new app entries The issue currently affects: • TubeChat AI – Apple ID 6752591427 • Vibex – Apple ID 6756860663 • vigilAI – Apple ID 6757738356 Since multiple unrelated apps are impacted in the same way, this appears to be an account-level or App Store Connect backend issue rather than a code signing or project configuration problem. Has anyone encountered a similar situation where TestFlight distribution fails across all apps within a developer account? Any guidance would be greatly appreciated.

Hi everyone, My TestFlight build has been stuck in 'Waiting for Review' for over 32 hours and I'm hoping someone can help or share their experience. The situation: I have an External Testing group with a Public Link set up. The build was submitted for Beta App Review on March 19th but it's been over 32 hours with no update. I have 25+ testers waiting to install the app. What I've tried: Waited patiently Checked App Store Connect multiple times No rejection emails received No issues flagged by Apple Questions: Is anyone else experiencing unusually long review times for TestFlight external builds right now? Is there anything I can do to speed up the process or check if something is wrong? Has anyone successfully resolved this by contacting Apple Developer Support directly? Any advice would be greatly appreciated. Thank you! Apple Support Case ID: 102846633409

Hi, Some crashes downloaded from TestFlight aren't symbolicated by Xcode and I don't know why, here's an example: Although all uploaded builds contain debug symbols (Symbols directory with .symbols files) and other crashlogs in the same version are symbolicated just fine (also visible on the above SS). I have access only to the .symbols files but not to the original dSYMs and I wonder how to perform symbolication manually. I tried pointing atos and symbolicatecrash utilities to respective .symbols file, but they are unable to work with it. I'm sure it's possible as TestFlight symbolicates crashlogs using only .symbols files somehow. Could you give a hint?

Hello everyone. We have an app that has been on the App Store for several years, originally distributed for iOS and iPadOS only. Recently, we enabled Mac (Designed for iPad) and started distributing macOS-compatible builds. Current situation: The app is available and downloadable from the macOS App Store and runs correctly on Apple Silicon Macs. The same app/build appears in TestFlight on macOS, but cannot be installed. TestFlight shows the message: “This app can only be tested on an iOS device.” This suggests the app itself is Mac-compatible, but TestFlight is treating the build as iOS-only. Environment and checks performed: Mac is Apple Silicon. App Store Connect app-level availability for Mac (Designed for iPad) is enabled. The app is not Mac Catalyst; it is a UIKit iOS/iPadOS app. Distribution is done via GitLab CI. CI uploads use an App Store provisioning profile (Apple Distribution), not development or ad-hoc. iPhone and iPad TestFlight installs work as expected. Info.plist verification: UIRequiredDeviceCapabilities was originally present (armv7) and has since been: removed entirely, build number incremented, new builds uploaded to TestFlight. No other hardware capability requirements are declared. LSRequiresIPhoneOS = true remains unchanged. No other plist keys that should exclude macOS are present. CI / build considerations: The same uploaded build is accepted by App Store Connect and distributed successfully on the macOS App Store. This tells us the binary itself is valid for macOS, but TestFlight applies additional or different eligibility checks. At the moment we think that TestFlight eligibility may depend on build metadata, scheme/configuration flags, or internal App Store Connect state that differs from App Store distribution. Questions: Are there known cases where a build is valid for macOS App Store distribution but not eligible for macOS TestFlight installation? Does anyone know if TestFlight applies stricter or different platform gating than the App Store for “Mac (Designed for iPad)” apps? Are there specific build settings (e.g. SUPPORTS_MAC_DESIGNED_FOR_IPAD, TARGETED_DEVICE_FAMILY, scheme/config mismatches) that can affect TestFlight macOS eligibility independently of App Store eligibility? Is there an authoritative way in App Store Connect to inspect why a specific TestFlight build is marked as “iOS-only” for macOS? Any insight into TestFlight-specific eligibility rules for “Mac (Designed for iPad)” would be appreciated, especially given that App Store distribution for macOS is already working. I hope we're missing something very basic, and not that the app can't be tested as is for the mac, because it's useful to have our QA team test it on the mac.

Hi there everyone! ELB owner of VIBERELIC here. NOTE: I tried posting this a couple times now but it keeps getting taken down - I am not too sure why. I haven't received any explanation and I am pretty certain that I am posting in the correct place for TestFlight Apps. Anyways, let's try this again! ✦ I am really excited and proud to finally share with you all what I have been working on for the past month! My flagship app "WilderDEX!" is finally at the point where it can be tested by the public. I hope you guys have pets because this is the perfect app to document their personalities! It's basically a real-life Pokemon PokeDEX! With WilderDEX!, you have the ability to collect animals using unoccupied "LIFE-CUBES". You get 1 LIFE-CUBE each day that you successfully collect an animal. From there, you can trade your occupied LIFE-CUBE with others users, generate unique digital cards + share them on social media straight from the app, see where in the world and by whom different wildlife was discovered, unlock a plethora of achievements, and participate in the leaderboard ranking system! Please help test the app and provide any feedback you possibly can. It is incredibly valuable for the improvement of the app before it's official launch. Report any glitches you encounter, performance issues, and ideas you may have that could improve the app from it's current state! I have a lot more ideas that I am planning on implementing once everything is certified working and stable. Please let me know if you have any questions! Thank you for your interest, and HAPPY COLLECTING! Test here : https://testflight.apple.com/join/8vmVfRrb all rights reserved © 2026 viberelic ✦ ventures ✦ Above : A Uniquely Generated WIlderDEX! Digital Kitty Card

There seems to be a problem to a specific Apple Developer Account regarding Xcode Cloud Distribution (Signing). The Xcode Cloud Error Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “XcodeCloudTest.app/XcodeCloudTest” is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose “Clean All” in Xcode, delete the “build” directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/support/code-signing. Investigation Apple Developer Forums This issue seems to be known: https://developer.apple.com/forums/thread/746210 Debugging by ourselves We setup an example Xcode project from a default iOS Xcode app template to rule out any project issues. This example project failed with the same error as stated above. In the next step we tried the same example project with a different Apple Developer Account and it successfully distributed the example App through Xcode Cloud. Conclusion It seems like there is no setup issue on developer-side, because our example project works out-of-the-box on a different Apple Developer Account. Our only hope is that Apple will have a look on our Developer Account. Maybe there is some internal setting.

Hello, I have an internal TestFlight build for my app PewPewApp (Apple ID 6760741808). The build is processed, assigned to an internal group, and the tester invitation is accepted. The build status shows Ready to Test / Testing in App Store Connect. However, installation from TestFlight fails with: “The requested app is not available or doesn’t exist.” Could you please check whether there is an account-level or backend TestFlight distribution issue affecting this app/build? Thank you.