Dear TestFlight Team! I am observing an increasing misuse of TestFlight public and private invites to distribute scam, spam, and potentially malicious builds: I had reported this already in December last year via Feedback assistant, but since the malicious behavior has not stopped, I hope that you can forward my bug reports to the right team: FB21379977, FB21845307 In multiple cases, these builds impersonate well-known apps (e.g. ChatGPT, OpenAI, Meta) by changing the app name and icon after an initial TestFlight approval, misleading users into installing software from unrelated developer accounts. I believe this represents a systemic weakness in the TestFlight review and update flow, enabling targeted phishing or malware distribution outside the App Store review process. My bug reports have attached: TestFlight invitation emails (.eml) Screenshots from TestFlight documenting impersonation behavior ⸻ Steps to reproduce Create a new Apple Developer account. Upload an initial, benign app (e.g. a calculator) as version 1.0.0 and obtain TestFlight approval. Upload a second build: without changing the version number increase build number Change the app name to a well-known product (e.g. “ChatGPT”) Change the app icon to match the impersonated product Invite targeted email addresses to the TestFlight group. Recipients receive an official TestFlight invite and are prompted to install the impersonating app. ⸻ Expected results TestFlight builds that significantly change app identity (name, icon, branding) should: Require additional review, or Be blocked from distribution without re-approval. Developer accounts should not be able to impersonate well-known companies (e.g. “OpenAI Platforms LLC”) without verification. Users should be protected from installing TestFlight builds that materially differ from what was originally reviewed. ⸻ Actual results App name and icon can be changed between TestFlight builds without triggering additional review. TestFlight invites can convincingly impersonate trusted brands. Targeted users may reasonably believe they are installing a legitimate beta. This creates a credible vector for: Phishing (credentials, payment details) Data exfiltration Social engineering attacks I did not install the builds to avoid personal risk, but the attached artifacts should allow Apple’s internal teams to reproduce and analyze the behavior safely. Some more examples:

Hello, I'm experiencing an issue with accepting testflight invitations. The workflow: Developer invites me through Connect I am receiving the email and clicking Accept Invitation The link opens testflight, however I am immediately prompted with a "Couldn't Load App: This invitation has been revoked or is invalid. Request a new invitation from the developer." I hope this gets resolved quickly, I need to join the app testing. Thanks

Hi all, I have a build in "Waiting for Beta App Review" that has been stuck for more than three days, well beyond the typical 24-48 hour window. Context: • Internal-use app distributed via TestFlight only (no App Store release). • Uploaded approximately April 18, 2026. • No ITMS warnings, no rejection notice, no request for additional information. • A newer build was uploaded today (April 21, 2026). It processed correctly and is also now awaiting Beta App Review behind the older one. • I noticed another forum thread referencing FB22543589 / Case ID 102872835864, reporting TestFlight builds being flagged as Expired/unavailable overnight between April 20 and April 21, 2026. I would like to rule out whether my submission was affected by that incident. Questions: Has anyone else experienced Beta App Review delays during the week of April 20, 2026? Beyond filing a Feedback Assistant report, is there a recommended escalation path for stuck beta reviews? If my pending build was affected by the April 20-21 TestFlight incident, does re-uploading resolve it, or does the new build simply re-enter the same queue with the same delay? I have also submitted a support request via the Contact Us form, but wanted to check with the community in case others are seeing the same pattern this week. Thanks,

Hello Community I have a current app that is live in production that was last deployed under Account X. I had to change my account name to Account Y so I created a new Account and asked Apple to transfer my app. They have done and I can see my App on the new Account as well as transferring my app id (bundleID) and provisioning profiles. I am trying to push a new version of the app that was transffered but I keep on Running into this error. My Account X has expired but the new Account (Account Y) is valid and has no agreement exceptions on it. Couple of questions The Transfer Status is Active (not complete) is this correct? Is it possible there is still ties to the bundle id to the old Account X that I can no longer see I have a paid agreement present and sitting in New Status under the business page. I do not have any paid app functions on my app.

