We are experiencing an issue when inviting a user to join our Apple Developer Program team through App Store Connect Users and Access. The purpose of adding this user is to include them as an internal TestFlight tester after the invitation is accepted. The invited user received the Apple Developer invitation email and clicked the "Accept invitation" link. The invitation link opens the following page: https://appstoreconnect.apple.com/activation_ds?key=... The page displays "Sign in to accept your invitation" and asks the user to sign in with an Apple Account. After the user signs in successfully, the page redirects back to the same sign-in page and asks the user to sign in again. The invitation cannot be accepted, and the user cannot join the Apple Developer Program team. Steps to reproduce: Go to Users and Access in App Store Connect. Add a new user and send an invitation to join the Apple Developer Program team. The invited user receives the Apple Developer invitation email. The invited user clicks the "Accept invitation" link. The page opens appstoreconnect.apple.com/activation_ds. The user signs in with an Apple Account. After signing in, the page redirects back to the same sign-in page. Repeating the sign-in process results in the same redirect loop. Expected result: The invitation should be accepted after the user signs in, and the user should be added to the Apple Developer Program team. Actual result: The page keeps redirecting back to the sign-in page, and the user cannot accept the invitation. Troubleshooting already tried: Safari and Chrome Private browsing mode Clearing browser cookies Signing out of Apple ID before opening the invitation link again Opening the link directly in the browser instead of an email app embedded browser The issue still occurs.

App: penombra notebook, Apple ID 6806388464, iPadOS, version 0.6, build 27. First submission from this account. Oct 1: submitted with build 23. Waiting for Review for 13 days, no status change, no message. Oct 14: replaced the build with 27 and resubmitted. Waiting for Review since Oct 14, 8:34 PM PT. After resubmitting on Oct 14, I requested an expedited review. No acknowledgment or decision as of Oct 19. Build 23 passed TestFlight beta review on Oct 1 within hours. The App Review section in App Store Connect shows no messages. Review notes, contact info and all metadata are complete. Developer Support case 103001747893 was opened on Oct 19. Is there anything on this submission that needs my attention? I can answer the same day in App Store Connect.

Hi everyone, Since October 16 I can’t use TestFlight at all on my individual developer account, and I’m hoping someone has seen this before. What happens Submitting any build for Beta App Review via the App Store Connect API returns: 422 ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING – "Beta contract is missing for the app." In App Store Connect the same action just shows “There was an error processing your request. Please try again later.” As an internal tester (status “Accepted”, build “In Beta Testing”), TestFlight on my iPhone says “The requested app is not available or does not exist.” App availability shows the content status CANNOT_SELL for my country (Türkiye), even though the app is free. What I’ve checked Free Apps Agreement and Paid Apps Agreement are both Active. No pending agreement to accept on developer.apple.com/account. Builds are processed and valid, export compliance answered (no non-exempt encryption). Test information, privacy policy URL, review contact and age rating are filled in. Pricing is set to Free and availability to Türkiye. I created a completely new app record with a new bundle ID: the first submission immediately returned BETA_CONTRACT_MISSING too, so it seems to be account-level. When it started TestFlight worked fine until the evening of October 16. That evening I updated my legal entity info, answered the Digital Services Act question (“not distributing in the EU”), and set up the Paid Apps Agreement with a bank account and W-8BEN. Right after that, all existing TestFlight builds expired on their own. My W-8BEN still shows “Missing Tax Info” (treaty claim checked on line 9 but line 10 empty), and the form is locked. I’ve contacted Developer Support but haven’t heard back yet. Has anyone run into BETA_CONTRACT_MISSING while all agreements show Active? Did support have to fix something on their side, or did updating the tax form or bank information resolve it? Thanks in advance!

