Trying to figure out why my public test group got rejected and what I need to do to rectify and move forward. Is anyone able to help with this?

I have a tester who switched phones a few months back. Crucially he no longer has access to the old phone. On his new phone when I send him a test flight invite to his apple account, 123@example, he receives it but it fails to work when he clicks the link. He is getting the following message. The Apple account (123@example) you're currently signed in with does not match the one (456@example) associated with this invitation. He has no idea what email 456 is. Since his old phone was a hand me down, I'm assuming it's someone else's email entirely. I'm trying to figure out how we clear this association out. I tried deleting his app store connect for my app and reinviting him all the way from the beginning. This did not work. As a stopgap I'm giving him a public link under an external testing group but I'd really like to not have to do that. Anyone have any ideas how we can fix this so I can shift him back to the Internal testing group?

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?

My iOS App testflight builds are stuck in Processing for hours. Usually takes 5 mins. Anyone else having this issue? Submitted a Feedback Assistant report.

Hello everyone, I’m reaching out from the music publishing side and would appreciate guidance from developers or anyone familiar with TestFlight governance. We’ve identified an app that has been distributed via TestFlight for an extended period (regular renewals, updates, and new TestFlight builds). The app’s core functionality involves publishing copyrighted musical works (sheet music), without authorization from the authors or rightsholders. We have attempted to contact the developer using the contact details available through the TestFlight listing and associated project information. To date, we have received no response, and the TestFlight distribution continues. From our perspective, the developer appears to rely on TestFlight to keep the app off the App Store, where standard copyright enforcement mechanisms would normally apply. My questions are: Does Apple consider long-term, continuously renewed TestFlight distribution to be a form of public distribution? Is there a mechanism within the Apple ecosystem to address repeated copyright infringement occurring specifically via TestFlight? From a developer-policy perspective, how does Apple Inc. typically handle cases where TestFlight is used to bypass compliance obligations rather than for genuine beta testing? I’m not looking for legal advice here — just insight into how Apple and the developer community view and handle this type of situation. Thanks in advance for any guidance or experience you can share.

i need a testflight invitation code, is it possible? i dont really know about the developer e-mail. could you send me a testflight code? here is my email: ******** [Personal Information Edited by Moderator]

Ever since I have upgraded to iOS 26 (at least, I THINK this was when it started) I have been seeing an email account on Testflight purchase flows that is NOT mine. I have never seen this email in my life, and have not used it during the 10+ years I have been a developer. I do not know how to make this use my Apple ID I am signed into on my device. However, locally signed builds from Xcode still work ok. But I need Testflight builds to work as well. How do I force this account to change?

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.

I'm having issues accepting an invite to access TestFlight. I may have tried multiple attempts due to my existing email address not being accepted, so I had to create a new email that's not linked to Apple yet and put it in the activation form. However, now I am getting an error, "Verification codes can't be sent to this phone number at this time. Please try again later." This has been an error since yesterday and the resend, verification via call, and text are all not working. I also tried a different phone number and same issue. Can someone help on this, please.

I've been experiencing complete TestFlight system failure for 6 days across ALL testing modes with 4 open support cases and zero technical resolution: Support Cases: • 102814191861 (submitted Jan 29) • 102814822980 (submitted Jan 30) • 102814123468 (phone call Feb 3) • 102818476151 (latest update Feb 3) ISSUE DETAILS: App: كيم تحصيلي (ChemTahsili) Bundle ID: com.chemTahsiliApp Build: 1.0.5 (34) SYMPTOMS: ✗ Internal Testing: Users receive "The requested app is not available or does not exist" ✗ External Testing: System shows "Validation Error - Check your entries and try again" ✓ Build Status: Shows "Valid" in App Store Connect ✓ App Status: "Waiting for Review" ✓ All Agreements: Active (Free Apps, Paid Apps, Banking, Tax Forms) ✓ Account Status: Good standing EVIDENCE THIS IS APPLE'S INFRASTRUCTURE ISSUE: Same build fails in BOTH Internal AND External TestFlight Build is marked "Valid" and approved for testing All developer configurations verified correct Issue persists across 6 days and multiple builds No configuration changes can affect External Testing validation SUPPORT RESPONSES SO FAR: "Wait 48 hours and rebuild" (ignoring that app is under App Store review - rebuilding would cancel review) No escalation to TestFlight engineering team No investigation of backend infrastructure Generic troubleshooting that doesn't apply to system-wide TestFlight failure IMPACT: Educational app for chemistry students preparing for critical exams. Hundreds of students affected. Launch delayed 6 days and counting. QUESTION: Has anyone else experienced total TestFlight system failure like this where BOTH Internal and External testing fail for a Valid build? How was it resolved? This is clearly Apple's TestFlight backend problem, not developer misconfiguration. I need engineering-level investigation but support is only providing generic advice. Any help or similar experiences appreciated.

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, 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.

