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

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 9th, 2026. What’s concerning is that this isn't just affecting the production build for the App Store, but 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 9, 2026. Status: Stuck at "Waiting for Review" (never transitioned to "In Review"). Communication: No messages in the Resolution Center, no metadata rejections, and 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 ago, but no actual progress. Account Status: All agreements (Paid Applications, etc.) 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 stuck, did "bumping" the version number (e.g., 1.0 to 1.1) actually clear the ghosted status, or 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 yes, should 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 3, and 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 TestFlight, not 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 day, 2 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 assistance, and called the help number. Thank you in advance for any help. I appreciate the community.

Hi, I’m seeing a strange TestFlight issue. My builds process successfully in App Store Connect, appear in TestFlight, and are assigned to internal testers, but 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 workflow, so 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 times, including old builds which had been distributed in the past to no avail. I'm not able to distribute to any tester group, please advise.

Hello, My app was rejected on iPad (iPad Air 11-inch M3, iPadOS 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 devices, I test without a local StoreKit configuration file to fetch products from App Store Connect. The subscription UI (title, duration, price) displays correctly when products are returned. At the time of review, the 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 review, the required information (title, price, duration) was not visible, which likely triggered the 3.1.2 rejection. Additionally, in TestFlight I sometimes see inconsistent behavior where the app appears but cannot be installed (“App Not Available”). Also, my app was rejected, but 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 testing, please 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 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.

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 project, if I include ARKit and upload it to testflight, when 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 on, any help would be massively appreciated!

Hi everyone, We are facing a critical blocker with our macOS app processing. Since March 5, 2026, every single build we have uploaded (8 builds total) has been stuck in the "Processing" state for over 4 days. For our project, due to the large binary size, processing usually takes about 4 to 6 hours normally. However, we 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 8, 3:09 PM (Processing) 1.0.0 (443): Mar 8, 5:36 AM (Processing) 1.0.0 (440): Mar 7, 6:37 AM (Processing) 1.0.0 (438): Mar 6, 5:01 PM (Processing) 1.0.0 (434): Mar 6, 12:04 AM (Processing) 1.0.0 (433): Mar 5, 6:26 PM (Processing) 1.0.0 (432): Mar 5, 10:51 AM (Processing) 1.0.0 (431): Mar 5, 6:11 AM (Processing) (Note: The last successful build was 1.0.0 (429) on March 4, which processed within the expected 6-hour window.) There have been no changes to our project settings, Info.plist, or 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 5th, I've since pulled that and resubmitted Monday this week, to see if things might have unstuck themselves, but no luck) I can't even get a build approved for TestFlight on anything. This is getting silly now, total lack of communication - emails go unanswered. I will give the lovely team in Ireland their dues though, as always helpful on the phone, but 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 invitation, accepted it, and the app is visible in the TestFlight app on Apple Vision Pro. However, the moment we click the "Install" button, an 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 group, waited, and 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 error, I created a completely new App Identifier (Bundle ID) for the same project code and uploaded it as a new app record. In this case, TestFlight worked perfectly, and 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 record, or is this a backend bug that only Apple Support can resolve? Any insights or workarounds would be greatly appreciated.

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 invitation, accepted it, and the app is visible in the TestFlight app on Apple Vision Pro. However, the moment we click the "Install" button, an 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 group, waited, and 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 error, I created a completely new App Identifier (Bundle ID) for the same project code and uploaded it as a new app record. In this case, TestFlight worked perfectly, and 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 record, or is this a backend bug that only Apple Support can resolve? Any insights or workarounds would be greatly appreciated.

I removed TestFlight app from old device (email is no where exists in AppStore connect in Testers) which has different email than my AppStoreConnect email. Now I am trying to get invitation to the device which has same email as my AppStoreConnect, but keep getting -> Couldn't Load App The apple Account you're currently signed in with, , doesn't match the one assiciated to this invitation. You can sign in to TestFlight with original Apple Account, , or request a ne…. Where as all other apps in the AppStore connect shows up fine in the TestFlight using appstore connect email. Followed all the reset & settings mentioned but no luck so far.

Hi, I am submitting auto-renewable subscriptions for the first time for a brand new iOS app (never approved before). Setup: App ID has In-App Purchase capability enabled Subscriptions created under a subscription group All metadata (pricing, localization, availability) completed Subscriptions currently show In Review Testing via TestFlight build Bundle ID matches App Store Connect Using react-native-iap (StoreKit under the hood) When calling: await getSubscriptions({ skus }) I consistently get: products fetched: 0 ProductsUnavailableError Also, the app version page does not show the “In-App Purchases and Subscriptions” section. Question: For a brand new app, will StoreKit return empty products while the first subscriptions are in review? Do the first subscriptions need to be approved and/or attached to a new app version before they become available in TestFlight sandbox? Thanks for any clarification.

Hi everyone, I am writing this out of pure desperation because I honestly don't know what else to do or where to turn. My app has been stuck in the review process since February 9th (almost 3 weeks now), and I feel like I am completely trapped in a black box. I have tried every official channel available to get at least some information: I submitted requests for an expedited review. I opened 3 separate tickets with Developer Support, but received absolutely zero response. Just complete, deafening silence. I finally called the developer hotline. The representative was polite but completely unhelpful. I was basically told that "everything is fine, this timeline is normal, we can't do anything to help you, just keep waiting." Just to put this wait time into perspective, while sitting in this Apple "black box" waiting for a single message, I have managed to do the following: Registered a Google Play Developer account and fully verified my identity. Almost completely rewrote my entire app from scratch, translating it from Swift to Kotlin. Uploaded the Android version, got it approved, and I am already on Day 8 of closed testing in Google Play! Meanwhile, in App Store Connect, absolutely nothing has changed. No status updates, no rejections, no questions from the reviewers, no replies to my tickets. Just an absolute void. Has anyone else experienced this kind of extreme delay and complete lack of communication recently? For context, here are my details: Submission ID: db1ffb72-8f0f-49bc-b215-179e1e179b7d Apple ID: 6756239914 Any advice or shared experiences would be deeply appreciated. Thank you.