For a few months now, every time I try to load up testflight I get the setup prompt with continue, but when I click on it it says TestFlight is currently inavaible. try again. ive tried logging out of iTunes and back in, didn’t work. Restarted multiple times, nothing. I do get mails saying I got invited, but it doesn’t work. anyone got a solution for me?

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 (with warnings) 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.

Hello Apple Developer Community, I’m facing an issue when submitting my iOS app to App Store Connect. ITMS-90429: Invalid Swift Support libswiftDarwin.dylib, libswiftMetal.dylib, libswiftCoreAudio.dylib, libswiftsimd.dylib, libswiftQuartzCore.dylib, libswiftos.dylib, libswiftObjectiveC.dylib, libswiftDispatch.dylib, libswiftCoreGraphics.dylib, libswiftCoreFoundation.dylib, libswiftUIKit.dylib, libswiftCoreMedia.dylib, libswiftCore.dylib, libswiftFoundation.dylib, libswiftCoreImage.dylib aren’t at the expected location: /Payload/Runner.app/Frameworks. Move the file to the expected location, rebuild your app using the current public (GM) version of Xcode, and resubmit it. My setup: Using Flutter for iOS development Flutter version: 3.32.8 Xcode version: Version 16.3 What I have tried so far: Cleaned build folder: flutter clean Upgraded Flutter and CocoaPods to the latest version. Rebuilt the project using latest Xcode GM version. Verified that Always Embed Swift Standard Libraries is set to YES in Xcode. Reinstalled pods and ensured use_frameworks! is correctly set in Podfile. Despite this, I still get the same error. My questions: What is the correct way to ensure the Swift libraries are embedded in the correct location for Flutter apps? Is there any known issue when building with Flutter and integrating static .a libraries that could cause this problem? Has anyone successfully submitted a Flutter iOS app with external static libraries linked and avoided this error? Are there any manual steps required to fix the location of Swift dylibs during the build process? Thank you in advance for your help!

Hi everyone, I’m preparing an updated version of my older game Plum Nut so I can eventually return it to the App Store. I’ve uploaded a new build (1.1 build 8) and it shows up correctly in TestFlight for beta testing. However, when I try to install it on a supported device (iPad Pro 2020, iOS), I get this popup: “Could not install Plum Nut. The requested app is not available or doesn’t exist.” The build is processed and available in TestFlight, but installation always fails with this message. I have several games that install fine on TestFlight. This is the first and only case and time where I have encountered this. Details: Platform: iOS Build: 1.1 (8) TestFlight status: Available for testing Issue first occurred: Nov 18, 2025 I contacted Apple Developer Support, but they directed me to the forums for technical guidance. If anyone has encountered this issue or has suggestions on what might cause it, I would be very grateful for any insight. Thank you! — Rob / Protopop Games

Having been forced to use TestFlight for app distribution (Since Apple changed the policy) bug fixes are taking way too long to go through review. Users have issues, bug fixed in 10 minutes, new release takes 2 days to be reviewed. There has got to be a better way.

Hi everyone, I’m having trouble distributing my app via TestFlight. I created the app completely from scratch — new bundle ID, new build number, fresh provisioning profile, and certificates. Everything looks correctly set up in App Store Connect, and the build is marked as ready for testing. However, when I send the TestFlight link to testers, they get a message saying the app is "unavailable" or "not found." I’ve double-checked all settings, and I can’t figure out what I’m missing. Has anyone experienced this before or have any suggestions on how to fix it? Any help is appreciated!

Hi all, We can’t install our app from TestFlight. The app is visible in TestFlight for invited internal testers, but tapping Install fails immediately with: “The requested app is not available or doesn’t exist.” --Setup-- Distribution: TestFlight – Internal Testing Internal group created and testers added (invite accepted) Build processing status in App Store Connect: Complete TestFlight build status shows: Ready to Submit / Prepare for Submission Minimum iOS deployment target: iOS 15.0 Version/Build: 1.0.0 (1) What we tried Confirmed tester is signed into TestFlight with the same Apple ID email that was invited Removed/added testers to the internal group and resent invites Reinstalled TestFlight, signed out/in Verified build is assigned to the internal group Set and saved Monetization → Pricing and Availability → App Availability (All Countries/Regions) Question Has anyone resolved this issue? Is there a known TestFlight/App Store Connect stuck state that causes this error even for internal testing? Any recommended steps (new build number, group reset, availability/pricing settings, etc.)? Screenshots available (TestFlight error + App Store Connect build/group view). Thanks.

