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.

Dear TestFlight Team! I am observing an increasing misuse of TestFlight public and private invites to distribute scamspamand potentially malicious builds: I had reported this already in December last year via Feedback assistantbut since the malicious behavior has not stoppedI hope that you can forward my bug reports to the right team: FB21379977FB21845307 In multiple casesthese builds impersonate well-known apps (e.g. ChatGPTOpenAIMeta) by changing the app name and icon after an initial TestFlight approvalmisleading users into installing software from unrelated developer accounts. I believe this represents a systemic weakness in the TestFlight review and update flowenabling targeted phishing or malware distribution outside the App Store review process. My bug reports have attached: TestFlight invitation emails (.eml) Screenshots from TestFlight documenting impersonation behavior ⸻ Steps to reproduce Create a new Apple Developer account. Upload an initialbenign app (e.g. a calculator) as version 1.0.0 and obtain TestFlight approval. Upload a second build: without changing the version number increase build number Change the app name to a well-known product (e.g. “ChatGPT”) Change the app icon to match the impersonated product Invite targeted email addresses to the TestFlight group. Recipients receive an official TestFlight invite and are prompted to install the impersonating app. ⸻ Expected results TestFlight builds that significantly change app identity (nameiconbranding) should: Require additional reviewor Be blocked from distribution without re-approval. Developer accounts should not be able to impersonate well-known companies (e.g. “OpenAI Platforms LLC”) without verification. Users should be protected from installing TestFlight builds that materially differ from what was originally reviewed. ⸻ Actual results App name and icon can be changed between TestFlight builds without triggering additional review. TestFlight invites can convincingly impersonate trusted brands. Targeted users may reasonably believe they are installing a legitimate beta. This creates a credible vector for: Phishing (credentialspayment details) Data exfiltration Social engineering attacks I did not install the builds to avoid personal riskbut the attached artifacts should allow Apple’s internal teams to reproduce and analyze the behavior safely. Some more examples:

Hi everyone, I’m currently facing an issue in App Store Connect when submitting a build to TestFlight. When I try to complete the “What to Test” section and submitI get the following error: “There was an error processing your request. Please try again later.” Case details: Case ID: 102871190604 Submitted: April 172026 (GMT+7) Status: No response after 3–4 days This issue is blocking me from submitting the build. What I’ve tried: Retried multiple times Switched browsers (ChromeSafari) Used Incognito mode Logged out and back in Simplified the “What to Test” text Checked build is processed and not expired I have already contacted Apple Developer Support but haven’t received any response yet. Questions: Is this a known App Store Connect issue? Should I wait for supportor upload a new build? If any Apple staff could help check this caseI would really appreciate it. Thank you.

Hi everyone, I’m getting this error in App Store Connect when submitting a build in TestFlight: “There was an error processing your request. Please try again later.” Case information: Case ID: 102871415765 Contacted Apple Developer Support: April 172026 (GMT+7) It has been 3–4 days with no response so far Where it happens: App Store Connect During the “What to Test” step The build is already processed and available What I tried: Retried several times Switched browsers Used Incognito mode Logged out and back in Simplified the “What to Test” text Checked that the build is not expired This issue has been blocking submission for several days now. Has anyone experienced this recently? Is there any workaroundor should I upload a new build? Thank you.

I'm experiencing a persistent issue where my app uploads successfully to TestFlight and appears in App Store Connectbut internal testers (including myself) receive the following error when attempting to install: "Could not install xxxxxxxxx. The requested app is not available or doesn't exist." What works: The build archives and exports successfully via Xcode (local buildRelease configuration) The IPA uploads to App Store Connect without errors via eas submit The build appears in TestFlight and passes processing I can add the build to my Internal Testing group Testers receive the TestFlight notification and can see the app What fails: When any tester taps "Install" or "Update," the download begins brieflythen fails with the "not available or doesn't exist" error This affects all internal testers on the accountnot just one device Troubleshooting already completed: Verified code signing is correct: Release configuration uses CODE_SIGN_STYLE = ManualCODE_SIGN_IDENTITY = "iPhone Distribution"with a valid App Store distribution provisioning profile (UUID: 39bc4c63-bc64-403a-a2a6-6737b3d33115) 2. Distribution certificate is valid: Serial 4838CD7571DE5361B98A5FB2F769F74Dnot expired (expires 2027-04-16) 3. Regenerated provisioning profile via EAS credentialsremoved stale profilesand rebuilt — same result 4. Incremented build numbers correctly across multiple submissions (3004 → 3005 → 3006) 5. Previously resolved a signing misconfiguration (build 3005 was incorrectly signed with "Apple Development" instead of "iPhone Distribution" due to expo prebuild reverting settings) — this was corrected for build 3006but the install error persists 6. Confirmed the build is not stuck in processing — it shows as ready for testing in App Store Connect 7. Tested on multiple devices running current iOS versions 8. Cleared TestFlight app cache and reinstalled TestFlight on test devices Why I believe this is a server-side issue: Multiple developers in the Apple Developer Forums have reported the identical symptom — valid builds that upload and process correctly but fail to install with this exact error message. In those casesApple Support resolved the issue on their end within 48 hours with no action required from the developer. The signingprovisioningand build configuration were not the cause. This one is very specific to what I am dealing with https://developer.apple.com/forums/thread/778597 One developer stated you fixed it on your sidewithout any real reasoning which also leads me to believe this is not something I can fix on my end https://developer.apple.com/forums/thread/778597?answerId=884241022#884241022 I've exhausted all client-side troubleshooting and believe this may require intervention on Apple's side. Has anyone been able to fix this on their end and not only when App Development called? I went through tons of the feedback and tried it all and it doesn't seem to be fixed. It's been a month or so like this. I can't get any info on who to call. I sent in a report to feedback assistant and through app developer support

