From some point, all new TestFlight submissions cannot be downloaded from any device. The progress bar gets stuck at 75% for several seconds, then install button appears again. The app icon appears on desktop, but when trying to launch, an error alert appears "App cannot be installed now, please try again later". I've tried uploading from multiple Macs with the same result.

Hi, I am trying to test my first ever build but i get this error on testflight. I tried rebooting my iphone 16 plus, rebuilding the app and upgrading the app version. I tried reinstalling the testflight as well but nothing worked so far. I am really stuck

My game has been successfully distributed multiple times via TestFlight for testing. However, I recently encountered an issue: after removing gamekit from the UIRequiredDeviceCapabilities configuration in Info.plist and republishing to TestFlight, the download prompt shows "Incompatible on this iPhone". PS: My application does not use any GameCenter features at all, and GameKit.framework is not included in the Xcode project.

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 use Apple Business Manager to install apps on my office iPads and to track them. I am a beta tester for a company that pushes new versions of their software through TestFlight. These iPads are logged into managed apple accounts [apple IDs] under my Apple Business Manager account. When I attempt to open TestFlight, I receive a message "TestFlight is currently unavailable, try again later." If I logout and sign in an iPad under a consumer Apple Account, TestFlight works properly. I however, want to use these iPads under my apple business account.

I have a problem with my client's account. I can't let internal testers download a test build from TestFlight. When they want to install there's this 2 alert popping up: "The requested app is not available or doesn't exist" This problem happens on both the app that is not published yet, and the app that is in Appstore already. I checked and there's no any pending agreement. Another problem is when I try to submit the build for External tester review it shows the error message (that doesn't really helping at all) like this:

I'm currently experiencing the same problem that many have had with error 422 "Beta contract is missing." I read that I should contact Apple support, but when I try to access the support page and log in with my credentials, the page doesn't load and I can't generate a ticket to resolve this problem. I get the message "There was an error processing your request. Please try again later." And when I inspect with Safari it shows me this information: "errors" : [ { "id" : "9be0314c-3bd5-4143-a625-602322d7156e", "status" : "422", "code" : "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title" : "Beta contract is missing for the app.", "detail" : "Beta Contract is missing." } ] This is when I want to share the most recent build of my app with external groups through Testflight, but additionally, when my internal testers try to access it through Testflight app, it shows the error "The requested app is not available or doesn't exist." Could someone tell me what process I should follow or where I can correctly generate the ticket for my error? Since the Apple support page does not load. Thanks!

I suddenly started to receive the following email with the error in it stating that my uploaded app is not available to be used in TestFlight: ITMS-90886: 'Cannot be used with TestFlight because the signature for the bundle at “MyApp.app/Contents/PlugIns/MyAppWidgetExtension.appex” is missing an application identifier but has an application identifier in the provisioning profile for the bundle. Bundles with application identifiers in the provisioning profile are expected to have the same identifier signed into the bundle in order to be eligible for TestFlight.' It was all working fine and now I am not sure even where to start looking. Signing, provisioning and everything else is managed automatically.

无法兑换TestFlight,如图同一个apple账号，无法兑换，啥原因，有什么解决方法？

Facing issue in iphone 13 and iphone 16. "Testflight is currently unavailbale, try again"

2025年10月20日11点左右，testflight不可用，是什么原因？什么时候恢复有人知道吗？

I work for a company in Germany and Testflight works on none of our managed devices. On all of them we get "TestFlight is currently unavailable, try again later.". On personal devices TestFlight works as normal and on https://developer.apple.com/system-status/ we saw nothing for Testflight. Is there a way to fix this? What can we do to get Testflight running?

I’m seeing an issue with subscriptions in TestFlight builds on iOS 26. Running from Xcode works as expected, and the App Store build looks fine. But when I install the same build via TestFlight, transaction.subscriptionStatus is nil. The identical binary behaves correctly on an iOS 18 device. Is this expected behavior on iOS 26 TestFlight, or am I missing something? Thanks!

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.