I have an app that has suddenly gotten a non-public API error after uploading the archive to TestFlight. The error is posted in full below, and has never occurred before. I'm not using the _UIDeviceOrientationDidChangeNotification symbol but I do have two extensions that use UIDevice.orientationDidChangeNotification. However those extensions are not included in the target for the two watch extensions where the error occurs. Has anyone seen this problem before or have some advice? 90338: Non-public API usage. The app references non-public symbols in Watch/watchkitappBeta.app/PlugIns/watchkitappExtensionBeta.appex/watchkitappExtensionBeta: _UIDeviceOrientationDidChangeNotification,The app references non-public symbols in Watch/watchkitappBeta.app/PlugIns/watchkitappExtensionBeta.appex/PlugIns/watchkitappWidgetExtensionBeta.appex/watchkitappWidgetExtensionBeta: _UIDeviceOrientationDidChangeNotification. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/

Hi everyone, I'm currently experiencing an issue when trying to submit my app/build via App Store Connect. Details: App name: Daily Habit Tracker 2026 Bundle ID: com.DailyHabitTrackerPro.2026 Case ID: 102871415765 Issue: Whenever I try to submit the build (TestFlight / App Review), I get the following error: "There was an error processing your request. Please try again later." This issue has persisted for several days. What I've tried: Retried submission multiple times Waited and tried again later Checked app metadata and settings Contacted Apple Developer Support on April 17, 2026 (no response yet) Question: Has anyone encountered this issue recently? Is this a known backend issue on Apple’s side, or is there anything else I should check? Thanks in advance.

I'm experiencing a persistent issue where my app uploads successfully to TestFlight and appears in App Store Connect, but internal testers (including myself) receive the following error when attempting to install: "Could not install xxxxxxxxx. The requested app is not available or doesn't exist." What works: The build archives and exports successfully via Xcode (local build, Release configuration) The IPA uploads to App Store Connect without errors via eas submit The build appears in TestFlight and passes processing I can add the build to my Internal Testing group Testers receive the TestFlight notification and can see the app What fails: When any tester taps "Install" or "Update," the download begins briefly, then fails with the "not available or doesn't exist" error This affects all internal testers on the account, not just one device Troubleshooting already completed: Verified code signing is correct: Release configuration uses CODE_SIGN_STYLE = Manual, CODE_SIGN_IDENTITY = "iPhone Distribution", with a valid App Store distribution provisioning profile (UUID: 39bc4c63-bc64-403a-a2a6-6737b3d33115) 2. Distribution certificate is valid: Serial 4838CD7571DE5361B98A5FB2F769F74D, not expired (expires 2027-04-16) 3. Regenerated provisioning profile via EAS credentials, removed stale profiles, and rebuilt — same result 4. Incremented build numbers correctly across multiple submissions (3004 → 3005 → 3006) 5. Previously resolved a signing misconfiguration (build 3005 was incorrectly signed with "Apple Development" instead of "iPhone Distribution" due to expo prebuild reverting settings) — this was corrected for build 3006, but the install error persists 6. Confirmed the build is not stuck in processing — it shows as ready for testing in App Store Connect 7. Tested on multiple devices running current iOS versions 8. Cleared TestFlight app cache and reinstalled TestFlight on test devices Why I believe this is a server-side issue: Multiple developers in the Apple Developer Forums have reported the identical symptom — valid builds that upload and process correctly but fail to install with this exact error message. In those cases, Apple Support resolved the issue on their end within 48 hours with no action required from the developer. The signing, provisioning, and build configuration were not the cause. This one is very specific to what I am dealing with https://developer.apple.com/forums/thread/778597 One developer stated you fixed it on your side, without any real reasoning which also leads me to believe this is not something I can fix on my end https://developer.apple.com/forums/thread/778597?answerId=884241022#884241022 I've exhausted all client-side troubleshooting and believe this may require intervention on Apple's side. Has anyone been able to fix this on their end and not only when App Development called? I went through tons of the feedback and tried it all and it doesn't seem to be fixed. It's been a month or so like this. I can't get any info on who to call. I sent in a report to feedback assistant and through app developer support

Hello, I created an app using the latest version of Xcode (16.2), and I'm having a problem testing this app on my iPhones. I created this app just like all the others I've made for my clients, including one on (03/24/25), but when I went to upload another App to App Store Connect on (03/26/25) I couldn't test it on my phone. Points to consider: The app runs perfectly on the Emulator. All my terms and agreements with Apple are up to date. I tried to download the apps through Testflight on 2 different devices, iPhone 7 Plus (iOS 15.8.1) and iPhone 15 Pro Max (iOS 18.3.2), and I was unsuccessful in neither attempt. I can send my app to the internal testers, but when I click download, the following message appears: Could not install [APP NAME]. The requested App is not available or doesn't exist. I imagine this problem is with Apple itself, I have already contacted support, but I need to resolve this urgently for my customers. Has anyone experienced this and resolved it?