Hi, We're seeing a recurring issue in Sandbox only with in-app subscriptions (StoreKit 2). Hoping someone has run into this and has a workaround or explanation. What happens A subscription purchase (e.g. Yearly) is made in Sandbox. For whatever reason, the transaction stays pending in the queue. On the next app launch (or when a different user logs into the app on the same device), the store returns this same pending transaction via getAvailablePurchases() / the purchase queue. Our app sends that transaction to our backend for validation and updates the currently logged-in user in our database. So the same transaction can end up being applied to another user if they log in on the same device after the original purchaser. We call finishTransaction after successful validation, but the pending transaction still reappears in subsequent sessions or for another user on the same device. So in short: one Sandbox purchase stays "pending" and is replayed every time we start the app or switch accounts, and we can't rely on it being tied to a single user. Environment Sandbox only (we haven't shipped to production yet). StoreKit 2 / modern App Store Server API (transaction ID validation). We run getAvailablePurchases() on connect and process pending purchases once per session; we then call finishTransaction only after our server has validated and updated the user. Same device, multiple app accounts (different app users, same Sandbox Apple ID or same device). What we're trying to understand Is it expected in Sandbox that one transaction can be delivered again and again (on each launch or for each user on the device) until something clears it? Is there a recommended way to clear or ignore a specific pending transaction in Sandbox when we've already validated it for a given user (e.g. idempotency key, or a way to "consume" it so it doesn't replay)? Has anyone else hit this "same pending transaction replaying for different users / on every launch" in Sandbox and found a reliable approach (e.g. server-side idempotency, or a StoreKit/Sandbox step we're missing)? We've added server-side protection (one transaction → one user) so the same purchase isn't credited to multiple accounts, but we'd like to understand if there's a proper way to handle or clear this pending state in Sandbox. Thanks in advance.

I have an app clip installed via TestFlight. My AASA file is configured correctly (per 'Domain Status' in TestFlight). I want to be able to run the app clip flow (app clip card showing and app clip card launched) by invoking UIApplication.shared.open(url) from a different app, or by pressing the URL from notes app. This doesn't seem to work. The only thing I am able to do is run the flow when scanning a proper QR code after configuring Local Experience with the matching parameters. But as stated above, the flow will not work when invoking the URL from a different app. Is the proper way to fix this is to define an HTML page for that URL path that contain the element with app-clip-bundle-id attribute that will match the Local Experience configuration? Is there another way to make this flow work with TestFlight releases? what are my options?

Hello, I’d like to share an issue we recently experienced with TestFlight and ask whether this behavior is expected. Environment App version string: 1.0.0 Multiple builds uploaded via CI/CD Both external TestFlight testing and internal CI builds exist Testers had automatic updates enabled in TestFlight What happened We uploaded build 1.0.0 (2601161653) and assigned it to an external TestFlight group. Testers installed this build and were testing normally. Later, we uploaded a newer build 1.0.0 (5) and reassigned the same external testers to this build. Testers successfully updated to 1.0.0 (5) and continued testing. After some time (without any manual action from testers), testers received a system notification saying that: “The App has been updated. Version 1.0.0 (2601161653) was automatically downloaded and installed.” When opening TestFlight, the app showed 1.0.0 (5) again as available for update, meaning the device had already been rolled back to 1.0.0 (2601161653). Additional context There are many archived builds in App Store Connect due to CI/CD testing. Some CI builds share the same version string but differ only in build number. External test groups were only explicitly assigned to build 1.0.0 (5) at the time of the rollback. Build 2601161653 did not have any external test group assigned at that moment. No App Store release or metadata changes occurred during this time. Questions If a tester’s currently installed build becomes temporarily unavailable (e.g. due to eligibility, internal status changes, or TestFlight processing), does TestFlight automatically fall back to a previously approved build? Is this automatic rollback behavior an intended part of TestFlight’s build availability logic, especially when multiple builds with the same version string exist? Can frequent CI/CD uploads (without consistent external group assignment) influence which build TestFlight considers “eligible” or “latest” for testers? Summary From our observation, it appears that when the currently tested build temporarily lost eligibility, TestFlight automatically installed a previous build that was still considered available, even though a newer build existed. We’d appreciate any clarification on whether this behavior is expected or if there are best practices to avoid this situation when using CI/CD with TestFlight. Thank you.

Hello , I recently uploaded an app and would like testflight , ı sent 2 friends of mine invitation however none of them got it ( prior that added them as user) one of them use icloud.com the other uses mail.ru. Does anyone face such problem and how to solve it? Its been almost 5 hours, I retry the process by deleting them then add later on again.

Hi, I’m experiencing a TestFlight issue affecting multiple apps in my account. Issue summary: • Several TestFlight builds across all of my apps expired at the same time. • After uploading new replacement builds, neither I nor my testers are able to install them. • Installation fails with the message: “Could not install {App Name}. The requested app is not available or doesn’t exist.” • The build shows as processed and available in App Store Connect. • Testers are already invited and active. • No redeem code is required. I am seeing the same issue on my own device as well. What I’ve tried: • Uploading new builds (incremented version + build number). • Confirmed builds are visible and available in App Store Connect. • Removing and re-adding testers. • Logging out of the app. • Deleting the app from the device. • Restarting the device. • Reinstalling directly from TestFlight. • Restarting TestFlight. Despite this, installation consistently fails with the “requested app is not available or doesn’t exist” error. Expected behavior: • New TestFlight builds should be installable once processed and available. • Testers (and the developer) should be able to install directly from TestFlight. • Expired builds should not block installation of newly uploaded builds. Additional context: • This started immediately after multiple TestFlight builds expired across my apps. • All affected apps were previously installing and testing without issue. • Apple Developer Support has been contacted, but I wanted to check whether others are seeing the same behavior or if there is a known workaround. Has anyone else encountered TestFlight builds becoming unavailable across multiple apps at once, or an install failure after replacing expired builds

Hi there, When I build my app in Xcode using a synched AppstoreConnect Storekit file, when using subscriptions, I am sent to the correct (for me) UK store to purchase a subscription. However when using the same build as a TestFlight App I am presented with the US store.. If I try to purchase a $ subscription I get the error: Account not in this store Your account is not valid for use in the U.S. store. You must switch to the U.K. store before purchasing If I try to use the presented Change App Store button - I get Unable to Complete request Error My AppStore on my Mac is set to the UK store.. How can I get the TestFlight version to present the correct store locale? Many thanks!

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 trying to test a crossgrade on a subscription plan that has the same duration and price. When running tests with renewal intervals shorter than one hour, and managing or modifying the subscription, I see a payment confirmation message that says “You’ll pay X euros today.” This message is confusing because it sounds like an immediate charge, whereas my understanding is that the payment actually occurs at the next renewal, which in the test environment happens “today” due to the accelerated renewal frequency (1 hour or less). To make sure this works as expected, according to the official documentation, when testing in TestFlight the renewal frequency is 1 day. Therefore, when managing and modifying the subscription to perform the crossgrade, I would expect the UI to indicate that the payment will occur tomorrow. However, when I manage the subscription from the device’s Developer section, it indicates that the subscription will renew today, and as a result, during the crossgrade flow it again shows that I will pay X euros today. Is there any way to properly test this scenario? Or should I assume that in production the crossgrade behavior will match the documented explanation?