Has this happened to anyone else? I am on rejection 3 now (first was my fault second would be resolved if reviewer actually used the app...easy fix) But this third time I was rejected for "items related to beta testing". My app has crashalytics installed and on first install it explains what data is sent, why and asks for user permission. But in beta I have a different view under isTestFlight() that says thank you for beta testing and doesn't give a choice (pretty standard). First 2 rejections never mentioned this screen. Meaning they never saw it. 3rd rejected for this screen...so I'm guessing the reviewer was somehow in a test flight environment. I followed best practices and got rejected. So I commented that out and now in test flight they get the production view. But if it wasn't the reviewer then the flag is worthless. Has anyone else had this problem?

After creating a new weekly subscription option, I get inconsistent results for subscriptionPeriod. In local testing with a synced or a un-synced StoreKit file I am getting unit == .week (as expected) whereas in TestFlight I am getting unit == .day. This makes unit.localizedDescriptionsomewhat unusable in the paywall. Am I missing something? Or is this bug or a limitation of StoreKit and/or TestFlight and/or newly created subscription options? Affected code (in a custom SubscriptionStoreControlStyle): private func priceDisplay(for pickerOption: Configuration.PickerOption) -> String { var result = "" if pickerOption.introductoryOffer != nil { result += NSLocalizedString("then", comment: "") + " " } result += pickerOption.displayPrice if let unit = pickerOption.subscriptionPeriod?.unit { result += " / " + unit.localizedDescription } return result } private func percentageSaved(for pickerOption: Configuration.PickerOption, allOptions: [Product]) -> Int? { guard let subscriptionPeriod = pickerOption.subscriptionPeriod, subscriptionPeriod != .weekly else { return nil } let weeklyOption = allOptions.first { otherOption in otherOption.subscription?.subscriptionPeriod == .weekly } guard let weeklyOption, weeklyOption.price > 0 else { return nil } let percentageSaved = 100 - (pickerOption.price / (weeklyOption.price * 52)) * 100 return Int((percentageSaved as NSNumber).doubleValue) }

I’m looking for iOS and Apple Watch users to help beta test ChoreFit, a fitness app that transforms everyday chores into measurable workouts using NEAT (Non-Exercise Activity Thermogenesis) science. What it does: • Tracks chores like vacuuming, mopping, and laundry as real workouts • Syncs with Apple Health for steps, heart rate, and calories • Lets you start or pause chores right from your Apple Watch • Adjusts effort based on body weight and optional weighted vests What I need from testers: • Install via TestFlight (link provided once approved) • Use the app during normal household tasks • Share feedback on usability, Apple Watch sync, and calorie accuracy If you’re interested in movement tracking, fitness analytics, or wearable integration, I’d love your help validating and refining this app before public release.

Hello, my builds keep failing in Xcode Cloud at the creation of the archive for tesflight. I am receiving an email mentioning "ITMS-90035: Invalid Signature" TMS-90035: Invalid Signature - Code failed to satisfy specified code requirement(s). The file at path “BASELog.app/BASELog” is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose “Clean All” in Xcode, delete the “build” directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/support/code-signing. The thing is the archives which are not intended for testflight not App Store connect are not failing. I think I have the required distribution certificates (initially they were created by API for Xcode Icloud, I add 3, revoked them and recreated one manually and the other from Xcode directly) : even though certificats seems ok, in Xcode I see a dev certificate in the managed release and if I try to force a distribution certificate in the build I then get the following warning It looks like my managed profile is not behaving properly, like not embedding a distribution certificate. I looked on the web for the signing issues, and I have found in other threads an issue with assets having special charsets. I checked on my side, the only thing I see is my app icon is named "icon_v1.png" I assume it shouldn't be an issue. I dont see any special char anywhere else in the sources name. Anyone has any idea on what is causing those build fails on the archive?

My archived xcode builds show that they have been successfully uploaded to testflight but once in the appstore they do not appear. Is there anyone else with the same problem?

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.