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 channelyou can share your TestFlight Public Links with the developer communityto gather valuable feedback on crucial elementslike technical implementationuser experiencedesignand more. To maximize the benefits of posting TestFlight Public Links in the Developer Forumshere are some best practices to keep in mind: Provide details: Give comprehensive information about your applike new features and test casesand note specific areas where you seek feedback. The more detailed your post isthe 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.

Please help! Apple Support Support is MIA Every app that I have in TestFlight returns with this messageI 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”

Hi, I’m looking for clarification on TN3134: Network Extension provider deploymentspecifically 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 supervisionwhich suggests they are using a different deployment model. Thank you for any clarification or guidance!

We are having trouble analyzing our app's size. When we evaluate the app size locallyit might show a decreasebut after uploading it to TestFlightwe sometimes see the exact opposite result. Evaluating this is very complex. We suspect this discrepancy is due to server-side optimizations by Applebut 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 easexpo 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 Supportbut 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 entitlementbut it doesn’t use the Shared with You framework. Please remove the entitlement and upload a new build. I'm using SWHighlightSWHighlightCenterand SWAttributionView in several places throughout my app... I filed an issue in the Feedback Assistant but so farhave not received any response.

Hi, I’m running into a persistent issue in App Store Connect related to TestFlight and app reviewsand I’m hoping someone has seen this before. Around two weeks agoI 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 appearbut 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 pointI cannot update two existing appsand 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 appsnot just one Nothing changed on my side (no contract updatesno account changes) before this started happening. I’ve already reached out to Apple Developer Support multiple timesbut unfortunately haven’t received any response so farwhich 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 Howeverwhen attempting to install the app via TestFlightthe 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 waythis 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 whyhere'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 filebut 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 yearsoriginally distributed for iOS and iPadOS only. Recentlywe 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 macOSbut cannot be installed. TestFlight shows the message: “This app can only be tested on an iOS device.” This suggests the app itself is Mac-compatiblebut 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 macOSbut TestFlight applies additional or different eligibility checks. At the moment we think that TestFlight eligibility may depend on build metadatascheme/configuration flagsor 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_IPADTARGETED_DEVICE_FAMILYscheme/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 appreciatedespecially given that App Store distribution for macOS is already working. I hope we're missing something very basicand not that the app can't be tested as is for the macbecause 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. Anywayslet'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 thereyou can trade your occupied LIFE-CUBE with others usersgenerate unique digital cards + share them on social media straight from the appsee where in the world and by whom different wildlife was discoveredunlock a plethora of achievementsand 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 encounterperformance issuesand 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 interestand 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 certificatenot 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). Additionallymake sure the bundle you are uploading was built using a Release target in Xcodenot a Simulator target. If you are certain your code signing settings are correctchoose “Clean All” in Xcodedelete the “build” directory in the Finderand rebuild your release target. For more informationplease 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-sidebecause 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 processedassigned to an internal groupand the tester invitation is accepted. The build status shows Ready to Test / Testing in App Store Connect. Howeverinstallation 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.

I've read several topics on cancelling subscriptions in sandbox environmentbut it seems to me that it could not be applied to TestFlight. I can cancel sandbox subscriptions through Settings > App Store > Sandbox account But since TestFlight does not use sandbox account I cannot cancel a sub from there. AlsoTF purchase does not appear in the list of regular subscriptions (Settings > Profile > Media & Purchases). So my question is: is there any way to manually cancel auto-renewable subscription bought in TestFlight build of the app?

I have an iOS app build that is being tested. The user has provided feedback and screenshots that I can see in Connect. But I cannot download the zip file of the screenshot and feedback information. There are 3 screenshots. Each time I try it just times out. I have tried on a couple of different computers with the same result. Can you help please? Thanks

Hello, I'm getting a persistent error when submitting my TestFlight build: App: Mealog Build: 1.0 (4) Platform: iOS Steps: Go to App Store Connect → My Apps → TestFlight → Builds → select 1.0 (4) Click "Submit for Review" with plain-text test notes (no special chars/emojis) Error: "An error occurred processing your request. Please try again later." Troubleshooting done: Simplified test notes to plain text Tried incognito/private browser + cleared cache Disabled VPN/proxy Waited >1 hour and retried multiple times Confirmed build status is "Processed" Goal: Submit this build to TestFlight successfully.Attachment: Error screenshot uploaded.

Hello everyone, I’m reaching out to see if others are experiencing an extreme delay with the App Store review process. My app has been stuck in the "Waiting for Review" status since February 9th2026. What’s concerning is that this isn't just affecting the production build for the App Storebut also a separate TestFlight External Testing submission for another project. Both have seen zero movement for over 5 weeks. Details of the situation: Submission Date: February 92026. Status: Stuck at "Waiting for Review" (never transitioned to "In Review"). Communication: No messages in the Resolution Centerno metadata rejectionsand no requests for additional info. Attempted Fixes: I have contacted Developer Support via the "Contact Us" form twice. I received a generic "we are looking into it" response 10 days agobut no actual progress. Account Status: All agreements (Paid Applicationsetc.) are active and signed. I’ve noticed a few other threads mentioned this specific February 9th date. It feels like submissions from that window might have been "ghosted" in the queue. Questions for the community/Apple: Is there a known technical issue with the review queue from early February? For those who were stuckdid "bumping" the version number (e.g.1.0 to 1.1) actually clear the ghosted statusor did it just put you at the back of another long line? Are there any new 2026 compliance flags (like the new AI disclosure or Privacy Manifests) that could cause a "silent hang" instead of a rejection? Any advice from fellow developers or a nudge from an Apple representative would be greatly appreciated. App ID: 6759763683 (External Testing)6758399041 (Production Update) Case ID: 102844123144,

I want to provide free test accounts so that mobile games reviewers can play my iOS game for free. They should be able to make in-app purchases(consumables) without any charges. I don´t know how to create the free test accounts. Is it necessary that my iOS game is already published in the Apple App Store before I can provide test accounts for mobile games reviewers? Or is it necessary to let the reviewers play my game while it is still in TestFlight? If yesshould I ask them to give me there email address so that I can add it to my Sandbox accounts? My game was not yet released in the App Apple Store. It´s only available on TestFlight.

Hi everyone, I submitted my app for review on February 3and as of March 15 it’s still showing as “In Review.” This means it’s been stuck for over six weeks now. App Apple ID: 6757989460 I reached out to App Review Support via email two weeks ago but haven’t received any response yet. The app is a standard submission (not using TestFlightnot part of an expedited appeal)and I’ve verified that all compliance and payment information are complete. Has anyone else experienced such a long delay recently? Is there any additional way to get the team’s attention or escalate the case? Thanks in advance for any insights or advice.