I have hosted the AASA file in our server and added the App associated domain and have added the local Appclip experience in Device settings with the same URL which i create Appclip QR. But when i install build from testflight i dont see the Appclip card coming up.Its working if i directly load it from xcode My associated domain - appclips:acviss.com (configured from main and appclip target) Qr code generated like this AppClipCodeGenerator generate --url https://acviss.com/restaurant1 --foreground 33AA22 --background FFFFFF --output myclip.svg In Device Setting>Developer>Local Experience URL Prefix - https://acviss.com/restaurant1 Bundle Id - com.acviss.RestApp.Clip AASA file hosted at https://acviss.com/.well-known/apple-app-site-association

The issue arises only when the .ipa is uploaded to App Store Connect via Xcode. When attempting to download the app through TestFlight, it crashes. This behaviour is isolated to TestFlight and does not occur in any other environment. To clarify the issue: the build is successfully running in Xcode across all iOS devices and versions without any problems. Additionally, the same production .ipa file downloaded from Firebase is functioning as expected.

Hi developers. I've been working on a Watch companion app for my product these past few days, and I'm currently trying to push it to TestFlight. I get stuck at the validation step with endless errors. The first one typically is missing WKApplication in Info.plist. That's fine, I'll add the field in Watch target > Info. Now more errors appear: Invalid UIDeviceFamily value of '1' and '2' Unsupported key UIRequiredDeviceCapabilities DTPlatformName value invalid Missing architecture, the bundle must contain arm64_32 because it's built with watchOS SDK 5+ I never set these values in the Info tab, so my guess is they're being overwritten by the Runner Build Settings, even though watch target build settings are correct (for example, Targeted Device Family is set to Apple Watch). What I've tried so far: Disabling auto generation of the Info.plist, and manually setting UIDeviceFamily to '4', but that doesn't help, unless I do it after creating the archive by editing the archive files and resending it to validation. I also tried a bunch of other post-build modifications to try and fix all the errors but new ones kept popping up. Cleaning Build Folder and DerivedData, restarting XCode, rebooting the computer... no effect, which is expected given that the building process doesn't return any errors Validating just the app without the apple watch (so from my main branch), still works as expected. Recreating a blank watchOS target and trying to validate just that, I get stuck in the same way. Project details: XCode Version 16.3 (16E140) Flutter 3.27.3 Targeting latest watchOS and iOS 16+ Do you have an idea what could be the problem here ? I'm sure it's just a missing or invalid property in some configuration file, but I can't figure it out and there are no resources online documenting the issue, and no "tutorials" on how to properly set up a watch target from Apple. Thank you for your time. A.H.

For the past 5 days, myself and all TestFlight users with my app have been unable to access TestFlight. When opening the TestFlight app, it immediately displays "Couldn't Load Apps" "TestFlight is currently unavailable. Try Again." If you press "Try Again" over and over for several minutes it will sometimes let you access the main install page on iPhone devices, but generally it just stays locked on "Couldn't Load Apps". On iPad, it is not possible to get to the install page. This is happening across all devices (iPad and iPhone) and OS (iOS 15 to iOS 26). User who are TestFlight testers on multiple apps are unable to access their other apps because of this issue. I've uploaded a new build and version and the issue persists. I filed a feedback assistant report: FB20901217. Has anyone else experienced a similar issue?

I have an application that is in TestFlight (Version 2.1 with different builds) as you can see there is a lot of crash . These crashes are not available on this web platform. I can only see the 2.0 crashes. Even in Xcode/Organizer I do not have the same number of crashes. I waited a few days before checking if these files arrived, but no, nothing, or just 3 useful crash reports, but not in the same number as this screenshot. There is an inconsistency between this table and my xcode. And I cannot select version 2.1 in the other part of the site, the one where you can download the crashes. The App number is 6741442093.