For the past couple of days having a problem with Xcode 26.4. When I try to upload an archive to App Store Connectit gets stuck on "Uploading". I see the progress bar about 70% fulland a "Preparing to upload xxxx.ipa" label below. Letting it sit overnightrestarting Xcodemachineetc. and the same result. Anybody else seeing?

Hi everyone, I’m an indie iOS developer working on Kleioan AI voice keyboard extension that lets you dictate text quickly anywhere you can type. I’m looking for a small group of beta testers who are willing to try it through TestFlight and share feedback about stabilityUXand accessibility. What Kleio does Adds a custom keyboard so you can press the mic button and dictate instead of typing. Uses AI to turn rough speech into cleaned‑upproperly punctuated text. Lets you pick different writing s (e.g. more formal vs more casual) for how your dictation should read. Supports a personal dictionary for custom words and names. Keeps transcript history on‑device by defaultwith optional cloud sync and improvement sharing. Includes a “Privacy Mode” toggle when you don’t want anything uploaded. What I’d love feedback on Onboarding flow for first‑time setup and keyboard enabling. The dictation experience inside real apps (MessagesNotesMailsocial appsetc.). Latencyaccuracyand how well the edited text matches what you meant to say. Keyboard layoutbutton placementand any confusing interactions. Accessibility and inclusion: How well it works with VoiceOver / Switch Control. Any issues with contrasttouch targetsor labels. Any specific needs for users who rely on voice input more than typing. TestFlight link You can join the beta here: https://testflight.apple.com/join/jGY1fZ7S External group: “Twitter” (currently around 9 testers). No login is required for basic dictation; some settings sync features use account sign‑in. How to send feedback Through TestFlight’s built‑in feedback / screenshots. If you run into crashesunexpected latencyor accessibility problemsdetails like device modeliOS versionand what app you were dictating into are extremely helpful. Thanks in advance to anyone who’s willing to try Kleio and help me make the keyboard more reliable and accessible.

Hi, I’m experiencing a server-side error in App Store Connect when trying to submit a TestFlight build for review. Details: App: Ngoc Rong 2 Platform: iOS Build status: Complete Distribution: External Testing App Store Connect Web (Safari / Chrome both tested) Steps: Go to TestFlight → Select build Click “Submit for Review” Fill in “What to Test” Click Submit Result: Popup shows: "There was an error processing your request. Please try again later." Notes: Build processing completed successfully Internal testing works External group already created Issue happens consistently Tried different browsers and cleared cache Same issue across multiple builds Is this a known App Store Connect issue? Is there any workaround? Additional information: I have already contacted Apple Developer Support. Case ID: 102871190604 If neededI can provide further details or logs. Thank you.

Hello, I have an issue with In-App Purchases during App Review. In TestFlight and Sandboxeverything works correctly: Products are loaded Subscriptions are visible Purchase completes successfully HoweverApple reports that the purchase fails during review. My subscriptions are: Created and active in App Store Connect Attached to the app version Paid Apps Agreement accepted I also added all required information (pricedurationEULAprivacy policy). Why would purchases work in TestFlight but fail during App Review? Thank you for your help.

Hello, I made my app icon with Icon Composer and added the .icon file directly to my Xcode project. I noticed that the icon preview in Icon Composer looks one waywhile the icon shown on the App Store looks different. Details: I am using the .icon file directly in the project I am not using an exported PNG for the app icon I did not add a separate background image The background was set with fill in Icon Composer The preview in Icon Composer looks as expected The App Store version has a different appearance I would like to ask whether this difference may come from: App Store processing caching or a recommended Icon Composer setup for background fill If anyone has seen something similarI would appreciate any guidance. I can also share screenshots of the Icon Composer preview and the App Store result.

When downloading an appI often cannot download it. What is the reason?

Hi, My app is waiting for review since Saturday at 5:42 PMso is TestFlight. It has been rejected a couple of timesand errors were fixed with each update. Is this normal?

