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.

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

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

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.

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?

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.

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.

I'm just looking for help/guidance on what if something I did wrong in my build submission? The first test flight build I submitted went through in about 1 day2 build updates after that went through and were deployed for my test flight participants each in less than 24 hours. The last build I have submitted has been 6 days now. I have had to submitted multiple builds and cancel a few of them as I keep making progress on my app. I have submitted a ticket for assistanceand called the help number. Thank you in advance for any help. I appreciate the community.

HiI’m seeing a strange TestFlight issue. My builds process successfully in App Store Connectappear in TestFlightand are assigned to internal testersbut installation fails immediately with: “The requested app is not available or doesn’t exist.” What I’ve verified: • builds are processed/completed • apps are visible in TestFlight • internal tester groups are configured • agreements/banking/tax are active This affects multiple apps in the same developer account. The issue started after adding a widget extension and moving to a new Swift-based workflowso I’m trying to isolate whether this is: • signing/provisioning/entitlements • widget extension misconfiguration • or a backend issue on Apple’s side I’ve already contacted Apple Developer Support and submitted Feedback Assistant reports. Has anyone seen this exact behavior before?

In App Store Connect I've uploaded a new build about 11 hours ago and but I'm unable to distribute the App to my tester groups - including internal. The internal group is grayed out. I am able to Select an External group but they actually do not receive any email notification nor do they see any update within their TestFlight App. I've attempted to upload the build a few timesincluding old builds which had been distributed in the past to no avail. I'm not able to distribute to any tester groupplease advise.

Hello, My app was rejected on iPad (iPad Air 11-inch M3iPadOS 26.2.1) with two related issues: Guideline 2.1 – Performance – App Completeness “The app exhibited one or more bugs that would negatively impact users. Bug description: the premium subscription cannot be loaded properly.” Guideline 3.1.2 – Business – Payments – Subscriptions “The submission did not include all the required information for apps offering auto-renewable subscriptions.” I am using StoreKit 2 with SubscriptionStoreView to present the auto-renewable subscription. During development: Subscriptions load correctly in the simulator (sandbox). On real devicesI test without a local StoreKit configuration file to fetch products from App Store Connect. The subscription UI (titledurationprice) displays correctly when products are returned. At the time of reviewthe Paid Apps Agreement was not active. I suspect this may have caused the subscription products to fail loading on the review device. Since then: Paid Apps Agreement is now Active. SubscriptionStoreView should automatically show required metadata. Because the subscription failed to load on iPad during reviewthe required information (titlepriceduration) was not visiblewhich likely triggered the 3.1.2 rejection. Additionallyin TestFlight I sometimes see inconsistent behavior where the app appears but cannot be installed (“App Not Available”). Alsomy app was rejectedbut the subscription is still waiting for review. I would really appreciate guidance on the following: Am I potentially missing any required configuration that could prevent products from loading in production? Is there any propagation delay after activating the Paid Apps Agreement that could affect product availability? If I am overlooking something in configuration or testingplease let me know what I should specifically verify before resubmitting. Thank you very much for your help.

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.

While WhatToTest..txt was being used in xcode cloud. I wish this feature should just being adopted to functioned from XCode archive and upload to set initial release note from the build pipeline directly from xcode in machine

Even when making a completely fresh Unity projectif I include ARKit and upload it to testflightwhen I open it on my ipad it says 'Couldn't Load App'. If I don't include testflight the app opens fine. If I build the app directly to my ipad the app works fine. It opens if I set ARKit to 'optional' but then the AR doesn't work. I have included a camera and location usage description so it's not that. Really not sure what's going onany help would be massively appreciated!

Hi everyone, We are facing a critical blocker with our macOS app processing. Since March 52026every single build we have uploaded (8 builds total) has been stuck in the "Processing" state for over 4 days. For our projectdue to the large binary sizeprocessing usually takes about 4 to 6 hours normally. Howeverwe now have a long queue of builds that haven't transitioned to "Ready to Submit" for up to 80+ hours. Stuck Builds List: 1.0.0 (444): Mar 83:09 PM (Processing) 1.0.0 (443): Mar 85:36 AM (Processing) 1.0.0 (440): Mar 76:37 AM (Processing) 1.0.0 (438): Mar 65:01 PM (Processing) 1.0.0 (434): Mar 612:04 AM (Processing) 1.0.0 (433): Mar 56:26 PM (Processing) 1.0.0 (432): Mar 510:51 AM (Processing) 1.0.0 (431): Mar 56:11 AM (Processing) (Note: The last successful build was 1.0.0 (429) on March 4which processed within the expected 6-hour window.) There have been no changes to our project settingsInfo.plistor entitlements since the last successful build. This is completely halting our scheduled update release. Is anyone else experiencing a similar backlog with large macOS binaries? Or is there a known issue with the App Store Connect pipeline for the macOS platform recently? Any help or investigation from Apple engineers would be greatly appreciated. (Feedback ID: FB22156358)

Hi, I know many of us are stuck right now it seems - I'm in the 12th Feb club (had another app that was since 5thI've since pulled that and resubmitted Monday this weekto see if things might have unstuck themselvesbut no luck) I can't even get a build approved for TestFlight on anything. This is getting silly nowtotal lack of communication - emails go unanswered. I will give the lovely team in Ireland their dues thoughas always helpful on the phonebut they also seem to have no information and their expedited review requests go no where. App ID is 6758779640

Hi everyone, I’m encountering a persistent issue with a visionOS app distributed through TestFlight for internal testing. The Problem: I have successfully archived and distributed the build as an Internal Test. The testers (including myself) received the invitationaccepted itand the app is visible in the TestFlight app on Apple Vision Pro. Howeverthe moment we click the "Install" buttonan alert pops up saying: "The requested app is not available or doesn't exist." Context: Platform: visionOS (Targeting Vision Pro). App History: This is an ongoing project where the last distribution was about 5 months ago. The app has never been submitted for formal App Review or public release; it has only been used for TestFlight. Account Status: All agreements (including the Paid Applications Agreement) are active and in effect. What I have tried (but did not work): Re-uploading builds: Increased both version and build numbers and re-archived. Resetting Test Groups: Deleted the existing internal testing groupwaitedand created a new group to re-invite testers. Tester Association: Removed all testers and re-added them to force a new invitation email. Device-side: Signed out and back into "Media & Purchases" on the Vision Pro. Key Observation: To determine if it was a project-level configuration errorI created a completely new App Identifier (Bundle ID) for the same project code and uploaded it as a new app record. In this caseTestFlight worked perfectlyand I could install the app without any issues. This leads me to believe that the original Bundle ID is stuck in some kind of "detached" or "stale" state on the App Store Connect backend. Has anyone experienced a specific Bundle ID being "corrupted" in the TestFlight system after a period of inactivity? Is there a way to force a full reset of the TestFlight status for an existing app recordor is this a backend bug that only Apple Support can resolve? Any insights or workarounds would be greatly appreciated.