I am unable to receive an invite email on my apple account in order to accept and get access to testflight for testing apps

App Store Connect: TestFlight show "Complete" for Mac application. What is the next step ? Do I need to invite (or create group for) testers ?

Hi everyone, I’m currently facing an issue in App Store Connect when submitting a build to TestFlight. When I try to complete the “What to Test” section and submit, I get the following error: “There was an error processing your request. Please try again later.” Case details: Case ID: 102871190604 Submitted: April 17, 2026 (GMT+7) Status: No response after 3–4 days This issue is blocking me from submitting the build. What I’ve tried: Retried multiple times Switched browsers (Chrome, Safari) Used Incognito mode Logged out and back in Simplified the “What to Test” text Checked build is processed and not expired I have already contacted Apple Developer Support but haven’t received any response yet. Questions: Is this a known App Store Connect issue? Should I wait for support, or upload a new build? If any Apple staff could help check this case, I would really appreciate it. Thank you.

Hi everyone, I’m getting this error in App Store Connect when submitting a build in TestFlight: “There was an error processing your request. Please try again later.” Case information: Case ID: 102871415765 Contacted Apple Developer Support: April 17, 2026 (GMT+7) It has been 3–4 days with no response so far Where it happens: App Store Connect During the “What to Test” step The build is already processed and available What I tried: Retried several times Switched browsers Used Incognito mode Logged out and back in Simplified the “What to Test” text Checked that the build is not expired This issue has been blocking submission for several days now. Has anyone experienced this recently? Is there any workaround, or should I upload a new build? Thank you.

This is my first in-App purchase App. I have other paid Apps and my business status are all active. I tested the in-app purchases on my devices using a StoreKit file and Xcode. I removed the StoreKit file from run configuration Scheme, I added in-app purchases to Signing & Capabilities then archived, validated and uploaded build to AppStore connect. I added two testers - a sandbox account (gmail subaddressed) and another gmail account. When I try to load the App using TestFlight I immediately get "couldn't load App". This is an App that previously had no in-app purchases. I added in-app after version 1 (tested ok in TestFlight). Now trying to test version 3 in TestFlight. Any insight would be appreciated.

We have enabled the Host Card Emulation (HCE) capability for our app and successfully implemented and tested the functionality during development. When running the app directly from Xcode, HCE-related flows work as expected. However, we are observing different behavior in the distributed build. In particular, the following check consistently evaluates to false: guard await CardSession.isEligible else { return } After distributing the app via TestFlight, HCE functionality is not available for external testers. The CardSession.isEligible property always returns false, even when tested on supported devices and in supported regions. We are using the same bundle identifier for both development and distribution builds, and the provisioning profiles include the required capability. Could you please clarify the following: Are there any additional entitlements, approvals, or configuration steps required for HCE to function in TestFlight or distribution builds? Are there known region, device, or account-related restrictions that could cause CardSession.isEligible to return false outside the development environment? Is there any difference in behavior between development-signed and distribution-signed builds for this capability?

Hi everyone, I’m an indie iOS developer working on Kleio, an AI voice keyboard extension that lets you dictate text quickly anywhere you can type. I’m looking for a small group of beta testers who are willing to try it through TestFlight and share feedback about stability, UX, and accessibility. What Kleio does Adds a custom keyboard so you can press the mic button and dictate instead of typing. Uses AI to turn rough speech into cleaned‑up, properly punctuated text. Lets you pick different writing styles (e.g. more formal vs more casual) for how your dictation should read. Supports a personal dictionary for custom words and names. Keeps transcript history on‑device by default, with optional cloud sync and improvement sharing. Includes a “Privacy Mode” toggle when you don’t want anything uploaded. What I’d love feedback on Onboarding flow for first‑time setup and keyboard enabling. The dictation experience inside real apps (Messages, Notes, Mail, social apps, etc.). Latency, accuracy, and how well the edited text matches what you meant to say. Keyboard layout, button placement, and any confusing interactions. Accessibility and inclusion: How well it works with VoiceOver / Switch Control. Any issues with contrast, touch targets, or labels. Any specific needs for users who rely on voice input more than typing. TestFlight link You can join the beta here: https://testflight.apple.com/join/jGY1fZ7S External group: “Twitter” (currently around 9 testers). No login is required for basic dictation; some settings sync features use account sign‑in. How to send feedback Through TestFlight’s built‑in feedback / screenshots. If you run into crashes, unexpected latency, or accessibility problems, details like device model, iOS version, and what app you were dictating into are extremely helpful. Thanks in advance to anyone who’s willing to try Kleio and help me make the keyboard more reliable and accessible.

