I am encountering an issue where I am unable to install the app from TestFlight. The installation fails or does not proceed as expected. Please advise on how this can be resolved. I have tried restarting the device and reinstalling TestFlight and reinvite the users but the problem persists.

I am experiencing a critical issue with my TestFlight builds and the App Store Connect submission process. I need urgent assistance as all my testing builds are currently expired. To fix the expiration, I increased the build number to Build 5 (Version 1.0.3) and uploaded it. I then tried to Submit for Review. The submission process failed, and I received an error message Has anyone experienced a widespread issue like this recently? What steps can I take to troubleshoot the submission error, and why would all my builds expire simultaneously, just days after a new upload? Thank you for your help!

In App Store Connect, a Build Uploads section recently appeared above versions in the iOS Builds page in the TestFlight tab. It’s always expanded, which pushes the Version sections halfway down the page—those are the ones I actually need to manage my builds (compliance, testing groups, etc.). Is there a way to either: Hide the Build Uploads section entirely, or Make it stay collapsed Right now, collapsing it doesn’t stick—it re-expands every time the page reloads. It wouldn’t be so bad if the list weren’t so long, but even expired builds still display, so I can't even expire a bunch of builds to minimize it.

I'm getting an error after clicking on a TestFlight Beta version invite from email. The error says The Apple Account you're currently signed in with, ****@outlook.com, doesn't match the one associated to this invitation. The invitation was sent to the email that I use to sign into my Apple account (it is my apple id) and I am signed into my iphone with that account. What can I do to get the invite to match up and go through with TestFlight?

I have a MacCatalyst app that is published on the Mac AppStore. All seems fine and dandy on the released version. However, when I try to test a build on my Intel based Macbook using the TestFlight app it says it's not compatible. I've looked at the build on AppStore connect and I can see that it's a universal build with x86_64, arm64 architectures. I'm at a loss as to why Test Flight reports it as incompatible yet the Mac App Store says it is compatible.

I’m developing an app that uses Family Controls to block other apps. I’ve already received approval from Apple for the entitlement, and everything works perfectly when I run the app from Xcode on a physical device. However, when I upload the same build to TestFlight, the app installs and runs, but the Family Controls functionality doesn’t work — it seems like the entitlement isn’t being applied in the TestFlight version. So I’d like to ask: 👉 Do Family Controls entitlements work automatically on TestFlight builds, or is there any additional step required to enable them?

Hey guys, somehow I used my real ID(not sandbox test ID) to purchase a non-consumable item in the TestFlight package, no actual payment was made, but this payment record cannot be erased. Even though I know the transaction ID, I cannot initiate a refund like using refundRequestSheet(). Does anyone know how to deal with this, or there is no way to solve it?

Hello, I'm currently setting up an external TestFlight testing phase for my iOS app and need some clarification on the release process after App Review approval. For App Store releases, I know I can manually release the app at my preferred time. However, when submitting an external TestFlight build for review, there is an option to "Notify testers". If this is selected, the build seems to be automatically made available to testers immediately upon approval. My concern is: If I uncheck the "Notify testers" option, will the build still become available on TestFlight, allowing testers who proactively check the app to download the update, even though they don't receive a notification? Is there a way to completely control the exact release time (similar to the manual App Store release) for external testers? We need to manage the release timing to align with backend production deployment. We want to ensure the app update is released only after our backend is fully ready. Any insights into how to best manage this timing would be greatly appreciated! Thank you.

Hello! Ive been working on a package tracking app for iOS and was looking forward to pushing it to TestFlight for some testers to use. When I go to archive the package, I get a warning about the "...TrackerIntents.appex is an ExtensionKit extension and must be embedded in the parent app bundle's Extensions directory, but is embedded in the parent app bundle's Tracker.app/Extensions directory". The extension is for siri integration with shortcuts. I have done quite a lot of things to try and diagnose this but cant seem to get passed this warning. I know it's a warning but would rather it not exist. Ideally I would think its a matter of "moving" the items but in the navigation area, I dont see an extensions area. The main app target has it in the dependencies along with the EmbedExtensionKit Extensions in the Build Phases. Any ideas or configs I can try? I can provide more information if needed. This is on the latest Xcode version 26.0.1 for iOS 26. Thank you.

I've reached maximum number of testers for my app. That's why I've deleted all testers from TestFlight to clean testers list and invite new and old testers again by public link. But deleted testers are still count in "All testers", but in "Deleted testers" filter. And the error "You’ve added the maximum number of external testers for this app" still occurs. Is this how it's supposed to work or is this a bug?

When I create new build for TestFlight, it could not install from Test Flight, and show any error/warning/tip, from device's console, I got this error: -[IXSDataPromise cancelForReason:client:error:]: <IXSPlaceholder(0xc1acd7480) Name:App Placeholder: XXXXXXX(com.YYYYYY) Creator:App Store UUID:8AB2A59C-C367-42E1-990A-ACAFD8F9F4B9 Location:[system-defined]> : canceled by client 17 for reason Error Domain=IXUserPresentableErrorDomain Code=1 "This app could not be installed at this time." UserInfo={NSUnderlyingError=0xc1b1751a0 {Error Domain=MIInstallerErrorDomain Code=99 "WatchKit 2.0 app has disallowed Info.plist key: ISIconPlatform" UserInfo={LegacyErrorString=WatchKitAppIllegalInfoPlistKey, FunctionName=-[MIExecutableBundle hasOnlyAllowedWatchKitAppInfoPlistKeysForWatchKitVersion:error:], SourceFileLine=2715, NSLocalizedDescription=WatchKit 2.0 app has disallowed Info.plist key: ISIconPlatform}}, NSLocalizedDescription=This app could not be installed at this time., NSLocalizedRecoverySuggestion=WatchKit 2.0 app has disallowed Info.plist key: ISIconPlatform, NSLocalizedFailureReason=Could not install at this time.} After I remove watch app in this app, It could install successful, but this watch app still needed. I count not find anything about [IconPlatform] in my code, and could not find it in the info.plist files in the .ipa file. I only do some tiny code change for my app, and it could install in yesterday, but could not install for today. So how to resolve this issue? I need submit my new build for a urgent company events.

Hi, I have an application published in the Marketplace. I made certain updates to the app. I did my tests.No problem. I did my tests via Testflight. There is no problem I encountered. But my app update request was returned by app review. The answer i got from them ;  "Specifically, our login attempt displayed loading indefinitely; we were unable to access the app features and functionality." Here are the ways that I tried and the app worked successfully. Connect from America using VPN.No problem, it works. I connected from using IPV6.No problem, it works. I tried with simulator.No problem, it works. I tried real device.No problem , it works. I tried testflight.No problem, it works. I tired version 15.2 and earlier.No problem , it works. I have no idea why apple staff are getting this error. Has anyone encountered such a problem before? What solutions would you suggest? I'm waiting for your help.

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.