I have a app that has both mobile and watch versions. Recently some testers report that the watch app could not be launched if the put the app in the background and then resume. And if they kill the app and try to launch againthere is no any response when tapping the app icon. I managed to export some system logs by installing a sysdiagnose profileand this info looks suspicious

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!

Update: Turns out it works for othersapparentlyand I also found one of my Macs where it does worktoo. So it must be something pertinent to my systems. Oddlythoughthe same ones where it now fails used to work because I had TestFlight enabled there before. I have TestFlight set up on App Store Connectand I have already about 50 testers subscribed. TodayI found that the Public Link does not work any more: Once TestFlight.app is installedand one clicks the link to add my app to TestFlightit always shows the error ""Unable to Open Link" in TestFlight.app: I've tried this on several Macs (Ventura and Sonoma)and with different Accountsboth where the app was already added or not. Is something generally brokeni.e. do others see the same issue with their TestFlight linksor is it just me? How do you suggest I get this resolved? Here's an example link I set up for this purpose - it only allows a handful of subscribersso please do not actually subscribe but just see if you even get allowed toor if you get the same error if you must try: https://testflight.apple.com/join/oV8NNojg And here's how it's set up:

Hi, I'm trying to set up external testing for my iOS app on TestFlight but I can't find the External Testing option anywhere in App Store Connect. My setup: I'm the Account Holder I've uploaded two builds (build 128 via "TestFlight Internal Only"build 130 via "App Store Connect" distribution) I have one internal group with myself added as a tester Both builds show as "Complete" The UI I see does NOT match the documentation. There is no sidebar with "Internal Testing" / "External Testing" sections. I access TestFlight via a dropdown at the top of App Store Connectwhich takes me to an iOS Builds list. Clicking into a build shows Test InformationGroupsand Individual Testers — but no way to create an External group or find a public link anywhere. I've tried navigating directly to appstoreconnect.apple.com/apps/[APPID]/testflight/groups but get "We can't process your request." Is there a new App Store Connect UI that has moved where External Testing lives? Is there anything else that needs to be completed before External Testing becomes available for a brand new app? Thanks

I have sent an invite to a user for internal testing. They have received the email and clicked the accept test link. It takes them to App Store Connect web login screen. I do not see that they have accepted the role on my dashboard and they do not have access to my app on Testflight. Has anyone had this/similar issue and resolved it?

I’m looking for a small number of iPhone users to test an app I’ve been building and give honest feedback on the UX. The app is called Triovel. It’s for a problem I kept running into after trips: photos end up in camera rollplans are buried in chatand later it’s surprisingly hard to reconstruct what actually happened on each day. The core idea is simple: rebuild or record a trip into a timeline of activitiesthen attach photos/notes to the right parts of the trip so everything stays together. At this stageI’m not looking for generic “nice app” feedback. What I need most is feedback on: first-time onboarding clarity whether rebuilding a past trip feels intuitive where the flow feels slowconfusingor unnecessary whether the timeline structure makes sense right away Good fit if you: recently came back from a trip have an upcoming trip or have old travel photos you never properly organized iPhone only for now. Early betaso I expect rough edges. If anyone is open to trying it through TestFlight and giving blunt feedbackI’d really appreciate it. TestFlight: https://testflight.apple.com/join/6FJp6AMG

I’ve had an issue with all of my apps. Where I push my build to TestFlight and then the image pops up. I’ve troubleshooted EVERYTHING. My account has no issues on itno payment or compliance issues. I’ve looked to reddit for adviceone user says they need there app to get approved by applei got a couple apps to have there update approvestill the bug persist. Whether the app is on the App Store or a work in progress nothing works.

I have a app that has both mobile and watch versions. Recently some testers report that the watch app could not be launched if the put the app in the background and then resume. And if they kill the app and try to launch againthere is no any response when tapping the app icon. I managed to export some system logsand this info in the screenshot looks suspicious. Does anyone have the same issue? Recently the app has been transferred to another developer accountnot sure if it is relatedthis TestFlight version was rebuilt with the new team

Hi folksI had a similar issue I was able to replicate without fail: Public beta submission fails with: "Beta app contract is missing" POST /iris/v1/betaAppReviewSubmissions returns 422 Error: TF_BETA_APP_REVIEW_RESPONSE Internal TestFlight installs fail with: "The requested app is not available or doesn't exist" Adding apps to beta review also fails I was unable to: Add builds to public testing groups Submit builds for TestFlight review Reliably update TestFlight metadata ("What to Test"etc.) The fix: filed via Feedback Assistant (not Developer Support email). Included a HAR capture of the failing request and response headersalso provided all affected App IDs (even though this was account-wide). Got traction within a couple days after filingmuch faster than waiting on Developer Support. Note: In my case this affected every app on the account. From what I’ve seenthis may be triggered by changes to tester groups (adding/removing testers)but this is not confirmed. Seems to be a backend contract/entitlement desync Apple-side. Hope this helps someone.