When downloading an app, I often cannot download it. What is the reason?

Update: Turns out it works for others, apparently, and I also found one of my Macs where it does work, too. So it must be something pertinent to my systems. Oddly, though, the same ones where it now fails used to work because I had TestFlight enabled there before. I have TestFlight set up on App Store Connect, and I have already about 50 testers subscribed. Today, I found that the Public Link does not work any more: Once TestFlight.app is installed, and one clicks the link to add my app to TestFlight, it always shows the error ""Unable to Open Link" in TestFlight.app: I've tried this on several Macs (Ventura and Sonoma), and with different Accounts, both where the app was already added or not. Is something generally broken, i.e. do others see the same issue with their TestFlight links, or is it just me? How do you suggest I get this resolved? Here's an example link I set up for this purpose - it only allows a handful of subscribers, so please do not actually subscribe but just see if you even get allowed to, or if you get the same error if you must try: https://testflight.apple.com/join/oV8NNojg And here's how it's set up:

Hi there, I'm at a loss as to how to resolve this so hoping I can get some help/ideas here. Issue: We currently have two users who are unable to install our development iOS app. We sign the app as normal during the build process and upload it to firebase for distribution. Both of these users and their devices have been able to use this system previously, all our other dev users and devices are also still working but two of them receive an "this app cannot be installed because it's integrity could not be verified" error. What I have done to resolve: Check device UDIDs are both registered in apple developer portal Checked that the development profile has those devices included Checked that the development certificate is valid, this cert is being used with a different development app that isn't having this issue Restored the device disabled and reenabled the developer mode reinstalled the firebase distribution profile recreated the developer provisioning profile All of the above have not resolved the issue and I'm running out of ideas. If anyone has had the same issue or knows of something else we might be able to attempt that would be great. Thank you in advance John

Hello, I’m experiencing a serious issue with TestFlight. I correctly set up internal testing: • Added testers via email • Assigned builds • Everything shows as “Ready to Test” However, when trying to install via TestFlight, I get: “App Name couldn’t be installed” “The requested app is not available or doesn’t exist” ⚠️ Important note: This issue is NOT limited to a single app. It happens across all apps in my account. So it does not seem to be app-specific. What I’ve already checked: • Agreements, Tax, and Banking are completed • App Privacy is fully filled • Builds are successfully uploaded and selected • I am correctly added as an internal tester • Tried logging out/in of TestFlight • Reinstalled the app and TestFlight I contacted Apple Developer Support twice but received no response. Has anyone experienced this issue affecting multiple apps? Any help or guidance would be greatly appreciated. ⸻ Additional technical details: • Developer Account Apple ID: yilmaz34muhammed(at)icloud.com • App Store Connect App ID: 6762088121 • Bundle ID: com.devyilmaz.TahlilAI • Build Version: 0.2.0 (1) This issue occurs across all apps in my account.

Hello, I’m experiencing a serious issue with TestFlight. I correctly set up internal testing: • Added testers via email • Assigned builds • Everything shows as “Ready to Test” However, when trying to install via TestFlight, I get: “App Name couldn’t be installed” “The requested app is not available or doesn’t exist” ⚠️ Important note: This issue is NOT limited to a single app. It happens across all apps in my account. So it does not seem to be app-specific. What I’ve already checked: • Agreements, Tax, and Banking are completed • App Privacy is fully filled • Builds are successfully uploaded and selected • I am correctly added as an internal tester • Tried logging out/in of TestFlight • Reinstalled the app and TestFlight I contacted Apple Developer Support twice but received no response. Has anyone experienced this issue affecting multiple apps? Any help or guidance would be greatly appreciated. ⸻ Additional technical details: • Developer Account Apple ID: yilmaz34muhammed(at)icloud.com • App Store Connect App ID: 6762088121 • Bundle ID: com.devyilmaz.TahlilAI • Build Version: 0.2.0 (1) This issue occurs across all apps in my account.