Hello, My app RecipePop seems to be stuck in the App Review process and I’m trying to understand if something might be wrong with the submission. App ID (Apple ID): 6758273317 Timeline: I have been submitting versions for a week and they remain in "Waiting for Review" for days.. Please help review this submission as soon as possible! My users are currently facing a bug that should have been fixed in this version. Any guidance would be greatly appreciated. Thank you.

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?

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?

Hello, I’m facing an issue installing my app from TestFlight on a physical iPhone device. App & Environment App: Desi Charades Framework: Flutter Distribution: TestFlight Build status: Upload completed Device: iPhone 7+ iOS version: 15.6 Tester type: Internal Apple Developer Program: Paid account Issue Description After uploading a build successfully to App Store Connect and adding it to TestFlight, the app appears in TestFlight with the Install button. However, when I tap Install, I receive the following error on the device: “Could not install Desi Charades App. The requested app is not available or doesn’t exist.” The build is visible in TestFlight, but installation fails immediately. Upload Warnings During archive upload, App Store Connect shows the following warnings: Upload Symbols Failed The archive did not include a dSYM for: ffmpegkit.framework libavcodec.framework libavdevice.framework The app uses ffmpeg-kit (Flutter plugin), which ships precompiled frameworks. Steps Already Checked Build shows in TestFlight Build added to test group Tester is assigned correctly Correct Apple ID signed in on device Device restarted Waited for processing to complete App Store availability set to “All Countries or Regions” Questions Can missing dSYM files for ffmpeg-kit frameworks cause TestFlight install failures? Are there additional TestFlight availability or processing checks that could cause this error? Is this error related to TestFlight build propagation or caching on Apple’s side? Any guidance on what could cause TestFlight to show the app but fail installation would be appreciated. Thank you.

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

Posting this wondering anyone from App Review may be able to help. I submitted two builds for External TestFlight builds. My iOS build got approved within a day, but my tvOS version is still stuck in "waiting for review" for four days now. Wondering if there's anything I can do, perhaps remove from review and re-upload a new build or will this effectively remove me from a queue? Many thanks in advance. I'm unable to find a submission ID for this as I assume they're not available for TestFlight reviews?

I am a beta tester. I successfully tested an app this week. However, a different app, by a different developer is generating the “TestFlight is unavailable. Try again” error. I have force closed, and then deleted the TF app, and restarted A16 iPad running 26.3.1 iPadOS, then redownloaded to no effect. I have worked with an Apple Senior Support advisor, and found no network, Apple ID problems on my end after troubleshooting for nearly 2 hours. The developer tried emailing me the link - didn’t work. Now, update builds by developer are now showing the same error on other beta testers iPads, - however, one tester can download the app for beta testing on an iPad Pro M4. The app will download to my phone as well as others´ phones, running current update, but not my iPad. I changed my Apple ID password, reset my network, and nothing works.

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 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 have created and verified a new sandbox account in Users and Access. Now I want to test my in-app purchases with this account on my iPad Air in my iOS game. I have already uploaded a build to TestFlight. Then I have downloaded and installed my game from TestFlight on my iPad Air. How can I login on my iPad Air with my new sandbox account to test my in-app purchases in my game?

I too have been in "waiting in review" for longer than expected. What is the normal time for a review?

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.

My app's in-app purchase works perfectly (i) locally (ii) in TestFlight internal testing (iii) in TestFlight external testing in the US. Where's the issue? Well I have one beta tester (TestFlight external tester) in the Philippines. She is unable to purchase. Her Apple ID region and device region are set to Philippines. My IAP has all regions and territories enabled and I can see the Philippine Peso pricing on App Store Connect. She keeps seeing the price in USD rather than PHP, which, based on my searching around, seems to be common in TestFlight. But, she also keeps getting an error "Account Not In This Store - Your account is not valid for use in the US Store. You must switch to the Philippine store before purchasing". Clicking on "Change Store" doesn't help. From searching, it seems despite seeing the price in $ she ought to be able to complete the fake purchase. Is this expected in TestFlight? I am apprehensive before submitting my app for final approval if there are going to be issues in purchasing internationally. The code is StoreKit2's product.purchase() - it's opaque to developers, and Apple is supposed to handle it correctly. Not sure what else I can do as far as the code goes. I have successfully been able to view pricing in dollars, euros, and Philippine Peso by setting the storefront to the US, Germany, and Philippines in a local Storekit config file on an iOS simulator. So I am kind of confident that it is a TestFlight issue, but it feels weird to say something like 'ah it's a TestFlight issue, it'll work in production' :) Ideally TestFlight should be identical to production. Shouldn't it? I am waiting on another international tester (this one is in Brazil) to get another data point. Has anybody encountered something similar to this before? Also, any pointers for writing an automated UI test for this? What API / sample code etc.?

