Hi everyone, I'm experiencing an unusually long wait time for my TestFlight external build review and wanted to see if others are facing similar issues in 2026. Current Status: Platform: iOS App Version: 1.2.90 (Build 24) Build Type: TestFlight External Testing Current Status: In Review - not "Waiting for Review" Time in Current Status: Over 2 weeks Submission Timeline: Current Submission: Wednesday at 9:49 AM (iOS 1.2.90 Build 24) Previous Submission: March 9, 2026 at 2:20 PM (iOS 1.2.90 Build 11) - Status: Completed (Rejected) Full History: March 9, 2026 2:20 PM - Initial submission (Build 11) March 15, 2026 5:25 AM - Rejection from Apple March 24 - April 15, 2026 - Multiple back-and-forth communications (5 messages total) April 15, 2026 2:22 PM - Last response from Apple Recent (Wednesday 9:49 AM) - Resubmitted new build (Build 24) Current - Still "In Review" after 2+ weeks What I've Tried: ✅ Addressed all rejection issues from the previous review ✅ Submitted a new build with higher build number (11 → 24) ✅ Submitted expedited review request through App Store Connect ✅ Contacted Apple Developer Support via email ✅ Requested phone callback for escalation What Concerns Me: The build has been stuck in "In Review" status for over 2 weeks This is AFTER already going through a full review cycle (rejection + resubmission) Normal review times are supposed to be 24-48 hours, even with the 2026 backlog The previous review cycle took over 1 month (March 9 → April 15) This is completely blocking our beta testing program Questions for the Community: Is anyone else experiencing 2+ week "In Review" times for TestFlight external builds in 2026? Does a previous rejection cause indefinite review delays on resubmission? Has anyone successfully resolved this by canceling and submitting a brand new build? Are there effective escalation paths beyond standard support channels? Could this indicate an account-level review issue? What I Understand: Review times have increased in 2026 due to higher submission volumes Previous rejections can lead to more thorough reviews However, 2+ weeks "In Review" (not even "Waiting") seems abnormal This delay is severely impacting our development timeline and beta testing plans. Any advice or shared experiences would be greatly appreciated! Thanks in advance for your help.

Hi, I got the error( IAPError(code: storekit_no_response, source: app_store, message: StoreKit: Failed to get response from platform., details: null) ) when run the code ( final InAppPurchase _iap = InAppPurchase.instance; Set kids = {‘some_available_product_id’} _iap.queryProductDetails(_kIds); ) from flutter I don’t know why this happened, can you let me know this?

Hi, I have been using Testflight iOS app to test my apps before releasing to production. Over the past few weeks, I am unable to install any of my apps through Testflight. I also don't get any email notification that my app is live on Testflight. This is really important and it would be really helpful if I can find any solution to this. Thank you so much.

Hello, I am unable to install my app from TestFlight even though the build appears valid and is in internal beta testing. The build was uploaded successfully to App Store Connect and shows as Testing / Internal Testing. The build metadata looks valid: processingState: VALID internalBuildState: IN_BETA_TESTING qcState: BETA_INTERNAL_TESTING usesNonExemptEncryption: false minOsVersion: 15.0 deviceFamilies: IPHONE supportedArchitectures: arm64 However, TestFlight installation fails, and the App Store Connect API returns: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING Beta contract is missing for the app. My App Store Connect agreements are all active. I checked Business > Agreements and both Paid Apps Agreement and Free Apps Agreement are Active. Bank accounts, tax forms, and compliance also appear Active. This also happens with a newly created app and a fresh build, so it looks like the TestFlight beta contract may be missing or detached on Apple’s backend. Has anyone seen this before, or is there a way to force App Store Connect to refresh the TestFlight beta contract state?

Beta testers outside the US, for our MacOS App, are being told their ID is not valid in the US Store and that they must switch to a store in their country. Yet the store switch fails Essentially beta testers outside the US cannot do testflight sandbox eCommerce for the Mac version of our app. Note that eCommerce on the Mac works for US based testers and eCommerce for the iOS/iPadOS works for testers in all territories. Many of these testers are in India, the UK and Canada. We believe that this is incorrect, that storeKit is not correctly detecting the AppStore Region for mac based testflight eCommerce. At this point we have 382 testers, most outside the US and we can only Beta Test our app with US users. Attached are images of the messages that are coming from storeKit: Here is a link to a video from a user in Canada who is demonstrating the problem (cut and paste into browser) https://youtu.be/kB818wfVld4 Here is another link to a video from a user in Canada who is demonstrating the problem (cut and paste into browser). https://youtu.be/7uAZKo8wpfU We see that there is another post with a similar problem. Similar eCommerce Problem Because eCommerce works in all territories on iOS/iPadOS but ONLY in the US for Mac we suspect that this is an error that either a DBA or a coder will need to fix. Any insights from anyone would be appreciated.