苹果人员，您好： 我用macOS 26系统遇到一个appstore的问题。当我从appstore下载我自己的macos app的时候，当时一直在转圈，无法下载成功，后来我下班后就关机了。第二天再上班后，再次下载就下载不了了。详见附件mp4操作视频。（别的macos机器可正常下载） 我自己尝试的方式： 1. 更换网络，—没有解决问题 2. 更换账号，—没有解决问题 3. 杀死appstoreagent进程 （killall -9 appstoreagent storedownloadd storeagent），—没有解决问题 4. 清除appstore缓存，—没有解决问题 5. 恢复模式下 reinstall macos 26，—没有解决问题 console 日志（详见附件截图和txt文件）： Error Domain=IXErrorDomain Code=5 "A coordinated app install already exists for [com.zhanghai.MacGuardApp/Invalid/[system-defined]] with intent IXCoordinatorIntentUpdating (creator App Store) but request by appstoreagent (pid 1469) was for intent IXCoordinatorIntentInitiating" UserInfo={NSLocalizedFailureReason=Coordinated install exists with different intent. 实在没有办法了，才求助apple团队，因为我需要测试我的app（testflight 也是无法下载的，提示无法安装。），但是我又无法下载下来，没法测试我就没法上架。

Can anyone please confirm that Apple-hosted Background Assets still will NOT work unless the app is: Installed from TestFlight, or Installed from the App Store Is it true Xcode-installed builds—Debug or Release—do not receive the App Store’s Background Asset metadata and cannot access the background asset packs? I am getting the error when running the app in Xcode: The asset pack with the ID “VALIDPACKNAME” couldn’t be looked up: No asset pack with the ID “VALIDPACKNAME” was found.

Since I donwloaded Testflight, an error message appears indicating that "Testflight is temporarily unavailable. Try again." And some of my colleagues encounter the same problem. Do you know what the issue can be?

Since 1st of September archives uploaded via Xcode 26 beta 7 or builds distributed via CD (fastlane deliver) don't appear in App Store Connect. No errors reported during/after upload process, no e-mails with errors received. Xcode reports successful upload (with a few warnings regarding dSYM) I'm not getting any e-mails with ITMS errors Builds don't appear at in App Store Connect in TestFlight section (not even in "Processing" or "Failed" states). For me it seems like App Store Connect outage but all statuses in https://www.apple.com/support/systemstatus/ are green.

Hello everyone. We have an app that has been on the App Store for several years, originally distributed for iOS and iPadOS only. Recently, we enabled Mac (Designed for iPad) and started distributing macOS-compatible builds. Current situation: The app is available and downloadable from the macOS App Store and runs correctly on Apple Silicon Macs. The same app/build appears in TestFlight on macOS, but cannot be installed. TestFlight shows the message: “This app can only be tested on an iOS device.” This suggests the app itself is Mac-compatible, but TestFlight is treating the build as iOS-only. Environment and checks performed: Mac is Apple Silicon. App Store Connect app-level availability for Mac (Designed for iPad) is enabled. The app is not Mac Catalyst; it is a UIKit iOS/iPadOS app. Distribution is done via GitLab CI. CI uploads use an App Store provisioning profile (Apple Distribution), not development or ad-hoc. iPhone and iPad TestFlight installs work as expected. Info.plist verification: UIRequiredDeviceCapabilities was originally present (armv7) and has since been: removed entirely, build number incremented, new builds uploaded to TestFlight. No other hardware capability requirements are declared. LSRequiresIPhoneOS = true remains unchanged. No other plist keys that should exclude macOS are present. CI / build considerations: The same uploaded build is accepted by App Store Connect and distributed successfully on the macOS App Store. This tells us the binary itself is valid for macOS, but TestFlight applies additional or different eligibility checks. At the moment we think that TestFlight eligibility may depend on build metadata, scheme/configuration flags, or internal App Store Connect state that differs from App Store distribution. Questions: Are there known cases where a build is valid for macOS App Store distribution but not eligible for macOS TestFlight installation? Does anyone know if TestFlight applies stricter or different platform gating than the App Store for “Mac (Designed for iPad)” apps? Are there specific build settings (e.g. SUPPORTS_MAC_DESIGNED_FOR_IPAD, TARGETED_DEVICE_FAMILY, scheme/config mismatches) that can affect TestFlight macOS eligibility independently of App Store eligibility? Is there an authoritative way in App Store Connect to inspect why a specific TestFlight build is marked as “iOS-only” for macOS? Any insight into TestFlight-specific eligibility rules for “Mac (Designed for iPad)” would be appreciated, especially given that App Store distribution for macOS is already working. I hope we're missing something very basic, and not that the app can't be tested as is for the mac, because it's useful to have our QA team test it on the mac.

I'm encountering an issue when trying to submit a new build of my iOS app to the App Store. The app launches from TestFlight without any problems, but when attempting to submit it for App Review, I get the following error: "This build is using a beta version of Xcode and can’t be submitted." However, I'm not using a beta version of Xcode. I've tested this with both the public releases of Xcode 16.3 and 16.2. The build logs show no issues with the SDK or Platform versions, but in App Store Connect, the metadata is displaying the following: Build SDK: $(SDK_PRODUCT_BUILD_VERSION) Build Platform: $(PLATFORM_PRODUCT_BUILD_VERSION) Have anyone else experienced this? Any insights on resolving it? Thanks in advance.

I've created a new app on App Store Connect. Setup everything like all the forms, the build, users, internal testing group, and then sent the invitation emails for testing. Now users can see the app in the TestFlight but when they try to install it, they get the error below. Could not install [APP]. The requested app is not available or doesn't exist. I've sent an email to Apple support couple of days ago but still no response. Saw some comments on the internet that you need to send your app for review and once it's approved you can use TestFlight. So I sent the app for review with a long description about how I'm not able to use TestFlight but still on wait. Tried to create a public TestFlight link but I get this error: "Beta contract is missing for the app." but there's actually no contract anywhere. What do I do? This is completely unacceptable. Why is the TestFlight not working? Why are the error messages not helpful?