After my beta internal testers receive the App Store Connect invitation and tap to accept, the TestFlight email with download link is taking DAYS to arrive. Apple, you need to look at the provisioning servers. This experience can deter Apple developers.

100% new here, and probably trying to jump the gun here. I've released my 1st build to TestFlight for some people to test, but till now the app is still under review. Does it always take this long (day 4 now) for a 1st build to be reviewed, or am I missing something here?

Full Report {"app_name":"Exueshi PC Desktop","timestamp":"2026-02-28 18:02:50.00 +0800","app_version":"1.0.20","slice_uuid":"4c4c4476-5555-3144-a1a1-7e047782f52d","build_version":"1.0.20","platform":0,"bundleID":"com.exueshi.pcdesktop","share_with_app_devs":0,"is_first_party":0,"bug_type":"309","os_version":"macOS 26.1 (25B78)","roots_installed":0,"name":"Exueshi PC Desktop","incident_id":"B1529D77-1AB2-4523-A7D1-288F3CF10E88"} { "uptime" : 33000, "procRole" : "Default", "version" : 2, "userID" : 501, "deployVersion" : 210, "modelCode" : "MacBookPro16,1", "coalitionID" : 4905, "osVersion" : { "train" : "macOS 26.1", "build" : "25B78", "releaseType" : "User" }, "captureTime" : "2026-02-28 18:02:50.5267 +0800", "codeSigningMonitor" : 0, "incident" : "B1529D77-1AB2-4523-A7D1-288F3CF10E88", "pid" : 10285, "cpuType" : "X86-64", "roots_installed" : 0, "bug_type" : "309", "procLaunch" : "2026-02-28 18:02:50.4101 +0800", "procStartAbsTime" : 33974865865372, "procExitAbsTime" : 33974982166804, "procName" : "Exueshi PC Desktop", "procPath" : "/Users/USER/Documents/*/Exueshi PC Desktop.app/Contents/MacOS/Exueshi PC Desktop", "bundleInfo" : {"CFBundleShortVersionString":"1.0.20","CFBundleVersion":"1.0.20","CFBundleIdentifier":"com.exueshi.pcdesktop"}, "storeInfo" : {"deviceIdentifierForVendor":"B7637F07-4339-5AC8-9EF3-70F9C5BFADD2","thirdParty":true}, "parentProc" : "launchd", "parentPid" : 1, "coalitionName" : "com.exueshi.pcdesktop", "crashReporterKey" : "A1F7F2B6-2663-5318-1FAE-D6C4B66DD3C2", "appleIntelligenceStatus" : {"reasons":["deviceNotCapable"],"state":"unavailable"}, "developerMode" : 1, "codeSigningID" : "", "codeSigningTeamID" : "", "codeSigningFlags" : 16777216, "codeSigningValidationCategory" : 0, "codeSigningTrustLevel" : 4294967295, "codeSigningAuxiliaryInfo" : 0, "bootSessionUUID" : "681A76FB-622D-4E50-8BD0-1921F4E47248", "bridgeVersion" : {"build":"23P1072","train":"10.1"}, "sip" : "disabled", "exception" : {"codes":"0x0000000000000000, 0x0000000000000000","rawCodes":[0,0],"type":"EXC_CRASH","signal":"SIGKILL (Code Signature Invalid)"}, "termination" : {"flags":66,"code":1,"namespace":"CODESIGNING","indicator":"Taskgated Invalid Signature"}, "extMods" : {"caller":{"thread_create":0,"thread_set_state":0,"task_for_pid":0},"system":{"thread_create":0,"thread_set_state":0,"task_for_pid":0},"targeted":{"thread_create":0,"thread_set_state":0,"task_for_pid":0},"warnings":0}, "faultingThread" : 0, "threads" : [{"triggered":true,"id":1279396,"threadState":{"r13":{"value":0},"rax":{"value":0},"rflags":{"value":512},"cpu":{"value":0},"r14":{"value":0},"rsi":{"value":0},"r8":{"value":0},"cr2":{"value":0},"rdx":{"value":0},"r10":{"value":0},"r9":{"value":0},"r15":{"value":0},"rbx":{"value":0},"trap":{"value":0},"err":{"value":0},"r11":{"value":0},"rip":{"value":4468977232,"matchesCrashFrame":1},"rbp":{"value":0},"rsp":{"value":140701890890536},"r12":{"value":0},"rcx":{"value":0},"flavor":"x86_THREAD_STATE","rdi":{"value":0}},"frames":[{"imageOffset":20048,"symbol":"_dyld_start","symbolLocation":0,"imageIndex":0},{"imageOffset":0,"imageIndex":1}]}], "usedImages" : [ { "source" : "P", "arch" : "x86_64", "base" : 4468957184, "size" : 647168, "uuid" : "2378f215-945e-342f-aecb-fee14f38b7b0", "path" : "/dyld_path_missing", "name" : "dyld_path_missing" }, { "source" : "P", "arch" : "x86_64", "base" : 4457902080, "size" : 8192, "uuid" : "4c4c4476-5555-3144-a1a1-7e047782f52d", "path" : "/main_executable_path_missing", "name" : "main_executable_path_missing" }, { "size" : 0, "source" : "A", "base" : 0, "uuid" : "00000000-0000-0000-0000-000000000000" } ], "vmSummary" : "ReadOnly portion of Libraries: Total=992K resident=0K(0%) swapped_out_or_unallocated=992K(100%)\nWritable regions: Total=8332K written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=8332K(100%)\n\n VIRTUAL REGION \nREGION TYPE SIZE COUNT (non-coalesced) \n=========== ======= ======= \nSTACK GUARD 56.0M 1 \nStack 8192K 1 \n__DATA 136K 2 \n__DATA_CONST 32K 2 \n__DATA_DIRTY 16K 2 \n__LINKEDIT 368K 4 \n__TEXT 640K 2 \nshared memory 8K 2 \n=========== ======= ======= \nTOTAL 65.2M 16 \n", "legacyInfo" : { "threadTriggered" : { } }, "logWritingSignature" : "2ba49213878463e7d643516687119b80d674c537", "trialInfo" : { "rollouts" : [ { "rolloutId" : "65a8173205d942272410674b", "factorPackIds" : [ "65d39fa4cb0e2417d11ce5f6" ], "deploymentId" : 240000001 }, { "rolloutId" : "63f9578e238e7b23a1f3030a", "factorPackIds" : [ ], "deploymentId" : 240000005 } ], "experiments" : [ ] }, "reportNotes" : [ "dyld_process_snapshot_get_shared_cache failed" ] } Above is my crash report Please help me

Hi, I’m running into a persistent issue in App Store Connect related to TestFlight and app reviews, and I’m hoping someone has seen this before. Around two weeks ago, I 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 appear, but 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 point, I cannot update two existing apps, and 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 apps, not just one Nothing changed on my side (no contract updates, no account changes) before this started happening. I’ve already reached out to Apple Developer Support multiple times, but unfortunately haven’t received any response so far, which makes it unclear how to proceed. Has anyone experienced this issue or found a resolution? Any insight would be greatly appreciated. Thanks!

An app build is uploaded using Xcode 26.3 RC and fully validated/provisioned/processed at AppStoreConnect that shows build is Complete/Ready to Test Export compliance has been done Internal testers have been added to internal testing group Internal testers have accepted invite App is visible with all details in Test Flight on testers' iPhones (running 26.3 final) Internal testers tap App but Install button NEVER appears and testers get request for code to redeem app but invitation email does NOT include redeem code Testers cannot download and install app What is going on with TestFlight Apple?

We are creating an app and app is uploaded on the TestFlight but it is not allowing to download from TestFlight. We are unable to connect to Apple Developer Support teams. Any one please guide us why it is showing error when we try to download from iPhone App store ( The requested App is not available or does not exist)