TestFlight

RSS for tag

Use TestFlight in App Store Connect to invite and manage beta testers for iOS, iPadOS, tvOS, and watchOS apps. Discuss questions here and share app builds publicly via TestFlight under the Community topic.

TestFlight Documentation

Posts under TestFlight subtopic

Post

Replies

Boosts

Views

Activity

TestFlight builds expired across multiple apps; new builds cannot be installed (“Requested app is not available or doesn’t exist”)
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
136
11
10k
9m
TestFlight Beta Contract Missing – ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING
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.
54
7
6.5k
1h
TestFlight Installation Fails for All Apps in Account (“App Not Available” Error)
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.
1
0
120
1h
"account not in this store" error when testing inApp purchase
I've already done my test on development signed app locally, all in-app purchase runs well with sandbox tester Apple ID. Errors happens when make a purchase in distribution app from TestFlight. Detail Info: in Apple Store connect , make app available to China Electron project, packaging by electron builder using distribution sign upload to TestFlight, invite myself to test using my Apple ID(not the sandbox tester) to login and purchase dialog appears and said "Account not in this store" VPN is off Apple Store shows Chinese language and Chinese apps, not llikely to be u.s. store I'm suspecting that: Maybe shouldn't use my developer Apple ID to run TestFlight test? TestFlight locked app to be in u.s. store ?
12
4
2.1k
1d
Is TestFlight officially supported for a watchOS app on an Apple Watch configured with Apple Watch For Your Kids / Family Setup?
I’m validating the officially supported distribution path for an independent watchOS app. Target device Apple Watch Series 6 GPS + Cellular watchOS 26.6 Configured using Apple Watch For Your Kids / Family Setup The Watch belongs to a child Apple Account Managed from the parent/guardian’s iPhone 11 running iOS 27.0 The child does not have their own iPhone Direct development deployment from Xcode is not available in this configuration on my setup. The Family Setup Watch does not appear as a development destination / CoreDevice device and does not expose Developer Mode. Main question Does TestFlight officially support installing a watchOS-only or independently installable watchOS app onto an Apple Watch configured with Apple Watch For Your Kids / Family Setup? If yes: Is installation initiated from TestFlight on the parent/guardian iPhone that manages the Family Watch? Should the Family Setup Watch appear as an eligible Apple Watch target inside TestFlight? Should the child Apple Account or the parent/guardian Apple Account be added as the TestFlight tester? Are there any additional restrictions or requirements specific to Apple Watch For Your Kids / Family Setup? Is Developer Mode required on the Watch for TestFlight installation? I’m specifically asking about an officially supported TestFlight/App Store Connect distribution path, not Ad Hoc distribution, manual IPA installation, private APIs, or unsupported workarounds. Thank you.
1
0
306
1d
TestFlight Cannot Install: Build Status ‘Ready to Submit’ but unable to install on device
Hello, I'm having trouble installing my app via TestFlight. Current Status: The app build has been successfully uploaded and processed in App Store Connect. The build status currently shows "Ready to Submit" All export compliance questionnaires have been completed. The Issue: Even though everything looks ready on the dashboard, I cannot install the app on my phone via TestFlight. • (Specifically, the app is visible but throws an error when I click install-‘this app doesn’t exist or not available’). What I've Tried: • Checked that the testing group is properly linked to the build. • Re-signed into the TestFlight app on my device. Could App Store Connect Team Adviser help me with this issue please as soon as possible!
4
1
526
1d
Cannot upload to App Store Connect due to "ITMS-90288: Invalid Code Signing Entitlements" and ITMS-90885
I am referring to this post. I am struggling with this now, too, and thought it may get more likely some attention if I start a new post about it instead of adding a comment there (does it actually make a difference, though?). I read through (most of) the posts, mainly by Quinn, and cannot find what I'm still doing wrong. Upload with Xcode 13.4.1 still works, but with Xcode 16.3 or later I get both these errors and the warning of this topic: ITMS-90288: Invalid Code Signing Entitlements - The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile. According to the provisioning profile, the bundle contains a key value that is not allowed: '25856V4B4X.org.tempel.findanyfile.helper' for the key 'com.apple.application-identifier' in 'Find Any File.app/Contents/Library/LaunchServices/org.tempel.findanyfile.helper' ITMS-90885: 'Cannot be used with TestFlight because the executable “${executable}” in bundle “${bundle}” is missing a provisioning profile but has an application identifier in its signature. Nested executables are expected to have provisioning profiles with application identifiers matching the identifier in the signature in order to be eligible for TestFlight.' I must admit that I only have an entitlement file for the main app, not for the embedded apps and frameworks. Until now, it appeared that they got automatically adopted. So, I don't understand what the entitlement for the embedded apps needs to contain. The main apps's entitlement file is now: codesign -d --ent - …/"Find Any File.app" Executable=…/FAFv2 MAS Release 31.10.26, 13.38.xcarchive/Products/Applications/Find Any File.app/Contents/MacOS/Find Any File [Dict] [Key] com.apple.application-identifier [Value] [String] 25856V4B4X.org.tempel.findanyfile [Key] com.apple.developer.team-identifier [Value] [String] 25856V4B4X [Key] com.apple.security.automation.apple-events [Value] [Bool] true [Key] com.apple.security.cs.allow-jit [Value] [Bool] true [Key] com.apple.security.personal-information.addressbook [Value] [Bool] true [Key] com.apple.security.personal-information.calendars [Value] [Bool] true(I just added the application-identifier and team-identifier to the entitlement file in hopes that would solve this but it made no difference.) I also checked with the other cmd on the app in the xcarchive, getting this: tempi@TTsMini24 ~ % security cms -D -i …/Find\ Any\ File.app/Contents/embedded.provisionprofile <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>AppIDName</key> <string>Find Any File</string> <key>ApplicationIdentifierPrefix</key> <array> <string>25856V4B4X</string> </array> <key>CreationDate</key> <date>2026-10-31T12:30:46Z</date> <key>Platform</key> <array> <string>OSX</string> </array> <key>IsXcodeManaged</key> <true/> <key>DeveloperCertificates</key> <array>…</array> <key>DER-Encoded-Profile</key> <data>…</data> <key>Entitlements</key> <dict> <key>com.apple.application-identifier</key> <string>25856V4B4X.org.tempel.findanyfile</string> <key>keychain-access-groups</key> <array> <string>25856V4B4X.*</string> </array> <key>com.apple.developer.team-identifier</key> <string>25856V4B4X</string> </dict> <key>ExpirationDate</key> <date>2027-10-31T12:30:46Z</date> <key>Name</key> <string>Mac Team Provisioning Profile: org.tempel.findanyfile</string> <key>ProvisionedDevices</key> <array> … </array> <key>TeamIdentifier</key> <array> <string>25856V4B4X</string> </array> <key>TeamName</key> <string>Thomas Tempelmann</string> <key>TimeToLive</key> <integer>365</integer> <key>UUID</key> <string>…</string> <key>Version</key> <integer>1</integer> </dict> </plist>Any help would be appreciated. Actually, I just realize that I may be confusing entitlements and profile - the latter is the one I claim from Apple's website, right? I haven't visited that for years (though I already struggled understanding it back in the early years when this all started). Gonna see if I can make sense of it on the Apple dev website now. Update - no, that can't be it. When i create a new profile, I need to choose an identifier that describes the entitlements for my app, right? So I checked my current identifier for my app, and that lists lots of options like "5G Network Slicing" and "Access Wi-Fi Information", but none of them look anything like the entitlements that I am using. So, my plain identifier that has none of these options checked should be fine, shouldn't it? Which also means that the current profile I have used for years should be fine as well. What am I missing here? These error msgs from the MAS upload are not helpful at all. They tell me things that seem right to me, and then there's that text with the unfilled ${executable} and ${bundle}, which isn't helping either. This could be so much better. And there's no way to reliably get help from DTS directly any more either - that option has apparently been dropped for having to ask here in the forum, where I can only hope that someone will take a look at this. If it weren't for Quinn, we'd all be doomed already, probably. Til then, I may just have to keep building and submitting with Xcode 13, and admitting to my MAS customers that I'm unable to make my app look modern while the indie build release works with the modern look as that's not locked out by Apple.
5
0
184
2d
TestFlight: "The requested app is not available or does not exist" for internal testers + 422 ENTITY_UNPROCESSABLE on beta review (new individual account)
New individual account (Team ID UTH8X8R54P). App ID 6825129426, bundle com.lichooo.inercia. Since Oct 20, every processed build (latest 1.3.0 (7), uploaded Nov 2) fails to install for internal testers with "The requested app is not available or does not exist", including the account holder, whose Apple ID matches the one on the device. Submitting any build for external beta review returns 422 ENTITY_UNPROCESSABLE "Please try again later" (error IDs a82b110f-0641-44db-af8e-7452cb4bf93c and 4115b133-61c0-4135-9306-ba4bbe51514e). Already checked: Latest Program License Agreement and Free Apps Agreement accepted (Active) EU DSA trader status completed Export compliance answered (no non-exempt encryption) Test Information complete (description, feedback email, privacy policy, contact, review notes) Internal tester status Accepted, internal build state IN_BETA_TESTING Re-uploading builds and reinstalling TestFlight didn't help Support cases 103003383660 and 103004342314 are open with no resolution, and phone support is currently unavailable. Could someone from the TestFlight team check whether the account is missing the beta agreement (BETA_CONTRACT_MISSING) or has a backend flag? Thank you.
0
0
112
2d
TestFlight + Sandbox: consumable second purchase fails (DuplicateTransaction) on some devices, and product price sometimes returns USD — expected behavior, and recommended test setup?
We're testing In-App Purchases for our app distributed via TestFlight, using Sandbox Apple Accounts. We observe two device-dependent behaviors and have two questions. (App-specific details, including the bundle ID, are in our Feedback report FB24632077.) Observation 1 — Consumable second purchase fails with DuplicateTransaction on some devices The first purchase of a consumable succeeds and the transaction is finished. A second purchase of the same consumable then fails with PurchaseFailureReason.DuplicateTransaction ("This In-App Purchase has already been bought") on some devices. It correlates with sandbox session persistence: on devices where the purchase prompts for password only (e.g., iOS 26.x, iPadOS 18.4.1) the second purchase succeeds; on devices where it prompts for the account (email) + password every time (e.g., iOS 18.3.2, iPadAir2 15.6), the second purchase fails. The same Sandbox Apple Account behaves differently on different devices. An Ad Hoc (development-signed) build with the same account succeeds. Observation 2 — Product price sometimes returns USD instead of the storefront currency With the same Sandbox account (region: Japan), prices are shown in JPY on iOS 26.2 but in USD on iOS 18.3.2. The App Store app shows JPY, but SKProductsRequest / StoreKit 2 Product metadata returns USD. Question 1: Are these known Sandbox/TestFlight limitations? If so, what is the recommended way to reliably test repeat consumable purchases (and to get the correct storefront currency) in TestFlight across many devices and OS versions? Question 2: For TestFlight IAP testing, are there environmental differences between (A) using the device's real Apple ID (signed into Media & Purchases; automatic sandbox) and (B) signing out of Media & Purchases and using a Sandbox Apple Account — with respect to: reliability of repeat consumable purchases, authentication / session persistence (password-only vs account + password each purchase), storefront / currency resolution for product metadata, ability to clear purchase history? Which approach do you recommend for a consistent, reliable TestFlight IAP QA environment? Environment: TestFlight (App Store distribution), Sandbox tester region = Japan. (App-specific identifiers such as bundle ID are in our Feedback report FB24632077.) Repro: buy a consumable once (succeeds, finished) → buy the same product again → DuplicateTransaction on affected devices. Thanks!
1
0
435
2d
TestFlight: “Could not install. The requested app is not available or doesn’t exist.” (internal testers, incl. account holder) + external testing fails – Case ID 103006602341
Hello, My app uploads and processes successfully in App Store Connect, but nobody can install it from TestFlight, including me as the account holder. Tapping Install/Update fails with: “Could not install [App Name]. The requested app is not available or doesn’t exist.” Trying to add the build to external testing also fails with a message saying a technical issue occurred and to try again later.
0
0
61
2d
Can TestFlight for macOS replace an app in another user’s Applications folder?
On a Mac with two separate macOS user accounts, Account A has a daily-use app in its private ~/Applications folder. I want to install a TestFlight build with the same bundle ID from Account B. Can TestFlight detect, replace, or update the app in Account A’s private folder? Can the installation destination be selected? I also want to understand whether installing or launching the build under Account B can affect Account A’s app container or Application Support data. What Apple-supported setup would you recommend for testing the TestFlight build while protecting Account A’s app and data? Would a separate Mac or separate macOS installation be appropriate?
0
0
59
3d
All of my testers are not able to install the app
It is showing: "Could not install MY_APP_NAME. The requested app is not available or doesn't exist". I provided correct bundle id, otherwise I cannot be able to upload the app to TestFlight. Testers can also see the app in testflight but are not able to install it. What might me the cause of this issue and how can I fix it? I sent multiple requests to apple developer but got no reply
1
0
88
4d
TestFlight Review Delay – Seeking Guidance on Review Timeline
Hello everyone, We submitted a major update for our social networking app, Yuppi, on October 23, 2026. Both our TestFlight and App Store submissions are still in "Waiting for Review" status. Following a previous consultation with Apple's App Review team, we carefully addressed their feedback, completely redesigned our app, and introduced several new features. We fully understand and respect Apple's review procedures and standard timelines. However, our main priority at this stage is TestFlight. We would love to give our existing users the opportunity to experience and test our new design and features before the official App Store release. We completely understand that the App Store review may take additional time, and we have no concerns about following the standard process. We would sincerely appreciate any guidance from the Apple App Review team regarding whether our TestFlight submission could be reviewed first. We would also love to hear from other developers who have experienced similar TestFlight review delays. How long did your review take, and was there anything that helped move the process forward? Thank you all for your time and support.
0
0
98
5d
Individual to Organization Conversion Stalled - Faster to Create a New Organization Account?
Hi everyone, I'm stuck in Apple's account migration process and could use some advice from those who've been through this. My situation: Submitted individual → organization migration request Got initial response from Apple on June 15 (case #102620626191) Confirmed to proceed immediately Radio silence for 4+ days since then Key details: No existing apps or certificates to preserve Have a finished app ready to publish under business name ASAP Already have D-U-N-S number and LLC setup My question: Should I start a fresh organization account application in parallel, or will that cause conflicts since it's the same LLC/D-U-N-S number? Has anyone been in a similar situation? Did creating a new org account end up being faster than waiting for the migration to complete? Any insights on typical timelines for both processes would be greatly appreciated! Thanks!
1
1
393
5d
BETA_CONTRACT_MISSING blocks external TestFlight although all agreements are Active
Since Oct 20, every attempt to submit a build of my iOS app for Beta App Review fails with HTTP 422 BETA_CONTRACT_MISSING (POST /iris/v1/betaAppReviewSubmissions). I re-tested today (Oct 28) with a new build 14 and got the same error. The public TestFlight link shows "Not Found". What I have verified: In App Store Connect > Business, the Paid Apps Agreement, Free Apps Agreement, banking, tax (W-9) and DSA compliance all show Active. On developer.apple.com/account, the Apple Developer Program License Agreement (issued Oct 13, 2026) was accepted Oct 16, 2026, and there is no pending agreement banner. TestFlight Test Information is complete (beta description, feedback email, privacy policy URL, beta review contact, review notes, beta license agreement), and export compliance is set. Support case 103003034724 (opened Oct 20, follow-up Oct 23) and feedback FB25331734 have had no reply. Has anyone seen BETA_CONTRACT_MISSING with all agreements active? Could an Apple engineer please check my account? Thank you.
2
1
118
6d
ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING — TestFlight builds show as "Testing" but cannot be installed (internal and external), newly enrolled account
Hi, We cannot distribute any build via TestFlight. Both internal and external testing fail. This appears to be a server-side beta contract issue on the account. SYMPTOMS Builds upload and process successfully. All 8 builds show status "Testing" in App Store Connect with 84-90 days remaining. In the TestFlight app on device, the build appears with an Install button. Tapping Install fails immediately with: "Could not install [App]. The requested app is not available or doesn't exist." This happens for INTERNAL testing as well, which does not require Beta App Review — indicating the problem is not in the review pipeline. In App Store Connect, the "What to Test" step fails with: "There was an error processing your request. Please try again later." BROWSER CONSOLE EVIDENCE Repeated failures on the beta review submission endpoint: Failed to load resource: the server responded with a status of 422 https://appstoreconnect.apple.com/iris/v1/betaAppReviewSubmissions Also observed: 404 NOT_FOUND — /iris/v1/appTaxCategories/[app id] "There is no resource of type 'appTaxCategories' with id '...'" ACCOUNT STATUS — all verified Active Free Apps Agreement: Active (Oct 19, 2026) Paid Apps Agreement: Active (Oct 21, 2026) Bank account: Active Tax forms (Certificate of Foreign Status, W-8BEN): Active (Oct 21, 2026) Digital Services Act: Active (Oct 22, 2026) Apple Developer Program membership: current Account Holder accepted the Oct 13, 2026 Developer Program License Agreement This is a newly enrolled account; all agreements became Active Oct 19-22, 2026. BUILD CONFIGURATION Version: 1.0.0, builds 6 through 15, uploaded Oct 22 and Oct 28, 2026 — all AFTER the agreements became Active Processing status: Complete / Ready to Submit App Availability: configured, no territories stuck in "Processing" Encryption: ITSAppUsesNonExemptEncryption set in Info.plist History: First release cycle; app has never been removed from sale ALREADY TRIED Multiple new builds, removing and re-adding testers, new testing groups, reinstalling TestFlight, verifying Apple IDs match invitations, multiple devices and multiple Apple IDs. No change. QUESTION Could the beta contract for this account be re-provisioned on the App Store Connect backend? Per previous threads this appears to require internal action. Apple Support Case ID: 103005208314 Bundle ID: com.tirtik.tirtik This is a server-side issue, not device-side. A sysdiagnose can be provided on request. Thank you.
1
0
88
6d
Programatically install a specific build of an app in TestFlight
I’m looking for a supported way to programmatically install a specific build of an app distributed through TestFlight on a test device. My goal is to automate UI testing with XCUITest (via Appium): select a particular TestFlight build, install or update the app, and then run tests against that exact version. Is there an Apple-provided API, command-line tool, or recommended workflow for doing this? If not, is there a reliable way to automate the TestFlight app’s installation flow, including targeting a specific build? I also want to be able to automatically reinstall the app so I can isolate between multiple tests. I’m especially interested in whether this is supported on physical devices in CI and whether the answer differs for internal versus external TestFlight builds.
0
0
39
1w
TestFlight broken for whole team after accepting Free Apps Agreement – builds auto-expire, installs fail, beta submission 422
New organization account. Since accepting the Free Apps Agreement on Oct 27, 2026, TestFlight stopped working for all our apps: All builds are marked Expired within days of upload, without anyone expiring them. Internal testers get "The requested app is not available or doesn't exist" when installing. External submission returns HTTP 422 ENTITY_UNPROCESSABLE (no sub-code) from /iris/v1/betaAppReviewSubmissions. TestFlight worked on Oct 21–22 (builds installed by testers). Membership and agreements are active; app metadata, privacy and export compliance are complete. App Apple ID: 6825263720 Developer Support case: 103012517274 Feedback: FB25359930 Could someone from Apple check whether our team's TestFlight beta contract needs to be re-linked? Thank you.
0
0
65
1w
TestFlight builds expired across multiple apps; new builds cannot be installed (“Requested app is not available or doesn’t exist”)
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
Replies
136
Boosts
11
Views
10k
Activity
9m
TestFlight Beta Contract Missing – ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING
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.
Replies
54
Boosts
7
Views
6.5k
Activity
1h
TestFlight Installation Fails for All Apps in Account (“App Not Available” Error)
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.
Replies
1
Boosts
0
Views
120
Activity
1h
"account not in this store" error when testing inApp purchase
I've already done my test on development signed app locally, all in-app purchase runs well with sandbox tester Apple ID. Errors happens when make a purchase in distribution app from TestFlight. Detail Info: in Apple Store connect , make app available to China Electron project, packaging by electron builder using distribution sign upload to TestFlight, invite myself to test using my Apple ID(not the sandbox tester) to login and purchase dialog appears and said "Account not in this store" VPN is off Apple Store shows Chinese language and Chinese apps, not llikely to be u.s. store I'm suspecting that: Maybe shouldn't use my developer Apple ID to run TestFlight test? TestFlight locked app to be in u.s. store ?
Replies
12
Boosts
4
Views
2.1k
Activity
1d
Is TestFlight officially supported for a watchOS app on an Apple Watch configured with Apple Watch For Your Kids / Family Setup?
I’m validating the officially supported distribution path for an independent watchOS app. Target device Apple Watch Series 6 GPS + Cellular watchOS 26.6 Configured using Apple Watch For Your Kids / Family Setup The Watch belongs to a child Apple Account Managed from the parent/guardian’s iPhone 11 running iOS 27.0 The child does not have their own iPhone Direct development deployment from Xcode is not available in this configuration on my setup. The Family Setup Watch does not appear as a development destination / CoreDevice device and does not expose Developer Mode. Main question Does TestFlight officially support installing a watchOS-only or independently installable watchOS app onto an Apple Watch configured with Apple Watch For Your Kids / Family Setup? If yes: Is installation initiated from TestFlight on the parent/guardian iPhone that manages the Family Watch? Should the Family Setup Watch appear as an eligible Apple Watch target inside TestFlight? Should the child Apple Account or the parent/guardian Apple Account be added as the TestFlight tester? Are there any additional restrictions or requirements specific to Apple Watch For Your Kids / Family Setup? Is Developer Mode required on the Watch for TestFlight installation? I’m specifically asking about an officially supported TestFlight/App Store Connect distribution path, not Ad Hoc distribution, manual IPA installation, private APIs, or unsupported workarounds. Thank you.
Replies
1
Boosts
0
Views
306
Activity
1d
TestFlight Cannot Install: Build Status ‘Ready to Submit’ but unable to install on device
Hello, I'm having trouble installing my app via TestFlight. Current Status: The app build has been successfully uploaded and processed in App Store Connect. The build status currently shows "Ready to Submit" All export compliance questionnaires have been completed. The Issue: Even though everything looks ready on the dashboard, I cannot install the app on my phone via TestFlight. • (Specifically, the app is visible but throws an error when I click install-‘this app doesn’t exist or not available’). What I've Tried: • Checked that the testing group is properly linked to the build. • Re-signed into the TestFlight app on my device. Could App Store Connect Team Adviser help me with this issue please as soon as possible!
Replies
4
Boosts
1
Views
526
Activity
1d
Cannot upload to App Store Connect due to "ITMS-90288: Invalid Code Signing Entitlements" and ITMS-90885
I am referring to this post. I am struggling with this now, too, and thought it may get more likely some attention if I start a new post about it instead of adding a comment there (does it actually make a difference, though?). I read through (most of) the posts, mainly by Quinn, and cannot find what I'm still doing wrong. Upload with Xcode 13.4.1 still works, but with Xcode 16.3 or later I get both these errors and the warning of this topic: ITMS-90288: Invalid Code Signing Entitlements - The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile. According to the provisioning profile, the bundle contains a key value that is not allowed: '25856V4B4X.org.tempel.findanyfile.helper' for the key 'com.apple.application-identifier' in 'Find Any File.app/Contents/Library/LaunchServices/org.tempel.findanyfile.helper' ITMS-90885: 'Cannot be used with TestFlight because the executable “${executable}” in bundle “${bundle}” is missing a provisioning profile but has an application identifier in its signature. Nested executables are expected to have provisioning profiles with application identifiers matching the identifier in the signature in order to be eligible for TestFlight.' I must admit that I only have an entitlement file for the main app, not for the embedded apps and frameworks. Until now, it appeared that they got automatically adopted. So, I don't understand what the entitlement for the embedded apps needs to contain. The main apps's entitlement file is now: codesign -d --ent - …/"Find Any File.app" Executable=…/FAFv2 MAS Release 31.10.26, 13.38.xcarchive/Products/Applications/Find Any File.app/Contents/MacOS/Find Any File [Dict] [Key] com.apple.application-identifier [Value] [String] 25856V4B4X.org.tempel.findanyfile [Key] com.apple.developer.team-identifier [Value] [String] 25856V4B4X [Key] com.apple.security.automation.apple-events [Value] [Bool] true [Key] com.apple.security.cs.allow-jit [Value] [Bool] true [Key] com.apple.security.personal-information.addressbook [Value] [Bool] true [Key] com.apple.security.personal-information.calendars [Value] [Bool] true(I just added the application-identifier and team-identifier to the entitlement file in hopes that would solve this but it made no difference.) I also checked with the other cmd on the app in the xcarchive, getting this: tempi@TTsMini24 ~ % security cms -D -i …/Find\ Any\ File.app/Contents/embedded.provisionprofile <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>AppIDName</key> <string>Find Any File</string> <key>ApplicationIdentifierPrefix</key> <array> <string>25856V4B4X</string> </array> <key>CreationDate</key> <date>2026-10-31T12:30:46Z</date> <key>Platform</key> <array> <string>OSX</string> </array> <key>IsXcodeManaged</key> <true/> <key>DeveloperCertificates</key> <array>…</array> <key>DER-Encoded-Profile</key> <data>…</data> <key>Entitlements</key> <dict> <key>com.apple.application-identifier</key> <string>25856V4B4X.org.tempel.findanyfile</string> <key>keychain-access-groups</key> <array> <string>25856V4B4X.*</string> </array> <key>com.apple.developer.team-identifier</key> <string>25856V4B4X</string> </dict> <key>ExpirationDate</key> <date>2027-10-31T12:30:46Z</date> <key>Name</key> <string>Mac Team Provisioning Profile: org.tempel.findanyfile</string> <key>ProvisionedDevices</key> <array> … </array> <key>TeamIdentifier</key> <array> <string>25856V4B4X</string> </array> <key>TeamName</key> <string>Thomas Tempelmann</string> <key>TimeToLive</key> <integer>365</integer> <key>UUID</key> <string>…</string> <key>Version</key> <integer>1</integer> </dict> </plist>Any help would be appreciated. Actually, I just realize that I may be confusing entitlements and profile - the latter is the one I claim from Apple's website, right? I haven't visited that for years (though I already struggled understanding it back in the early years when this all started). Gonna see if I can make sense of it on the Apple dev website now. Update - no, that can't be it. When i create a new profile, I need to choose an identifier that describes the entitlements for my app, right? So I checked my current identifier for my app, and that lists lots of options like "5G Network Slicing" and "Access Wi-Fi Information", but none of them look anything like the entitlements that I am using. So, my plain identifier that has none of these options checked should be fine, shouldn't it? Which also means that the current profile I have used for years should be fine as well. What am I missing here? These error msgs from the MAS upload are not helpful at all. They tell me things that seem right to me, and then there's that text with the unfilled ${executable} and ${bundle}, which isn't helping either. This could be so much better. And there's no way to reliably get help from DTS directly any more either - that option has apparently been dropped for having to ask here in the forum, where I can only hope that someone will take a look at this. If it weren't for Quinn, we'd all be doomed already, probably. Til then, I may just have to keep building and submitting with Xcode 13, and admitting to my MAS customers that I'm unable to make my app look modern while the indie build release works with the modern look as that's not locked out by Apple.
Replies
5
Boosts
0
Views
184
Activity
2d
TestFlight: "The requested app is not available or does not exist" for internal testers + 422 ENTITY_UNPROCESSABLE on beta review (new individual account)
New individual account (Team ID UTH8X8R54P). App ID 6825129426, bundle com.lichooo.inercia. Since Oct 20, every processed build (latest 1.3.0 (7), uploaded Nov 2) fails to install for internal testers with "The requested app is not available or does not exist", including the account holder, whose Apple ID matches the one on the device. Submitting any build for external beta review returns 422 ENTITY_UNPROCESSABLE "Please try again later" (error IDs a82b110f-0641-44db-af8e-7452cb4bf93c and 4115b133-61c0-4135-9306-ba4bbe51514e). Already checked: Latest Program License Agreement and Free Apps Agreement accepted (Active) EU DSA trader status completed Export compliance answered (no non-exempt encryption) Test Information complete (description, feedback email, privacy policy, contact, review notes) Internal tester status Accepted, internal build state IN_BETA_TESTING Re-uploading builds and reinstalling TestFlight didn't help Support cases 103003383660 and 103004342314 are open with no resolution, and phone support is currently unavailable. Could someone from the TestFlight team check whether the account is missing the beta agreement (BETA_CONTRACT_MISSING) or has a backend flag? Thank you.
Replies
0
Boosts
0
Views
112
Activity
2d
TestFlight + Sandbox: consumable second purchase fails (DuplicateTransaction) on some devices, and product price sometimes returns USD — expected behavior, and recommended test setup?
We're testing In-App Purchases for our app distributed via TestFlight, using Sandbox Apple Accounts. We observe two device-dependent behaviors and have two questions. (App-specific details, including the bundle ID, are in our Feedback report FB24632077.) Observation 1 — Consumable second purchase fails with DuplicateTransaction on some devices The first purchase of a consumable succeeds and the transaction is finished. A second purchase of the same consumable then fails with PurchaseFailureReason.DuplicateTransaction ("This In-App Purchase has already been bought") on some devices. It correlates with sandbox session persistence: on devices where the purchase prompts for password only (e.g., iOS 26.x, iPadOS 18.4.1) the second purchase succeeds; on devices where it prompts for the account (email) + password every time (e.g., iOS 18.3.2, iPadAir2 15.6), the second purchase fails. The same Sandbox Apple Account behaves differently on different devices. An Ad Hoc (development-signed) build with the same account succeeds. Observation 2 — Product price sometimes returns USD instead of the storefront currency With the same Sandbox account (region: Japan), prices are shown in JPY on iOS 26.2 but in USD on iOS 18.3.2. The App Store app shows JPY, but SKProductsRequest / StoreKit 2 Product metadata returns USD. Question 1: Are these known Sandbox/TestFlight limitations? If so, what is the recommended way to reliably test repeat consumable purchases (and to get the correct storefront currency) in TestFlight across many devices and OS versions? Question 2: For TestFlight IAP testing, are there environmental differences between (A) using the device's real Apple ID (signed into Media & Purchases; automatic sandbox) and (B) signing out of Media & Purchases and using a Sandbox Apple Account — with respect to: reliability of repeat consumable purchases, authentication / session persistence (password-only vs account + password each purchase), storefront / currency resolution for product metadata, ability to clear purchase history? Which approach do you recommend for a consistent, reliable TestFlight IAP QA environment? Environment: TestFlight (App Store distribution), Sandbox tester region = Japan. (App-specific identifiers such as bundle ID are in our Feedback report FB24632077.) Repro: buy a consumable once (succeeds, finished) → buy the same product again → DuplicateTransaction on affected devices. Thanks!
Replies
1
Boosts
0
Views
435
Activity
2d
TestFlight: “Could not install. The requested app is not available or doesn’t exist.” (internal testers, incl. account holder) + external testing fails – Case ID 103006602341
Hello, My app uploads and processes successfully in App Store Connect, but nobody can install it from TestFlight, including me as the account holder. Tapping Install/Update fails with: “Could not install [App Name]. The requested app is not available or doesn’t exist.” Trying to add the build to external testing also fails with a message saying a technical issue occurred and to try again later.
Replies
0
Boosts
0
Views
61
Activity
2d
Can TestFlight for macOS replace an app in another user’s Applications folder?
On a Mac with two separate macOS user accounts, Account A has a daily-use app in its private ~/Applications folder. I want to install a TestFlight build with the same bundle ID from Account B. Can TestFlight detect, replace, or update the app in Account A’s private folder? Can the installation destination be selected? I also want to understand whether installing or launching the build under Account B can affect Account A’s app container or Application Support data. What Apple-supported setup would you recommend for testing the TestFlight build while protecting Account A’s app and data? Would a separate Mac or separate macOS installation be appropriate?
Replies
0
Boosts
0
Views
59
Activity
3d
All of my testers are not able to install the app
It is showing: "Could not install MY_APP_NAME. The requested app is not available or doesn't exist". I provided correct bundle id, otherwise I cannot be able to upload the app to TestFlight. Testers can also see the app in testflight but are not able to install it. What might me the cause of this issue and how can I fix it? I sent multiple requests to apple developer but got no reply
Replies
1
Boosts
0
Views
88
Activity
4d
TestFlight Review Delay – Seeking Guidance on Review Timeline
Hello everyone, We submitted a major update for our social networking app, Yuppi, on October 23, 2026. Both our TestFlight and App Store submissions are still in "Waiting for Review" status. Following a previous consultation with Apple's App Review team, we carefully addressed their feedback, completely redesigned our app, and introduced several new features. We fully understand and respect Apple's review procedures and standard timelines. However, our main priority at this stage is TestFlight. We would love to give our existing users the opportunity to experience and test our new design and features before the official App Store release. We completely understand that the App Store review may take additional time, and we have no concerns about following the standard process. We would sincerely appreciate any guidance from the Apple App Review team regarding whether our TestFlight submission could be reviewed first. We would also love to hear from other developers who have experienced similar TestFlight review delays. How long did your review take, and was there anything that helped move the process forward? Thank you all for your time and support.
Replies
0
Boosts
0
Views
98
Activity
5d
Individual to Organization Conversion Stalled - Faster to Create a New Organization Account?
Hi everyone, I'm stuck in Apple's account migration process and could use some advice from those who've been through this. My situation: Submitted individual → organization migration request Got initial response from Apple on June 15 (case #102620626191) Confirmed to proceed immediately Radio silence for 4+ days since then Key details: No existing apps or certificates to preserve Have a finished app ready to publish under business name ASAP Already have D-U-N-S number and LLC setup My question: Should I start a fresh organization account application in parallel, or will that cause conflicts since it's the same LLC/D-U-N-S number? Has anyone been in a similar situation? Did creating a new org account end up being faster than waiting for the migration to complete? Any insights on typical timelines for both processes would be greatly appreciated! Thanks!
Replies
1
Boosts
1
Views
393
Activity
5d
BETA_CONTRACT_MISSING blocks external TestFlight although all agreements are Active
Since Oct 20, every attempt to submit a build of my iOS app for Beta App Review fails with HTTP 422 BETA_CONTRACT_MISSING (POST /iris/v1/betaAppReviewSubmissions). I re-tested today (Oct 28) with a new build 14 and got the same error. The public TestFlight link shows "Not Found". What I have verified: In App Store Connect > Business, the Paid Apps Agreement, Free Apps Agreement, banking, tax (W-9) and DSA compliance all show Active. On developer.apple.com/account, the Apple Developer Program License Agreement (issued Oct 13, 2026) was accepted Oct 16, 2026, and there is no pending agreement banner. TestFlight Test Information is complete (beta description, feedback email, privacy policy URL, beta review contact, review notes, beta license agreement), and export compliance is set. Support case 103003034724 (opened Oct 20, follow-up Oct 23) and feedback FB25331734 have had no reply. Has anyone seen BETA_CONTRACT_MISSING with all agreements active? Could an Apple engineer please check my account? Thank you.
Replies
2
Boosts
1
Views
118
Activity
6d
ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING — TestFlight builds show as "Testing" but cannot be installed (internal and external), newly enrolled account
Hi, We cannot distribute any build via TestFlight. Both internal and external testing fail. This appears to be a server-side beta contract issue on the account. SYMPTOMS Builds upload and process successfully. All 8 builds show status "Testing" in App Store Connect with 84-90 days remaining. In the TestFlight app on device, the build appears with an Install button. Tapping Install fails immediately with: "Could not install [App]. The requested app is not available or doesn't exist." This happens for INTERNAL testing as well, which does not require Beta App Review — indicating the problem is not in the review pipeline. In App Store Connect, the "What to Test" step fails with: "There was an error processing your request. Please try again later." BROWSER CONSOLE EVIDENCE Repeated failures on the beta review submission endpoint: Failed to load resource: the server responded with a status of 422 https://appstoreconnect.apple.com/iris/v1/betaAppReviewSubmissions Also observed: 404 NOT_FOUND — /iris/v1/appTaxCategories/[app id] "There is no resource of type 'appTaxCategories' with id '...'" ACCOUNT STATUS — all verified Active Free Apps Agreement: Active (Oct 19, 2026) Paid Apps Agreement: Active (Oct 21, 2026) Bank account: Active Tax forms (Certificate of Foreign Status, W-8BEN): Active (Oct 21, 2026) Digital Services Act: Active (Oct 22, 2026) Apple Developer Program membership: current Account Holder accepted the Oct 13, 2026 Developer Program License Agreement This is a newly enrolled account; all agreements became Active Oct 19-22, 2026. BUILD CONFIGURATION Version: 1.0.0, builds 6 through 15, uploaded Oct 22 and Oct 28, 2026 — all AFTER the agreements became Active Processing status: Complete / Ready to Submit App Availability: configured, no territories stuck in "Processing" Encryption: ITSAppUsesNonExemptEncryption set in Info.plist History: First release cycle; app has never been removed from sale ALREADY TRIED Multiple new builds, removing and re-adding testers, new testing groups, reinstalling TestFlight, verifying Apple IDs match invitations, multiple devices and multiple Apple IDs. No change. QUESTION Could the beta contract for this account be re-provisioned on the App Store Connect backend? Per previous threads this appears to require internal action. Apple Support Case ID: 103005208314 Bundle ID: com.tirtik.tirtik This is a server-side issue, not device-side. A sysdiagnose can be provided on request. Thank you.
Replies
1
Boosts
0
Views
88
Activity
6d
Programatically install a specific build of an app in TestFlight
I’m looking for a supported way to programmatically install a specific build of an app distributed through TestFlight on a test device. My goal is to automate UI testing with XCUITest (via Appium): select a particular TestFlight build, install or update the app, and then run tests against that exact version. Is there an Apple-provided API, command-line tool, or recommended workflow for doing this? If not, is there a reliable way to automate the TestFlight app’s installation flow, including targeting a specific build? I also want to be able to automatically reinstall the app so I can isolate between multiple tests. I’m especially interested in whether this is supported on physical devices in CI and whether the answer differs for internal versus external TestFlight builds.
Replies
0
Boosts
0
Views
39
Activity
1w
TestFlight broken for whole team after accepting Free Apps Agreement – builds auto-expire, installs fail, beta submission 422
New organization account. Since accepting the Free Apps Agreement on Oct 27, 2026, TestFlight stopped working for all our apps: All builds are marked Expired within days of upload, without anyone expiring them. Internal testers get "The requested app is not available or doesn't exist" when installing. External submission returns HTTP 422 ENTITY_UNPROCESSABLE (no sub-code) from /iris/v1/betaAppReviewSubmissions. TestFlight worked on Oct 21–22 (builds installed by testers). Membership and agreements are active; app metadata, privacy and export compliance are complete. App Apple ID: 6825263720 Developer Support case: 103012517274 Feedback: FB25359930 Could someone from Apple check whether our team's TestFlight beta contract needs to be re-linked? Thank you.
Replies
0
Boosts
0
Views
65
Activity
1w