I have 4 iOS apps under one Developer team. None of them have ever been installable through TestFlight by my single internal tester since day 1. The error is always the same: "The requested app is not available or doesn't exist" — appearing only after the tester taps Install (the app DOES appear in the TestFlight app's list). Apps (all PREPARE_FOR_SUBMISSION, never released to App Store) AutoChoice — com.jiejuefuyou.autochoice — 4 valid builds, latest v1.0.1 (11) AltitudeNowPro — com.jiejuefuyou.altitudenow — v1.0.0 (2) valid PromptVaultPro — com.jiejuefuyou.promptvault — v1.0.0 (2) valid NewDaysUntil — com.jiejuefuyou.daysuntil — v1.0.0 (2) valid What's verified clean via App Store Connect API + web UI All 3 account-level agreements ACTIVE (Developer Program, Free Apps, Paid Apps) Banking + tax form filled All builds: state=VALID, expired=False, 88+ days remaining All builds in Internal Testers betaGroup buildBetaDetail.internalBuildState = IN_BETA_TESTING Tester sh1990***@hotmail.com state = ACCEPTED in all 4 betaGroups ASC TF group/builds page shows latest builds as "Testing" Distribution certificates: 2 active until 2027 App Store provisioning profiles: 8 active until 2027 usesNonExemptEncryption = False (export compliance set) contentRightsDeclaration = DOES_NOT_USE_THIRD_PARTY_CONTENT primaryCategory set on each app (LIFESTYLE / HEALTH_AND_FITNESS / PRODUCTIVITY) ageRatingDeclaration created (4+, all NONE) copyright filled betaAppReviewDetail filled (contact name/email/phone) appStoreReviewDetail filled Beta App Description, feedback email, marketing URL, privacy policy URL all filled 5 screenshots uploaded for AutoChoice (APP_IPHONE_67), 4 for AltitudeNow, 3 for DaysUntil 175 territories available What's verified on iPhone side iOS version ≥ 17 (build minOsVersion=17.0, satisfied) iCloud Apple ID = sh1990***@hotmail.com Settings → Media & Purchases Apple ID = sh1990***@hotmail.com TestFlight app signed in as sh1990***@hotmail.com All 4 apps visible in TF app's main list What's been tried (none worked) Force close TF app + reopen Sign out + sign in TF app Sign out + sign in Media & Purchases Restart iPhone Tap "View in TestFlight" link in invite email TF app's "Redeem" with invite code DELETE + 30s + POST tester record (Apple distribution cache reset) Multiple invite resends via POST /v1/betaTesterInvitations Patched all "Pending Submission" indicators that the API allowed (categories, content rights, age rating, copyright, review details, screenshots) POST /v1/appStoreVersionSubmissions returns 403 (not allowed for current version state) What we cannot try New build upload (Mac+Xcode chain not currently available; previous attempts via fastlane on macOS GitHub Actions runner cost 12+ hours of debug) Apple Configurator 2 (we're on Windows) The contradiction Apple's API and web UI both say the build is in beta testing and available to the accepted internal tester. The iPhone says "App not available or doesn't exist." This contradicts every part of the documented internal-testing flow. Question What ASC-side or account-side check could still be missing that's specifically blocking distribution to internal testers, given everything above is set? Is there an account-level "first-build flag" or distribution-eligibility flag invisible in the public API/UI that requires Apple intervention to flip on for new developer teams? Team ID: ZJ3FQ63UV3 First app created: late April 2026 First build uploaded: 2026-05-02 Any pointers appreciated.

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.

Hello, I am unable to use TestFlight for any app (existing or new), while production uploads work normally. All TestFlight actions fail with: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING There are no pending agreements in App Store Connect. This is an older account that previously used TestFlight successfully. This appears to be a missing or detached TestFlight Beta contract on Apple’s backend. Could this be manually reattached or re-provisioned? This is time-sensitive, as I need a TestFlight external testers link to submit an app for an upcoming hackathon. Apple Support case ID (for reference): 102817552619 Thank you.

Hello Apple Developer Support, We are experiencing an issue with TestFlight Internal Testing. Our internal testers can see the app and the assigned build in the TestFlight app, but when they try to install it, the installation fails with the following error: "Could not install [App Name]. The requested app is not available or doesn't exist." This issue happens with Internal Testing, so Beta App Review should not be involved. We have already checked the following: The build was uploaded successfully through Xcode using App Store Connect distribution. The build processing is completed. The build is assigned to the correct Internal Testing group. The testers are added as App Store Connect users and have access to the app. The app appears in TestFlight for the testers. Agreements, Tax, and Banking do not show any pending actions. Export Compliance / Missing Compliance does not show any pending actions. The issue happens on multiple devices. We have tried removing and reinstalling TestFlight, and uploading a new build number, but the issue still occurs. App details: App Name: WearNow AR Try-On Bundle ID: com.yakovchuk.wearnow Apple Developer Team ID: 6G4QX44Y4A Could you please check whether there is an account-level, app-level, or TestFlight backend issue that prevents this build from being installed by internal testers? This looks similar to multiple recent Apple Developer Forums reports where the app is visible in TestFlight, but installation fails with "The requested app is not available or doesn't exist." Thank you.

"Could not install . The requested app is not available or doesn't exist." when installing app from TestFlight" I've tried uninstalling and reinstalling the app, and even removed older versions. I emailed support, but I still haven't found a solution. Does anyone know the solution to this problem?

Error in TestFlight: “The requested app is not available or does not exist.” This happens on multiple iPhones and Apple IDs. Important: Builds from OTHER Apple Developer accounts install fine on the same devices. We tried new apps, new bundle IDs, new certificates, new provisioning profiles. Internal testing fails. External testing also fails. All Agreements, Tax, Banking, and membership requirements are completed and active. When configuring external testing in App Store Connect, we also get: “There was an error processing your request. Please try again later.” This has been happening for 3 weeks. Has anyone seen an Apple Developer account / TestFlight backend issue like this? Any solution besides contacting Apple Developer Support?

Hi Our team is not able to install the app from testflight after April 30. Install stops with the following error The requested app is not available or doesn't exist." This is a blocker for us. Please help resolve this.

I have a binary that successfully install & run on my Mac, that is build with codesign and pkgbuild with "Developer ID Application" and "Developer ID Installer" identities. I cannot figure out how to transform this pkg into a distribution package that fits with App Store and TestFlight. Xcode builds it fine and can run it seemingly, but cannot provide the App Store Distribution option in Organizer after creation of Archive. (Only Custom option.) I probably may not be able to specify properly the build Target as Release (don't know where to specify). (pkgbuild ->) productbuild -> Transporter is also an option, but don't know how to properly specify the productbuild --component options... I have a developer program and can generate the Apple developers certificate fine, such as "3rd Party Mac Developer Application/Installer". A pkg codesign'ed by them was rejected by the notarization process. My application is C and can be started again as New project from Xcode as "MacOS Command-Line Tool", so in other words my question can be said as "how can I organize a MacOS Command-line tool to conform as App Store distribution?" I am checking documents but so far cannot get the proper document. Any pointing to a document is appreciated.

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.

Does anyone know whether it is good practice or not to remove old builds? they're piling up...i don't know if apple wants us to have that trail or if they prefer we clean up old builds periodically. any kind of quick way to do this?

I have an app that i want to test but when i try to download it on TestFlight it keeps saying "The requested app is not available or doesn't exsist." I have tried different builds. Previously the same app was working. Please fix this asap.

Hello, I submitted a Family Controls (Distribution) entitlement request for my extensions a few days ago. My main app com.prionsdabord.app already has Family Controls (Distribution) approved. I need the same capability for my three extensions and i have already requested them: com.prionsdabord.app.DeviceActivityMonitorExtension com.prionsdabord.app.ShieldActionExtension com.prionsdabord.app.ShieldConfigurationExtension Team ID: 3H27T8RX6U App Apple ID: 6761482549 This is currently blocking my TestFlight distribution. Could you please with this request? Thank you.

Hi,i am trying to provide my newest build to my testers.I have to provide some information in the invitation mail, since many of them are new to the process.But after inviting my self as a test, Testflight keeps sending the outdated app description in the invitation mail.For the specific build, i changed the "What to Test" content and i also changed the "Beta App Description" in the "Test Information" Tab.But Testflight still sends the old text, which is nowhere to be found anymore.Am i doing something wrong? How can i fix this?

Has anyone seen Managed Background Assets get stuck before any download progress is reported on iPadOS 26.3 / TestFlight? We are using Apple-hosted managed asset packs for a large on-demand model download. The app can resolve the asset pack metadata: we can show the asset pack’s download size in the UI, so AssetPackManager.assetPack(withID:) appears to work. But when we call ensureLocalAvailability(of:), the UI stays at 0% indefinitely. We also do not receive any useful terminal state from statusUpdates(forAssetPackWithID:): no .began, .downloading, .failed, or .finished. The app remains responsive. The issue also appears persistent on the affected device/account. Reinstalling the app does not help, reinstalling TestFlight does not help, logging out and back in does not help, and restarting the device does not help. After each attempt, the app can still resolve the asset pack metadata/download size, but the actual download remains stuck before any progress or failure status is delivered. The suspicious part of the device log is that the managed helper starts normally, fetches/installs the manifest from TestFlight, but repeatedly fails to create its helper directory inside the app container: OurApp Initializing the asset-pack manager… OurApp Creating a proxy object for the helper service… OurApp activating connection ... name=com.apple.backgroundassets.managed.helper.service kernel Sandbox: no system container path found for ID "com.apple.backgroundassets.managed.helper.service" Managed Background Assets Helper Service Starting the Managed Background Assets Helper Service… Managed Background Assets Helper Service Configuring the directory suffix… Managed Background Assets Helper Service The directory suffix was successfully configured. Managed Background Assets Helper Service The extension token "<...>" was consumed. kernel Sandbox: Managed Background Assets Helper(...) deny(1) file-write-create /private/var/mobile/Containers/Data/Application/.../tmp/com.apple.backgroundassets.managed.helper.service Managed Background Assets Helper Service mkdir: path=/private/var/mobile/Containers/Data/Application/.../tmp/com.apple.backgroundassets.managed.helper.service/ mode= -rwx------: [1: Operation not permitted] After that, manifest fetching still seems to work: OurApp The asset-pack manager has been initialized. OurApp The system download-manager delegate has been assigned to the download manager. OurApp The app was installed for internal beta testing; checking for updates automatically… OurApp Refreshing the manifest… Managed Background Assets Helper Service The app with the bundle ID "..." is configured to use Apple hosting. Managed Background Assets Helper Service Asking the TestFlight extension via the App Store Daemon for the URL request... Managed Background Assets Helper Service Fetching the download manifest ... from TestFlight… Managed Background Assets Helper Service Installing a manifest at ".../Library/Application Support/.../Manifest.json"... But during/after manifest install, the same mkdir failure appears again: Managed Background Assets Helper Service Installing a manifest at ".../Manifest.json"... Managed Background Assets Helper Service mkdir: path=/private/var/mobile/Containers/Data/Application/.../tmp/com.apple.backgroundassets.managed.helper.service/ mode= -rwx------: [1: Operation not permitted] kernel duplicate reports for Sandbox: Managed Background Assets Helper(...) deny(1) file-write-create /private/var/mobile/Containers/Data/Application/.../tmp/com.apple.backgroundassets.managed.helper.service So the behavior seems to be: TestFlight/internal beta install Apple-hosted managed asset pack Manifest fetch succeeds Asset pack metadata resolves, including download size Actual local availability request never starts reporting progress No visible Background Assets failure reaches the app Logs show repeated sandbox file-write-create denial for the Managed Background Assets Helper trying to create /tmp/com.apple.backgroundassets.managed.helper.service inside the app container Reinstalling the app/TestFlight, logging out and back in, and restarting the device do not clear the stuck state On devices with 26.4, the issue doesn’t seem to exist Has anyone else seen this on iOS/iPadOS/macOS versions before 26.4? Is this a known issue in the Managed Background Assets helper/runtime? I noticed 26.4 added more local status APIs for asset packs, so I’m wondering whether this area changed in 26.4. Any hints on whether the sandbox denial is expected/noisy, or whether it could explain ensureLocalAvailability(of:) never progressing, would be appreciated.

I am having an issue where my builds are marked green and ready for testing, but when I go to install from TestFlight I get the following message: "Could not Install X App" "The requested app is not available or doesn't exist" I've tried troubleshooting with information found online, tried different testing users. New builds. All result in the same message. Multiple support emails to Apple Developer. No response in 8 days.