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

Account-wide TestFlight build expiration issue — Feedback ID: FB25656884
@DTS Engineer (Albert), I am experiencing the exact same issue across all 3 apps on our team account (TJ9KJ6WV99). Every newly uploaded, validated build (Binary State: Validated, beta-reports-active: true) automatically changes status to Expired within 30–60 minutes of upload and disappears from TestFlight, despite all agreements (Paid Apps, Free Apps), Tax Forms, and DSA Compliance being verified Active (since account reactivation on Oct 29, 2026). Apple Support performed a backend process restart 48 hours ago which temporarily resolved the issue, but all new builds reverted to Expired again today within an hour (matching the BETA_CONTRACT_MISSING / backend state desync reported earlier in this thread). Feedback Assistant Ticket: FB25656884 (includes Team ID TJ9KJ6WV99 and all 3 numeric App IDs). Thanks in advance for routing this to the TestFlight / App Store Connect team!
0
0
89
5h
TestFlight unusable on new paid account: no invite emails, Beta App Review submission always fails
Hello, My Apple Developer Program membership is paid and active (individual account, enrolled 11 Nov 2026), but I cannot use TestFlight at all, and Developer Support has not replied. What works Builds upload and process fine (processing state VALID). Free and Paid Apps agreements, bank account, tax forms and DSA compliance are all "Active" in App Store Connect > Business. Export compliance, age rating, category, Beta App Review contact info, beta description, feedback email and privacy policy URL are all filled in. What does not work Internal testing: testers are added and stay in "Invited" status, but the invitation email never arrives (checked spam, tried iCloud and Gmail addresses, resent several times). External testing: submitting a build to Beta App Review always fails. On the App Store Connect website I get "There was an error processing your request. Please try again later." The App Store Connect API (POST /v1/betaAppReviewSubmissions) returns HTTP 422 ENTITY_UNPROCESSABLE, "Please try again later." Same result for different builds, the existing external group and a brand new group, over several days (13 attempts in total). A second app on the same account shows the same symptoms, so it looks account-level, not app-level. Example error IDs from the API: 5cbd887c-80d7-4dcf-bcea-94377c972ffb, d9761cf6-5584-413f-826d-017dd6a5029b, 97644394-7884-4ce6-bfdc-cc065c4a12d6, d8771b1e-4860-48ee-92bb-86e93161832a Support case 30000014824443 (Distribution / TestFlight): three messages since 14 Nov, no reply. Has anyone seen this on a newly enrolled account, and is there anything I can do on my side? If an Apple engineer can look at the error IDs above, I can share the app Apple ID and team ID privately. Thank you.
1
0
108
15h
TestFlight dead on new accounts (Oct-Nov 2026): no invite emails, Beta App Review 422 "Please try again later". Collecting all cases here
This thread collects every account with the fault below in one place, so Apple sees one issue across many accounts instead of many lonely threads. If you have it, please reply. What to include is at the end. The fault Builds upload and process fine. Then two things never work: No TestFlight invite email is ever sent. Every tester, internal or external, stays "Invited". Reinvite does nothing: POST /iris/v1/betaTesterInvitations returns 201 Created and no email arrives, not in spam either. A build cannot be submitted for Beta App Review. "There was an error processing your request. Please try again later." POST /iris/v1/betaAppReviewSubmissions returns 422 ENTITY_UNPROCESSABLE with only that sentence and no further reason. So internal testing is blocked by the missing emails and external testing by the refused review. Agreements, tax, banking and DSA are Active, Test Information and export compliance are complete, and nothing a developer can change makes a difference. The accounts reporting it are mostly new, enrolled around October 2026. My case Account enrolled 31 October 2026. Fault since 5 November 2026, every day. Region: Türkiye. No invite email reaches any of my six testers. Beta App Review submit returns the 422 every time. On 13 November I reset everything to rule out my side: removed every tester and both groups, expired the old builds, uploaded a fresh build, added everyone again. Nothing changed. The fresh build is VALID. Its internal state is IN_BETA_TESTING with "automatically notify testers" on, yet its record says the testers were not notified. Its external state is READY_FOR_BETA_SUBMISSION and the submit is refused. Feedback Assistant: FB25540791 (two HAR logs). Developer Support cases 30000005155573 and 30000005989992: only automatic receipts since 4 November, no human reply. Phone support shows as unavailable. Others reporting it https://developer.apple.com/forums/thread/856330 (@Hopeforge): internal invite emails never delivered, testers stay "Invited". Recreating groups, resending and new builds did not help. An App Store Connect Engineer replied there and asked for Feedback Assistant tickets with HAR logs. https://developer.apple.com/forums/thread/857012 (@Kirnuvirsta): tester stuck on "Invited" with no email, Beta App Review submit fails, same on a second app record. FB25399719, case open since 28 October. https://developer.apple.com/forums/thread/856896 (@medlzd, @ganderbite): new internal testers show "Invited" and never get the email, Resend Invite does nothing, on all apps. https://developer.apple.com/forums/thread/856592 (@EmlakBaseDev): Beta App Review submit returns 422 "Please try again later" on three apps since 24 October, build VALID and READY_FOR_BETA_SUBMISSION. https://developer.apple.com/forums/thread/854803 (@SefaAygun, @JanuaryTwelfth): adding a build to external testing fails with "try again later". https://developer.apple.com/forums/thread/854106 (@BWGTrading): new organization account, TestFlight stopped working for all apps on 27 October. If you have this too, please reply with When your account was enrolled, and since when the fault shows Which of the two you have: no invite emails, 422 on Beta App Review, or both Your country or region, to see whether it is tied to one Your Feedback Assistant number (FB...) and Developer Support case ID Anything Apple told you, and above all whether it got fixed, and how If you have not filed a Feedback Assistant ticket yet, please do: steps, a HAR log of the failing request, your App ID. The engineer in thread 856330 asked for exactly that. To Apple Could someone from the App Store Connect or TestFlight team tell us whether this is a known fault in how TestFlight is set up for newly enrolled accounts, and whether each account needs a change on your side? We are paying members who cannot use TestFlight at all, and our support cases stay unanswered for weeks. Thank you.
17
8
827
20h
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
154
13
12k
1d
TestFlight dead on new account: internal invites never sent, 422 ENTITY_UNPROCESSABLE on beta review
Since my first TestFlight upload on November 2, 2026, TestFlight does not work for my app at all. This looks like the same account-level issue many developers have reported since late October 2026. Region: Türkiye Account: individual, enrolled October 26, 2026; latest Program License Agreement accepted November 6 App ID: 6828238853, builds 1.0 (1) and 1.0 (2) Symptoms: Internal testers stay "Invited", the INVITES column stays empty and no invitation email is ever sent. Submitting a build for external beta review always fails: POST /iris/v1/betaAppReviewSubmissions returns 422 ENTITY_UNPROCESSABLE "There was an error processing your request. Please try again later." Error ID: a254e078-e9a9-44c4-be23-3d75d6d8daad API correlation key: 4IHT4ZPBDXIOSMH6J2GPZTDU5E Even saving "What to Test" notes for an internal build fails with "Validation Error". Already checked: Free Apps Agreement and DSA are active, Test Information, privacy policy, App Privacy, age rating and export compliance are complete, ITSAppUsesNonExemptEncryption = NO. A new build, reinvites and removing/re-adding testers did not help. Developer Support case 30000005085209 has been open since November 4. A reply dated November 17 shows on the case but the email never arrived. Could someone from the TestFlight team please check and re-provision the TestFlight setup for my account?
2
0
170
1d
TestFlight not working for new account: invitations never sent, Beta App Review submission returns 422
Problem 1: External Beta App Review submission always fails Submitting the build to an external group fails both in App Store Connect ("Submit for Review") and via the App Store Connect API (POST /v1/betaAppReviewSubmissions) with: 422 ENTITY_UNPROCESSABLE, "There was an error processing your request." / "Please try again later." No sub-code and no field is named. It has failed consistently for more than a day. Error IDs: 87d6bf69-3f70-485a-ae69-a3e3dc4f5acd 85377625-b7e8-45d2-a3ac-bc34f083e693 eb1396ca-8869-4a34-84b1-24f6dcbf0b65 (2026-11-20 12:57 UTC) Immediately before the last attempt, the build showed externalBuildState=READY_FOR_BETA_SUBMISSION, and there was no pending submission. Problem 2: Internal tester invitations are never emailed The build is IN_BETA_TESTING in the internal group. Testers stay "Invited", and no invitation email ever arrives. Resending the invitation via the API returns 201 Created (invitation ID b6a6d90c-607d-4ae4-9277-de79ca752130), but nothing is delivered. I checked the inbox and junk folders on icloud.com. The app does not appear in the TestFlight app on my iPhone. This also happened with builds 1 and 2. Already verified Free Apps Agreement: Active. The Paid Apps Agreement shows "Pending User Info"; the app has no paid content. Build 3 was uploaded with App Store Connect distribution (APP_STORE_ELIGIBLE); export compliance is declared in Info.plist (ITSAppUsesNonExemptEncryption = NO). Test Information, Beta App Review contact details, What to Test and age rating are complete. All 6 internal testers are active App Store Connect users. The Apple ID signed in to TestFlight is the same as my App Store Connect account. The device runs iOS 26.1 (minimum is 26.0). No open incident on Apple System Status. Several developers with new accounts report the same two symptoms on the Developer Forums (threads 857429, 856330, 856863). One case was resolved on Apple's side through Developer Support. Please check the TestFlight provisioning of my account and escalate to engineering if needed. I can provide screen recordings and HAR logs.
0
0
37
1d
TestFlight - 422 ENTITY_UNPROCESSABLE
Enrolled: 10 Nov 2026. First builds uploaded 11–12 Nov 2026, fault seen from the very first build. Internal testers stay "Invited", the invitation e-mail never arrives (Resend, removing/re-adding testers and new builds did not help). Other Apple e-mails reach the same addresses normally. Beta App Review submit always fails with "There was an error processing your request. Please try again later." — POST betaAppReviewSubmissions returns 422 ENTITY_UNPROCESSABLE, both in the web UI and through the App Store Connect API. No betaAppReviewSubmission is created. Builds are VALID, external state READY_FOR_BETA_SUBMISSION. Same result from the Account Holder's own session and from the Admin's session. What we checked / tried, none helped: All agreements accepted (Program License Agreement, Free Apps Active), DSA compliance completed. Test Information, Beta App Review Information, What to Test, export compliance all complete. New builds with new build numbers. A brand-new app record with a NEW bundle ID in the same team: exactly the same two symptoms. Two observations that may help others: Another newly enrolled individual team that we manage (same week, same Admin user, same CI pipeline, same Test Information) works normally: invites arrive, external submission goes to Waiting for Review. So it looks team-specific, not setup-specific. App Store submission is NOT blocked: the same build went to "Waiting for Review" for App Store review without problems. Only TestFlight is affected. Two Developer Support cases are open (Membership and Account), automated replies only so far. Following b2mode's update, I will also file under Distribution > TestFlight. Will report back here when it is resolved.
0
1
47
1d
Beta testers wanted: Starbit Dash, retro pixel space shooter (iPhone, iOS 17+)
Hi everyone! I’m looking for beta testers for Starbit Dash, a twin-stick space shooter for iPhone with pixel art and a handheld console look. 6 acts, 18 bosses with their own attack patterns, endless mode with up to 4 bosses at once Perks after every boss, 30 pilot levels, unlockable rockets No ads, no tracking, no account; works offline What I’d most like feedback on: Is Act 1 too easy, too hard or just right? Anything confusing in the menus or the workshop? Join the beta: Starbit Dash Testflight Feedback via TestFlight screenshot or as a reply here. Thanks!
0
0
35
1d
TestFlight external "Submit for Review" fails with "There was an error processing your request" (all apps, new and old)
Since about 17 November, adding a build to an external TestFlight group and pressing Submit for Review fails every time in App Store Connect with: "There was an error processing your request. Please try again later." What I've tried: Several different builds of one app (builds 1, 3, 4 and 5), uploaded with Xcode 27.2. Two different external groups. A brand-new app record with a new bundle ID. An older app on the same team that was set up before the problem started. It fails the same way. Declaring my DSA trader status, then retrying. What works: uploads, processing ("Ready to Submit"), and internal testing. External testing never gets as far as "Waiting for Review". The Apple Developer System Status page shows nothing about TestFlight or App Store Connect. I've had a support case open for several days with no reply yet. It looks like a team- or account-level fault, since it affects every app I try. Has anyone else seen this, or found a fix? I'd also be grateful if an Apple engineer could check this. Thanks.
2
1
95
1d
Looking for beta testers: Remolo, your Mac's screen on iPhone and iPad (iOS, iPadOS, macOS, watchOS)
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!
4
0
335
2d
SKPaymentQueue.default().storefront?.countryCode returns "USA" only in TestFlight
Hi everyone, I'm encountering an issue where the storefront country code returns "USA" unexpectedly in TestFlight builds, and I'd appreciate any insights from the community. Issue Description When executing SKPaymentQueue.default().storefront?.countryCode in our TestFlight builds, the property returns USA. However, we expect it to return JPN because both the Sandbox test user account and the Apple Account region configured on the device are set to Japan. Behavior Across Environments Xcode Debug & Ad Hoc Builds: Returns JPN as expected. TestFlight Builds: Returns USA unexpectedly. Related Threads I've noticed several threads reporting similar issues without a clear resolution: https://developer.apple.com/forums/thread/660817 https://developer.apple.com/forums/thread/794932 https://developer.apple.com/forums/thread/800078 https://developer.apple.com/forums/thread/814178 https://developer.apple.com/forums/thread/810860 Questions Is this USA value a known TestFlight/Sandbox-specific limitation or bug? Will production users in Japan correctly receive JPN (and see JPY prices) once the app is approved and published on the App Store? Is there any workaround or project configuration fix required on our side prior to App Store submission? Has anyone experienced this recently or confirmed the behavior in the production environment after release? Thanks!
3
1
668
2d
Cloudless AI - on-device AI for pictures, short films, sound and music (iPhone, iPad, Mac)
I'm an individual developer testing Cloudless AI, an app that makes pictures, short films (5 to 10 seconds), sound effects and music entirely on the device. There is no server and no account. TestFlight public link: https://testflight.apple.com/join/Y1gkZt8W Platforms: iOS, iPadOS, macOS Category: Photo & Video What to test First run: model download and preparation. Note how long it takes and whether anything fails. Pictures: people and faces, the cartoon and anime styles, and the photo tools (face fix, enlarge, erase, blur background, cut-out). Films from a description or a picture: does the film follow your description, and how warm does the device get? Sound and music from a description. Memory and heat on devices other than an iPhone 17 Pro or an M1 Pro Mac. That's all I've tested properly, so reports from older iPhones and iPads are especially welcome. Please tell me your device and iOS version, the time to the first result, and anything confusing or wrong. Feedback also goes through Settings > Help > Report a problem in the app (nothing is sent unless you press Send) or through the TestFlight app.
0
0
63
2d
App Replacement - How to test in TestFlight
Has anyone gotten the App Replacement dialog to show up when launching an app configured with the replacement bundle identifiers in TestFlight? Per the documentation is says app [re]placement can be tested via TestFlight. https://developer.apple.com/documentation/bundleresources/entitlements/com.apple.developer.superseded-application-identifiers I've tried these two scenarios and have not gotten the system prompt to appear yet, all testing done on iOS 27.2 or 27.3 beta 1/2. Scenario A: App 1 installed via TestFlight, bundle "abc" App 1 launched App 2 installed via TestFlight, bundle "def" --> replacement entitlement configured to replace "abc". Scenario B: App 1 installed via App Store, bundle "abc" App 1 launched App 2 installed via TestFlight, bundle "def" --> replacement entitlement configured to replace "abc". In neither scenario did the system present the modal for me to transfer data or delete the previously installed app. Are there minimum usage or filesystem requirements that need to be present in the original and replaced app? FB25559759 - TestFlight / App Replacement: App Replacement did not trigger as described by documentation when installing from TestFlight
0
0
57
3d
TestFlight external Beta App Review fails with HTTP 422 across multiple apps on the same developer team
Hi everyone, I’m unable to submit builds for external TestFlight testing across multiple iOS apps on the same Apple Developer team. The builds upload successfully, but clicking “Submit for Review” in App Store Connect fails before the build enters Beta App Review. Here’s one example I reproduced and captured in Chrome DevTools: App: Benny Wallet App Apple ID: 6834886147 iOS version and build: 0.3.1 (104) Build status: Ready to Submit Request: POST /iris/v1/betaAppReviewSubmissions Response: HTTP 422 ENTITY_UNPROCESSABLE Error message: “There was an error processing your request. Please try again later.” Both the Free Apps and Paid Apps agreements show as active. I reproduced the error with “Automatically notify testers” turned off as well. Other apps on the same team show the same submission error in the UI. This looks similar to the reports in https://developer.apple.com/forums/thread/857429. Has anyone with the same HTTP 422 across multiple apps managed to get external TestFlight submissions working again? If so, what fixed it? If someone from the App Store Connect or TestFlight team is able to look into this, could you check whether there’s an issue with our team’s beta distribution authorization or Beta Contract association? I’ve filed Feedback Assistant report FB25625640. I can provide the Apple request UUID and UTC timestamp through that report if needed. Thanks, Frank
0
1
55
3d
TestFlight installation returns 404 for one developer account; other accounts work
The error shown in TestFlight is: “The requested app is not available or doesn’t exist.” The HTTP 404 mentioned below is the historical install-service response, not the wording displayed to users. I am trying to resolve a TestFlight installation failure that appears specific to one developer account. None of the users we have tested can install our apps. What I have observed: Installation of build 964 returned HTTP 404 from the install service. The internal tester was assigned to the build, and the build was not expired. TestFlight apps from another organization install successfully on the same device. A newer build, 969, was marked ready on November 12, 2026. I have now tested it, and it also fails to install with the same error message as before. Account timeline: The account was migrated from individual to organization, with migration completed on October 23, 2026. The installation issue began after the migration request but before completion. I do not know whether the migration is related; I am including the timeline in case it helps narrow down the checks. Has anyone encountered this account-specific install-service 404? What should I check to distinguish a build or tester configuration issue from an account-side distribution issue? If this needs Apple investigation, which diagnostics would be most useful to provide privately? I found a potentially similar report at https://developer.apple.com/forums/thread/837330, but I do not have confirmation that it has the same cause.
1
0
73
3d
TestFlight broken for every app on my team: installs fail, no invitation emails, beta review submission returns 422 (case 30000010345074)
Hello. Since November 2, 2026, TestFlight has been unusable for all apps on my team (Team ID 8NNQY8P7EP), including apps that are live on the App Store : In the TestFlight app, Install always fails with "Could not install [app]. The requested app is not available or doesn’t exist", although the builds are listed. This happens on every app of the account. Tester invitation emails are no longer delivered, on any app. The API returns 201 for the invitation, but no email arrives. Removing and re-inviting a tester does not help. Submitting a build for external beta review fails with 422 ENTITY_UNPROCESSABLE "There was an error processing your request. Please try again later." (app 6830730952, build 5), both in App Store Connect and through the API. My membership and agreements are active. On November 2, I expired some builds, removed testers and deleted one unpublished app from the account; the problems started around that date. The same symptoms are reported in many other threads on this forum. Support case 30000010345074 has been open since November 9 without a reply. Could someone from Apple please check the TestFlight status of my account ? Thank you !
0
0
87
4d
TestFlight invitations not sent to any internal testers – account-level issue
Hello, I’m following up on case 30000013215244, opened 4 days ago, still without a response. TestFlight invitation emails are not being delivered to any internal tester on my account, including myself (Account Holder). The app does not appear in the TestFlight app for any of us. App name / Apple ID: Cosmine / 6825922062 Team ID: 5YFU7N787S Build 1.0.0 is processed and shows “Testing” in the internal group All testers are active App Store Connect users and are added to the internal group The Apple Account on each device matches the invited email Already tried: resending invitations, removing and re-adding testers, creating a new internal group, reinstalling TestFlight All agreements are active Since this affects multiple testers and not just one device or account, I believe this is an account-level issue on Apple’s side (possibly related to the beta contract). Could you please escalate this to the TestFlight team? Thank you.
0
1
85
5d
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.
60
8
7.2k
5d
Account-wide TestFlight build expiration issue — Feedback ID: FB25656884
@DTS Engineer (Albert), I am experiencing the exact same issue across all 3 apps on our team account (TJ9KJ6WV99). Every newly uploaded, validated build (Binary State: Validated, beta-reports-active: true) automatically changes status to Expired within 30–60 minutes of upload and disappears from TestFlight, despite all agreements (Paid Apps, Free Apps), Tax Forms, and DSA Compliance being verified Active (since account reactivation on Oct 29, 2026). Apple Support performed a backend process restart 48 hours ago which temporarily resolved the issue, but all new builds reverted to Expired again today within an hour (matching the BETA_CONTRACT_MISSING / backend state desync reported earlier in this thread). Feedback Assistant Ticket: FB25656884 (includes Team ID TJ9KJ6WV99 and all 3 numeric App IDs). Thanks in advance for routing this to the TestFlight / App Store Connect team!
Replies
0
Boosts
0
Views
89
Activity
5h
TestFlight unusable on new paid account: no invite emails, Beta App Review submission always fails
Hello, My Apple Developer Program membership is paid and active (individual account, enrolled 11 Nov 2026), but I cannot use TestFlight at all, and Developer Support has not replied. What works Builds upload and process fine (processing state VALID). Free and Paid Apps agreements, bank account, tax forms and DSA compliance are all "Active" in App Store Connect > Business. Export compliance, age rating, category, Beta App Review contact info, beta description, feedback email and privacy policy URL are all filled in. What does not work Internal testing: testers are added and stay in "Invited" status, but the invitation email never arrives (checked spam, tried iCloud and Gmail addresses, resent several times). External testing: submitting a build to Beta App Review always fails. On the App Store Connect website I get "There was an error processing your request. Please try again later." The App Store Connect API (POST /v1/betaAppReviewSubmissions) returns HTTP 422 ENTITY_UNPROCESSABLE, "Please try again later." Same result for different builds, the existing external group and a brand new group, over several days (13 attempts in total). A second app on the same account shows the same symptoms, so it looks account-level, not app-level. Example error IDs from the API: 5cbd887c-80d7-4dcf-bcea-94377c972ffb, d9761cf6-5584-413f-826d-017dd6a5029b, 97644394-7884-4ce6-bfdc-cc065c4a12d6, d8771b1e-4860-48ee-92bb-86e93161832a Support case 30000014824443 (Distribution / TestFlight): three messages since 14 Nov, no reply. Has anyone seen this on a newly enrolled account, and is there anything I can do on my side? If an Apple engineer can look at the error IDs above, I can share the app Apple ID and team ID privately. Thank you.
Replies
1
Boosts
0
Views
108
Activity
15h
TestFlight dead on new accounts (Oct-Nov 2026): no invite emails, Beta App Review 422 "Please try again later". Collecting all cases here
This thread collects every account with the fault below in one place, so Apple sees one issue across many accounts instead of many lonely threads. If you have it, please reply. What to include is at the end. The fault Builds upload and process fine. Then two things never work: No TestFlight invite email is ever sent. Every tester, internal or external, stays "Invited". Reinvite does nothing: POST /iris/v1/betaTesterInvitations returns 201 Created and no email arrives, not in spam either. A build cannot be submitted for Beta App Review. "There was an error processing your request. Please try again later." POST /iris/v1/betaAppReviewSubmissions returns 422 ENTITY_UNPROCESSABLE with only that sentence and no further reason. So internal testing is blocked by the missing emails and external testing by the refused review. Agreements, tax, banking and DSA are Active, Test Information and export compliance are complete, and nothing a developer can change makes a difference. The accounts reporting it are mostly new, enrolled around October 2026. My case Account enrolled 31 October 2026. Fault since 5 November 2026, every day. Region: Türkiye. No invite email reaches any of my six testers. Beta App Review submit returns the 422 every time. On 13 November I reset everything to rule out my side: removed every tester and both groups, expired the old builds, uploaded a fresh build, added everyone again. Nothing changed. The fresh build is VALID. Its internal state is IN_BETA_TESTING with "automatically notify testers" on, yet its record says the testers were not notified. Its external state is READY_FOR_BETA_SUBMISSION and the submit is refused. Feedback Assistant: FB25540791 (two HAR logs). Developer Support cases 30000005155573 and 30000005989992: only automatic receipts since 4 November, no human reply. Phone support shows as unavailable. Others reporting it https://developer.apple.com/forums/thread/856330 (@Hopeforge): internal invite emails never delivered, testers stay "Invited". Recreating groups, resending and new builds did not help. An App Store Connect Engineer replied there and asked for Feedback Assistant tickets with HAR logs. https://developer.apple.com/forums/thread/857012 (@Kirnuvirsta): tester stuck on "Invited" with no email, Beta App Review submit fails, same on a second app record. FB25399719, case open since 28 October. https://developer.apple.com/forums/thread/856896 (@medlzd, @ganderbite): new internal testers show "Invited" and never get the email, Resend Invite does nothing, on all apps. https://developer.apple.com/forums/thread/856592 (@EmlakBaseDev): Beta App Review submit returns 422 "Please try again later" on three apps since 24 October, build VALID and READY_FOR_BETA_SUBMISSION. https://developer.apple.com/forums/thread/854803 (@SefaAygun, @JanuaryTwelfth): adding a build to external testing fails with "try again later". https://developer.apple.com/forums/thread/854106 (@BWGTrading): new organization account, TestFlight stopped working for all apps on 27 October. If you have this too, please reply with When your account was enrolled, and since when the fault shows Which of the two you have: no invite emails, 422 on Beta App Review, or both Your country or region, to see whether it is tied to one Your Feedback Assistant number (FB...) and Developer Support case ID Anything Apple told you, and above all whether it got fixed, and how If you have not filed a Feedback Assistant ticket yet, please do: steps, a HAR log of the failing request, your App ID. The engineer in thread 856330 asked for exactly that. To Apple Could someone from the App Store Connect or TestFlight team tell us whether this is a known fault in how TestFlight is set up for newly enrolled accounts, and whether each account needs a change on your side? We are paying members who cannot use TestFlight at all, and our support cases stay unanswered for weeks. Thank you.
Replies
17
Boosts
8
Views
827
Activity
20h
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
154
Boosts
13
Views
12k
Activity
1d
TestFlight dead on new account: internal invites never sent, 422 ENTITY_UNPROCESSABLE on beta review
Since my first TestFlight upload on November 2, 2026, TestFlight does not work for my app at all. This looks like the same account-level issue many developers have reported since late October 2026. Region: Türkiye Account: individual, enrolled October 26, 2026; latest Program License Agreement accepted November 6 App ID: 6828238853, builds 1.0 (1) and 1.0 (2) Symptoms: Internal testers stay "Invited", the INVITES column stays empty and no invitation email is ever sent. Submitting a build for external beta review always fails: POST /iris/v1/betaAppReviewSubmissions returns 422 ENTITY_UNPROCESSABLE "There was an error processing your request. Please try again later." Error ID: a254e078-e9a9-44c4-be23-3d75d6d8daad API correlation key: 4IHT4ZPBDXIOSMH6J2GPZTDU5E Even saving "What to Test" notes for an internal build fails with "Validation Error". Already checked: Free Apps Agreement and DSA are active, Test Information, privacy policy, App Privacy, age rating and export compliance are complete, ITSAppUsesNonExemptEncryption = NO. A new build, reinvites and removing/re-adding testers did not help. Developer Support case 30000005085209 has been open since November 4. A reply dated November 17 shows on the case but the email never arrived. Could someone from the TestFlight team please check and re-provision the TestFlight setup for my account?
Replies
2
Boosts
0
Views
170
Activity
1d
TestFlight not working for new account: invitations never sent, Beta App Review submission returns 422
Problem 1: External Beta App Review submission always fails Submitting the build to an external group fails both in App Store Connect ("Submit for Review") and via the App Store Connect API (POST /v1/betaAppReviewSubmissions) with: 422 ENTITY_UNPROCESSABLE, "There was an error processing your request." / "Please try again later." No sub-code and no field is named. It has failed consistently for more than a day. Error IDs: 87d6bf69-3f70-485a-ae69-a3e3dc4f5acd 85377625-b7e8-45d2-a3ac-bc34f083e693 eb1396ca-8869-4a34-84b1-24f6dcbf0b65 (2026-11-20 12:57 UTC) Immediately before the last attempt, the build showed externalBuildState=READY_FOR_BETA_SUBMISSION, and there was no pending submission. Problem 2: Internal tester invitations are never emailed The build is IN_BETA_TESTING in the internal group. Testers stay "Invited", and no invitation email ever arrives. Resending the invitation via the API returns 201 Created (invitation ID b6a6d90c-607d-4ae4-9277-de79ca752130), but nothing is delivered. I checked the inbox and junk folders on icloud.com. The app does not appear in the TestFlight app on my iPhone. This also happened with builds 1 and 2. Already verified Free Apps Agreement: Active. The Paid Apps Agreement shows "Pending User Info"; the app has no paid content. Build 3 was uploaded with App Store Connect distribution (APP_STORE_ELIGIBLE); export compliance is declared in Info.plist (ITSAppUsesNonExemptEncryption = NO). Test Information, Beta App Review contact details, What to Test and age rating are complete. All 6 internal testers are active App Store Connect users. The Apple ID signed in to TestFlight is the same as my App Store Connect account. The device runs iOS 26.1 (minimum is 26.0). No open incident on Apple System Status. Several developers with new accounts report the same two symptoms on the Developer Forums (threads 857429, 856330, 856863). One case was resolved on Apple's side through Developer Support. Please check the TestFlight provisioning of my account and escalate to engineering if needed. I can provide screen recordings and HAR logs.
Replies
0
Boosts
0
Views
37
Activity
1d
TestFlight - 422 ENTITY_UNPROCESSABLE
Enrolled: 10 Nov 2026. First builds uploaded 11–12 Nov 2026, fault seen from the very first build. Internal testers stay "Invited", the invitation e-mail never arrives (Resend, removing/re-adding testers and new builds did not help). Other Apple e-mails reach the same addresses normally. Beta App Review submit always fails with "There was an error processing your request. Please try again later." — POST betaAppReviewSubmissions returns 422 ENTITY_UNPROCESSABLE, both in the web UI and through the App Store Connect API. No betaAppReviewSubmission is created. Builds are VALID, external state READY_FOR_BETA_SUBMISSION. Same result from the Account Holder's own session and from the Admin's session. What we checked / tried, none helped: All agreements accepted (Program License Agreement, Free Apps Active), DSA compliance completed. Test Information, Beta App Review Information, What to Test, export compliance all complete. New builds with new build numbers. A brand-new app record with a NEW bundle ID in the same team: exactly the same two symptoms. Two observations that may help others: Another newly enrolled individual team that we manage (same week, same Admin user, same CI pipeline, same Test Information) works normally: invites arrive, external submission goes to Waiting for Review. So it looks team-specific, not setup-specific. App Store submission is NOT blocked: the same build went to "Waiting for Review" for App Store review without problems. Only TestFlight is affected. Two Developer Support cases are open (Membership and Account), automated replies only so far. Following b2mode's update, I will also file under Distribution > TestFlight. Will report back here when it is resolved.
Replies
0
Boosts
1
Views
47
Activity
1d
Beta testers wanted: Starbit Dash, retro pixel space shooter (iPhone, iOS 17+)
Hi everyone! I’m looking for beta testers for Starbit Dash, a twin-stick space shooter for iPhone with pixel art and a handheld console look. 6 acts, 18 bosses with their own attack patterns, endless mode with up to 4 bosses at once Perks after every boss, 30 pilot levels, unlockable rockets No ads, no tracking, no account; works offline What I’d most like feedback on: Is Act 1 too easy, too hard or just right? Anything confusing in the menus or the workshop? Join the beta: Starbit Dash Testflight Feedback via TestFlight screenshot or as a reply here. Thanks!
Replies
0
Boosts
0
Views
35
Activity
1d
TestFlight external "Submit for Review" fails with "There was an error processing your request" (all apps, new and old)
Since about 17 November, adding a build to an external TestFlight group and pressing Submit for Review fails every time in App Store Connect with: "There was an error processing your request. Please try again later." What I've tried: Several different builds of one app (builds 1, 3, 4 and 5), uploaded with Xcode 27.2. Two different external groups. A brand-new app record with a new bundle ID. An older app on the same team that was set up before the problem started. It fails the same way. Declaring my DSA trader status, then retrying. What works: uploads, processing ("Ready to Submit"), and internal testing. External testing never gets as far as "Waiting for Review". The Apple Developer System Status page shows nothing about TestFlight or App Store Connect. I've had a support case open for several days with no reply yet. It looks like a team- or account-level fault, since it affects every app I try. Has anyone else seen this, or found a fix? I'd also be grateful if an Apple engineer could check this. Thanks.
Replies
2
Boosts
1
Views
95
Activity
1d
Looking for beta testers: Remolo, your Mac's screen on iPhone and iPad (iOS, iPadOS, macOS, watchOS)
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!
Replies
4
Boosts
0
Views
335
Activity
2d
SKPaymentQueue.default().storefront?.countryCode returns "USA" only in TestFlight
Hi everyone, I'm encountering an issue where the storefront country code returns "USA" unexpectedly in TestFlight builds, and I'd appreciate any insights from the community. Issue Description When executing SKPaymentQueue.default().storefront?.countryCode in our TestFlight builds, the property returns USA. However, we expect it to return JPN because both the Sandbox test user account and the Apple Account region configured on the device are set to Japan. Behavior Across Environments Xcode Debug & Ad Hoc Builds: Returns JPN as expected. TestFlight Builds: Returns USA unexpectedly. Related Threads I've noticed several threads reporting similar issues without a clear resolution: https://developer.apple.com/forums/thread/660817 https://developer.apple.com/forums/thread/794932 https://developer.apple.com/forums/thread/800078 https://developer.apple.com/forums/thread/814178 https://developer.apple.com/forums/thread/810860 Questions Is this USA value a known TestFlight/Sandbox-specific limitation or bug? Will production users in Japan correctly receive JPN (and see JPY prices) once the app is approved and published on the App Store? Is there any workaround or project configuration fix required on our side prior to App Store submission? Has anyone experienced this recently or confirmed the behavior in the production environment after release? Thanks!
Replies
3
Boosts
1
Views
668
Activity
2d
Cloudless AI - on-device AI for pictures, short films, sound and music (iPhone, iPad, Mac)
I'm an individual developer testing Cloudless AI, an app that makes pictures, short films (5 to 10 seconds), sound effects and music entirely on the device. There is no server and no account. TestFlight public link: https://testflight.apple.com/join/Y1gkZt8W Platforms: iOS, iPadOS, macOS Category: Photo & Video What to test First run: model download and preparation. Note how long it takes and whether anything fails. Pictures: people and faces, the cartoon and anime styles, and the photo tools (face fix, enlarge, erase, blur background, cut-out). Films from a description or a picture: does the film follow your description, and how warm does the device get? Sound and music from a description. Memory and heat on devices other than an iPhone 17 Pro or an M1 Pro Mac. That's all I've tested properly, so reports from older iPhones and iPads are especially welcome. Please tell me your device and iOS version, the time to the first result, and anything confusing or wrong. Feedback also goes through Settings > Help > Report a problem in the app (nothing is sent unless you press Send) or through the TestFlight app.
Replies
0
Boosts
0
Views
63
Activity
2d
App Replacement - How to test in TestFlight
Has anyone gotten the App Replacement dialog to show up when launching an app configured with the replacement bundle identifiers in TestFlight? Per the documentation is says app [re]placement can be tested via TestFlight. https://developer.apple.com/documentation/bundleresources/entitlements/com.apple.developer.superseded-application-identifiers I've tried these two scenarios and have not gotten the system prompt to appear yet, all testing done on iOS 27.2 or 27.3 beta 1/2. Scenario A: App 1 installed via TestFlight, bundle "abc" App 1 launched App 2 installed via TestFlight, bundle "def" --> replacement entitlement configured to replace "abc". Scenario B: App 1 installed via App Store, bundle "abc" App 1 launched App 2 installed via TestFlight, bundle "def" --> replacement entitlement configured to replace "abc". In neither scenario did the system present the modal for me to transfer data or delete the previously installed app. Are there minimum usage or filesystem requirements that need to be present in the original and replaced app? FB25559759 - TestFlight / App Replacement: App Replacement did not trigger as described by documentation when installing from TestFlight
Replies
0
Boosts
0
Views
57
Activity
3d
TestFlight external Beta App Review fails with HTTP 422 across multiple apps on the same developer team
Hi everyone, I’m unable to submit builds for external TestFlight testing across multiple iOS apps on the same Apple Developer team. The builds upload successfully, but clicking “Submit for Review” in App Store Connect fails before the build enters Beta App Review. Here’s one example I reproduced and captured in Chrome DevTools: App: Benny Wallet App Apple ID: 6834886147 iOS version and build: 0.3.1 (104) Build status: Ready to Submit Request: POST /iris/v1/betaAppReviewSubmissions Response: HTTP 422 ENTITY_UNPROCESSABLE Error message: “There was an error processing your request. Please try again later.” Both the Free Apps and Paid Apps agreements show as active. I reproduced the error with “Automatically notify testers” turned off as well. Other apps on the same team show the same submission error in the UI. This looks similar to the reports in https://developer.apple.com/forums/thread/857429. Has anyone with the same HTTP 422 across multiple apps managed to get external TestFlight submissions working again? If so, what fixed it? If someone from the App Store Connect or TestFlight team is able to look into this, could you check whether there’s an issue with our team’s beta distribution authorization or Beta Contract association? I’ve filed Feedback Assistant report FB25625640. I can provide the Apple request UUID and UTC timestamp through that report if needed. Thanks, Frank
Replies
0
Boosts
1
Views
55
Activity
3d
TestFlight installation returns 404 for one developer account; other accounts work
The error shown in TestFlight is: “The requested app is not available or doesn’t exist.” The HTTP 404 mentioned below is the historical install-service response, not the wording displayed to users. I am trying to resolve a TestFlight installation failure that appears specific to one developer account. None of the users we have tested can install our apps. What I have observed: Installation of build 964 returned HTTP 404 from the install service. The internal tester was assigned to the build, and the build was not expired. TestFlight apps from another organization install successfully on the same device. A newer build, 969, was marked ready on November 12, 2026. I have now tested it, and it also fails to install with the same error message as before. Account timeline: The account was migrated from individual to organization, with migration completed on October 23, 2026. The installation issue began after the migration request but before completion. I do not know whether the migration is related; I am including the timeline in case it helps narrow down the checks. Has anyone encountered this account-specific install-service 404? What should I check to distinguish a build or tester configuration issue from an account-side distribution issue? If this needs Apple investigation, which diagnostics would be most useful to provide privately? I found a potentially similar report at https://developer.apple.com/forums/thread/837330, but I do not have confirmation that it has the same cause.
Replies
1
Boosts
0
Views
73
Activity
3d
TestFlight broken for every app on my team: installs fail, no invitation emails, beta review submission returns 422 (case 30000010345074)
Hello. Since November 2, 2026, TestFlight has been unusable for all apps on my team (Team ID 8NNQY8P7EP), including apps that are live on the App Store : In the TestFlight app, Install always fails with "Could not install [app]. The requested app is not available or doesn’t exist", although the builds are listed. This happens on every app of the account. Tester invitation emails are no longer delivered, on any app. The API returns 201 for the invitation, but no email arrives. Removing and re-inviting a tester does not help. Submitting a build for external beta review fails with 422 ENTITY_UNPROCESSABLE "There was an error processing your request. Please try again later." (app 6830730952, build 5), both in App Store Connect and through the API. My membership and agreements are active. On November 2, I expired some builds, removed testers and deleted one unpublished app from the account; the problems started around that date. The same symptoms are reported in many other threads on this forum. Support case 30000010345074 has been open since November 9 without a reply. Could someone from Apple please check the TestFlight status of my account ? Thank you !
Replies
0
Boosts
0
Views
87
Activity
4d
TestFlight invitations not sent to any internal testers – account-level issue
Hello, I’m following up on case 30000013215244, opened 4 days ago, still without a response. TestFlight invitation emails are not being delivered to any internal tester on my account, including myself (Account Holder). The app does not appear in the TestFlight app for any of us. App name / Apple ID: Cosmine / 6825922062 Team ID: 5YFU7N787S Build 1.0.0 is processed and shows “Testing” in the internal group All testers are active App Store Connect users and are added to the internal group The Apple Account on each device matches the invited email Already tried: resending invitations, removing and re-adding testers, creating a new internal group, reinstalling TestFlight All agreements are active Since this affects multiple testers and not just one device or account, I believe this is an account-level issue on Apple’s side (possibly related to the beta contract). Could you please escalate this to the TestFlight team? Thank you.
Replies
0
Boosts
1
Views
85
Activity
5d
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
60
Boosts
8
Views
7.2k
Activity
5d