Hi everyone, I've been struggling with a TestFlight issue for over a month, and I'm hoping someone here has encountered something similar or knows how to resolve it. I'm developing an iOS app called Bondi, and every time I try to submit a new build for external beta testing, App Store Connect returns an HTTP 422 error. I've tried contacting Apple Developer Support, but I haven't received a helpful response, and I'm completely blocked from distributing new builds to my external testers. The error: When submitting a build for Beta App Review, the following API request fails: { "data": { "type": "betaAppReviewSubmissions", "relationships": { "build": { "data": { "type": "builds", "id": "9fc5c303-4edb-4aee-9b39-75c8c8c53e1c" } } } } } The browser console shows: The server responded with a status of 422. API Response Error: TF_BETA_APP_REVIEW_RESPONSE status code: 422 api correlation key: SRKTSBKDZ2F7XPBJH7XFYSBUL4 In previous attempts, I also encountered this error: `ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING im not sure it's connect but I also noticed the following console warning: fetched via init(), using default/cached config values. What I'm trying to understand Has anyone encountered BETA_CONTRACT_MISSING when submitting a TestFlight build? Does TestFlight require any additional agreements, even for completely free applications? Could this indicate an issue with my Apple Developer account rather than the app itself? Is there any workaround to reset or reinitialize the TestFlight beta agreement? Can someone from Apple confirm whether this is a known issue? I've been blocked for over a month, and it's incredibly frustrating that App Store Connect provides no meaningful explanation of what's wrong.

A brand new app, uploaded through the normal export and upload flow, processes fine and shows "Ready to Submit" in App Store Connect. An internal tester sees it under "Currently Testing" in TestFlight, but tapping Install immediately shows: Could not install RollWave. "The requested app is not available or doesn't exist." This happens for all six builds I have uploaded. The Installs column in App Store Connect stays empty. The same source installs and runs from Xcode. Environment Device: iPhone XS Max, iOS 18.7.10 (registered in the developer account) Build tools: Xcode with the iOS 27.1 SDK, deployment target iOS 17.0, Swift 5.10, arm64 only Dependencies via Swift Package Manager: Google Mobile Ads 13.11.0, which pulls in Google User Messaging Platform 3.1.0 Tester: one internal tester in one internal group. Invitation accepted. The TestFlight app on the device shows the right build number. Account: new developer account. Free Apps Agreement became active on Oct 14, 2026. Paid Apps Agreement is Pending User Info because no bank or tax details are entered (the app is free). TestFlight app version on the device: [fill in] What I checked and changed, in order Minimum OS. Build Metadata shows minimum iOS 17.0 and Required Capabilities arm64. The phone is on iOS 18.7.10, so this is not an OS mismatch. Thinning variants. The "App File Sizes" table in Build Metadata lists an "iPhone XS Max" row (2.26 MB download), so a variant exists for the device. Price and availability. The app had no price schedule and no availability set when I first tried. I set Free and all countries and regions. Failure unchanged on later builds. Agreements. Free Apps Agreement is Active. Digital Services Act status is Active. Beta App Information. It was empty. I filled in the description, feedback email and privacy policy URL. No change. Device family. My project set iPhone only, but the target-level setting overrode it, so the build was flagged "iPhone, iPad". I fixed the target setting. No change for TestFlight. Privacy manifest. After submitting build 4 for review, App Review returned Invalid Binary with ITMS-91064 (invalid tracking information in the app's own PrivacyInfo.xcprivacy). Upload-time validation had passed. The manifest had NSPrivacyTracking true and an empty NSPrivacyTrackingDomains array. Removing the empty array key fixed the rejection. TestFlight install did not change on later builds. Upload path. Builds 1 to 5 were uploaded with altool and an API key after xcodebuild -exportArchive. Build 6 was exported and uploaded through xcodebuild -exportArchive with destination = upload (the same engine as Organizer). Same failure. Client side. Reinstalling TestFlight, restarting the device, and uploading fresh builds changed nothing. [Add anything else you tried.] Install from Xcode. [Fill in the result of running the app on the iPhone from Xcode.] One odd thing I found Both Google SDKs are static binary frameworks that Xcode embeds as small stub frameworks (only a privacy manifest and an empty dylib). The stub for User Messaging Platform declares MinimumOSVersion 100.0 in its Info.plist and minos 100.0 in its Mach-O build load command. Every release I downloaded, 2.7.0, 3.0.0 and 3.1.0, has that same Info.plist value, so it is how Google ships the framework. The stub for Google Mobile Ads says 13.0. I could not confirm whether this affects TestFlight, because I cannot test an install without the stub. It is the only unusual value in the bundle. Related reports Several other threads describe the same alert for internal testers with no confirmed cause or fix, for example thread 812811 and thread 829465. Some say it affects every app on the account or team and that Apple Support fixed it on their side. Questions Has anyone seen this resolved by something other than Apple Support? Can an embedded stub framework with MinimumOSVersion 100.0 break TestFlight installs while upload validation and processing still succeed? Is there any way to see why a build is unavailable to a specific tester, for example a distribution state in the API? I have a support case open or about to be opened and can share app and build identifiers with Apple on request.

iWeαlth is a household finance tracker for iPhone built in SwiftUI, with all data stored on device (GRDB/SQLite). There's no account and no backend that receives financial data. I'd especially appreciate feedback on: onboarding and first-run clarity (passcode, sample data) the expense keypad and the transaction detail screen the guided Enable Banking setup (an in-app web view that walks the user through registering their own PSD2 application), if you're in Europe and want to try it with your own accounts general UI polish on different iPhone sizes, light and dark mode Shared trips use a small relay where expense data is end-to-end encrypted with a key that only lives in the share link. TestFlight: https://testflight.apple.com/join/sQNvXPdJ Fastest path: Settings → "Load Sample Data". Thanks for any feedback!

I’m experiencing a persistent TestFlight installation issue that started after my most recent Apple Developer Program renewal. All builds upload and process successfully in App Store Connect/TestFlight, and there are no apparent issues with the builds themselves. However, when testers try to install the apps, they receive the following error: “The requested app is not available or doesn’t exist.” Since the same problem is affecting multiple apps under the same Apple Developer account, while the builds are uploading and processing successfully, I suspect this may be related to the TestFlight/App Store Connect distribution state or account-level backend configuration after the renewal. I have already checked the builds and TestFlight configuration, but the issue still persists. Has anyone experienced the same issue after renewing their Apple Developer Program membership? If so, were you able to resolve it, and did Apple Support have to fix something on the backend? Any guidance or suggestions would be greatly appreciated.

Hi, I have been using Testflight iOS app to test my apps before releasing to production. Over the past few weeks, I am unable to install any of my apps through Testflight. I also don't get any email notification that my app is live on Testflight. This is really important and it would be really helpful if I can find any solution to this. Thank you so much.

Hello, I'm hitting both of the following problems on the same app at the same time, and I believe something on Apple's side (a beta contract record) may be missing for my account or app. External testing: submitting a build for TestFlight external beta review fails. POST /v1/betaAppReviewSubmissions returns HTTP 422: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING: Beta Contract is missing. Error ID: c8dbd3ce-92b3-490c-a908-13663f07dc44 (October 14, 2026, 22:30 UTC) Internal testing: as the account holder and an internal tester, I can see build 16 (1.0.0) under "Currently Testing" in the TestFlight app, but tapping Install fails with "The requested app is not available or doesn't exist." (October 15, 2026, 04:51 and 05:36 UTC). I opened it from the "View in TestFlight" button in the invitation email. What I have checked: I accepted the agreement shown under Business in App Store Connect on October 14, 2026. The error has continued since then. Build 16 has finished processing (state: VALID) and shows as being tested in the internal group. The external tester group and Test Information (description, feedback email, privacy policy URL) are filled in. The Apple Account signed in to TestFlight on my iPhone is the same as the App Store Connect account holder. I opened a support case (102996922469) on October 15 and added the internal testing details, but I haven't received a reply yet. Other threads describe the same combination, and in at least one case it seems to have been fixed on Apple's side. Could someone from Apple check whether the beta contract record for my account or this app is missing? App: 雲来松 (Bundle ID: com.unraimatsu.app, Apple ID: 6790007313, Team ID: 794DY3RQ8N) Thank you.

I’m the developer of GridBot for iPhone and would appreciate feedback from up to 10 volunteer beta testers on the first-launch experience, backtest presentation (especially drawdowns), and the paper-trading demo. Platform: iOS. Planned App Store category: Finance. This testing round uses the paper-only demo server. No deposits, real trades or exchange API keys are needed. The app also contains live mode for users with their own server and exchange setup; please use only the paper demo for this test. Public beta: https://testflight.apple.com/join/CAtQ4vbE Installation on iPhone: install Apple’s free TestFlight app, return to this invitation and open the beta link again. Tap View in TestFlight if shown, then Accept and Install to install GridBot. If TestFlight is already installed, open the link directly. No email invitation or invitation code is needed. Please tell me where you hesitated during installation or first launch, whether paper mode was clear, and which backtest numbers were confusing. Screenshots and reproduction steps can be sent via TestFlight feedback. Historical results are not a promise of future trading performance.

Hoping a DTS engineer can take a look, as this seems to be the same backend issue described in threads 814565, 815875, 815885 and 813703. What's happening (team N74PHKXB5Q, individual Account Holder): Every TestFlight build on the account expired at the same moment on 30 Sep 2026, across unrelated apps. New builds upload and process fine (1.0 (2), (3), (4) of app 6817732435 are all Complete / In Beta Testing), but tapping Install in TestFlight on iPad and iPhone fails instantly with "Could not install - The requested app is not available or doesn't exist". The device log shows the install request to testflight.apple.com/v2/accounts/.../builds/.../install returning HTTP 404 (X-Apple-Jingle-Correlation-Key KARDZQVMLS5G3EAMOGBKFYGFEE). Submitting the same build for external testing through the App Store Connect API returns 422 ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING "Beta contract is missing for the app". "Report a Problem" from inside TestFlight opens a page that says it can't be found. Paid Apps and Free Apps agreements, bank and tax forms are all Active with nothing pending; the tester (the Account Holder) is Internal / Accepted; app availability is all territories; devices restarted; VPN off; testers removed and re-added with a fresh invite. App Store downloads work normally, so it's TestFlight only. Developer Support case 102981727998 was opened on 1 Oct 2026 with all of the above. No reply yet. Two questions, asked genuinely rather than as a complaint: Is this the known "Beta Contract entity not re-provisioned" condition from the threads above, and can it be re-provisioned on this account? I have a family member waiting to test a build for a wedding in November, so I'd be very grateful for a nudge. For future reference, what actually triggers it (membership renewal? agreement regeneration?) and is there anything a developer can do on their side to avoid or clear it, rather than waiting on a support case? Several of us seem to hit the same wall and the only documented fix so far is an engineer doing it manually. Happy to provide the full device log or file a Feedback Assistant report if that helps. Thanks for reading.

Hi everyone, I’m building Nivora, an iOS music discovery and social listening app. You can explore music, search for songs and artists, save favorites, create playlists, and listen together in shared sessions called Pulse. I’m looking for people who would be willing to try the TestFlight beta and share honest feedback. I’m especially interested in feedback about the first-time experience, music playback, finding and saving songs, playlists, and anything that feels confusing or broken. TestFlight: https://testflight.apple.com/join/BCsWqj48 If you try it, please include your iPhone model and iOS version when reporting a problem. Thanks for helping me improve Nivora.

I'm investigating a Restore Purchases failure in my app, PW Paycheck, which uses StoreKit 2. TestFlight purchases of consumable checks and an annual subscription have succeeded, but restoring purchases repeatedly fails. The failing call is: try await AppStore.sync() Apple displays an account password prompt. I enter my password and tap OK, after which the call throws. Our typed error classifier and NSError conversion report: StoreKitError.unknown StoreKit.StoreKitError: 2 This is the StoreKit.StoreKitError domain, not SKErrorDomain. We have not established whether authentication succeeded internally or what causes the failure. Environment: Physical iPhone 16 Pro; installed through TestFlight. App version 1.0 (20), bundle com.ggeller.pwpaycheck. In-app OS report: Version 26.6.2 (Build 23G90). Reported StoreKit price storefront: USA / 143491. Annual subscription: com.ggeller.pwpaycheck.pro.annual. Developed and uploaded using Swift Playgrounds on iPad. I have a Windows laptop and no Mac access. Steps: Open the TestFlight app with an existing unexpired annual test subscription. Open Payment Options and tap Restore Purchases. Enter the password in Apple's prompt and tap OK. AppStore.sync() throws the error above. The app then refreshes entitlements and displays a restore failure message. Observed results: Verified active subscription access is recognized before and after the failed operation. We do not count this as successful restoration. The subscription was canceled but still unexpired during the captured attempt. Build 19 produced the same NSError domain/code on Wi-Fi and cellular. Build 20 captured the typed .unknown classification on Wi-Fi. Our logger captured no additional underlying error. The latest attempt started at 2026-10-14T13:59:09Z and completed at 13:59:25Z, including the post-failure entitlement refresh. We are not treating this as evidence of a timeout. The restore action is user initiated, guarded against duplicate operations, and waits for an earlier entitlement refresh to finish before calling AppStore.sync(). What supported diagnostic or configuration check would help distinguish possible causes of this error, particularly without access to Xcode's device console? Also, how should we isolate a TestFlight-specific restore failure in a focused sample while preserving the relevant app/account context? A separate sample has been prepared, but compilation and reproduction are still pending.

Hi everyone, I'm Kiril, a solo developer. I'm looking for testers for Remolo, an iPhone and iPad app (with a small Mac companion) that puts your Mac's screen on your phone so you can control it right there. What it does the Mac's live screen above a trackpad with macOS gestures, a magnifier and full screen keyboard with modifiers and shortcuts, a shared clipboard, files both ways the Mac's Dock on the phone: switch apps, open their windows, snap windows Keynote from the phone with the next slide and notes; a clicker for any app; Apple Watch turns slides works at home directly and from anywhere through an end-to-end encrypted relay (Noise XX + CPace pairing), no accounts, no port forwarding Links TestFlight: https://testflight.apple.com/join/e4JNpMT4 Mac companion (free, notarized menu-bar app, macOS 15+): https://remolo.app/download Requires iOS / iPadOS 18 or later. Where feedback helps most Setup: how long from installing the Mac app to the first cursor move, and where you got stuck (Accessibility and Screen Recording permissions, pairing) Connecting from outside your home network: cellular, hotel or office Wi-Fi, CGNAT How the trackpad and screen feel: latency, scrolling, gestures, rotating to full screen iPad layout and Apple Watch slide control In the beta all Pro features are unlocked. Shake the phone to send a report from inside the app, or reply here. Thanks!

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:

Helix is an iOS app designed to help you better understand your health and fitness data from Apple Health. Instead of navigating through multiple screens and disconnected metrics, Helix brings everything together in a clean, interactive dashboard with detailed analytics and personalized insights. Key features: 🏃 Running & Cycling: Performance analysis, pace, distance, heart rate, splits and workout trends. ❤️ Heart Health: Resting heart rate, HRV and cardiovascular trends. 🌙 Sleep: Sleep stages, duration and recovery insights. 🍎 Nutrition: Calories, macronutrients and nutritional trends. ⚖️ Body Composition: Weight, BMI and body composition tracking. 📊 Personalized Insights: Health trends, visual analytics and Daily Coach recommendations. Who we're looking for We're looking for iPhone users who regularly use Apple Health, especially those who track workouts with an Apple Watch. No technical experience is required. We welcome feedback from both fitness enthusiasts and everyday Apple Health users. What we'd like you to test Install Helix through TestFlight and grant access to the Apple Health data you're comfortable sharing. Explore the Dashboard, Running, Sleep, Heart, Nutrition and Body sections. Compare the metrics displayed in Helix with those in Apple Health or Apple Fitness. Try the Daily Coach and personalized insights. Report any incorrect values, missing data, crashes or confusing interactions. Estimated testing time: 15–20 minutes for an initial exploration. Feedback we're interested in Data accuracy and consistency with Apple Health App performance and stability Interface design and ease of use Missing or incorrect health metrics Suggestions for improvements TestFlight beta link: https://testflight.apple.com/join/8BMfABPa Thank you for helping improve Helix before its official release!

I am unable to submit builds for External TestFlight review or install builds as an internal tester. Error in browser console (422): ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING "Beta contract is missing for the app." TestFlight app shows: "The requested app is not available or doesn't exist." Account details: App: تطوّر - Evolve (Bundle ID: sa.evolve.app) Individual developer account, I am the Account Holder All agreements (Free + Paid Apps) are Active Bank account and tax forms are Active App Privacy: Published (11 data types) Age Rating: Completed Export Compliance: Set (ITSAppUsesNonExemptEncryption: false) Multiple builds tested (1.0.0 builds 15-16, 1.0.1 build 17) Issue affects both internal installs and external submissions Apple Support Case: 102897579430 Could an Apple engineer please check and reset/reattach the Beta Contract on my account? Thank you.

Hello everyone. We're looking for testers for our iPhone and iPad app Lunch Trio (German: Mittagstrio). Every day it suggests three lunches. Pick one and you get a step-by-step recipe for 2 or 4 people and a shopping list sorted by aisle. Vegetarian, vegan and family-friendly options; German, Italian and Colombian dishes. Available in English, German and Spanish. No account, no ads, no personal data collected. TestFlight link: https://testflight.apple.com/join/ZqtxMAHW Requires iOS / iPadOS 26 or later. Website: https://mittagstrio.de The recipes were developed with AI assistance and haven't been kitchen-tested yet, so feedback from actually cooking a dish helps most: Did amounts and cooking times work? Was any step unclear? Is the shopping list practical in the store? Any layout or usability issues, especially on iPad? For meat, fish or eggs, please check the core temperature with a thermometer. Feedback via TestFlight (screenshot → share) or right here. Thanks!

I currently have multiple macOS app icons configured in my project: AppIcon.icon AppIcon-Development.icon AppIcon-Beta.icon In Xcode, I can assign different app icons for Debug and Release configurations, which works well for local development and production builds. However, I cannot find any equivalent way to specify a dedicated app icon for TestFlight distributions. I would like TestFlight builds to automatically use AppIcon-Beta.icon. Where is this configured, or what is the recommended approach? Is there a specific build setting, archive configuration or App Store Connect mechanism for this, or do I need to handle it manually using build configurations or schemes? Thanks.

I’m working on my first app and I wanted to add someone to TestFlight to help me test it. I submitted it for review and it was rejected because it’s asking for demo credentials. However, my app doesn’t use any credentials at all. It is fully local, doesn’t communicate or send any telemetry to any servers. The only servers it hits is Gmail and iCloud, if the user chooses to connect their mailboxes, and for backups to iCloud Drive. do I reach out to them and tell them that this app doesn’t need credentials or do I create a demo mode of the app and resubmit?