TestFlight Public Links are a great way to share beta versions of your apps with other members of the Apple Developer Program. With this new channel, you can share your TestFlight Public Links with the developer community, to gather valuable feedback on crucial elements, like technical implementation, user experience, design, and more. To maximize the benefits of posting TestFlight Public Links in the Developer Forums, here are some best practices to keep in mind: Provide details: Give comprehensive information about your app, like new features and test cases, and note specific areas where you seek feedback. The more detailed your post is, the better equipped the community will be to provide insight. Select platforms: Select the platforms that your beta app supports. Enter categories: Enter the App category you’ve selected or plan to select for your app on the App Store. Categories are critical to ensuring your post can be easily found by interested users. Stay connected with notifications: Enable web and push notifications so you’ll know when you receive feedback on your post. Note: The TestFlight app is still the most comprehensive way to gather feedback. This space is meant as a helpful secondary channel.

Hello, I am new for apple developer. I see the problem and I think apple show me very few error message and I do not know to start with it. I was created my app by python and build to .app then package it to pkg by the pkgbuild. I have problem to upload the pkg file to app store connect by transporter both CLI and GUI. when I try to upload it by GUI, I see this message. Cannot find the ITMSP file: (null). (11)` and when I upload my pkg by the CLI, I found more message but still cannot start with it as well. [2026-08-23 09:57:58 ICT] <main> DEBUG: Registered file for monitoring: /Users/xxxxxxxxx/.itmstransporter/temp/tx-xxxxxxxxx.pkg-swinfo.plist16166255377348903097.tmp with action CANCEL_ALL [2026-08-23 09:57:58 ICT] <main> DEBUG: Started file monitor for 1 file(s) [2026-08-23 09:57:58 ICT] <main> INFO: Starting upload for package b7ac46de-45fe-4fa6-b0f6-6fea35038d8f-tx-xxxxxxxxx.pkg-swinfo.plist16166255377348903097.tmp. [2026-08-23 09:57:58 ICT] <main> INFO: Computing total size of files to upload ... [2026-08-23 09:57:58 ICT] <main> DBG-X: adding file for % complete logging: tx-xxxxxxxxx.pkg-swinfo.plist16166255377348903097.tmp , size: 7704460 [2026-08-23 09:57:58 ICT] <main> DEBUG: Setting total size of files for upload to: 7704460 [2026-08-23 09:57:58 ICT] <main> INFO: Done computing total size of files to upload. [2026-08-23 09:57:58 ICT] <main> INFO: Starting checksum calculations for 1 file(s) using up to 1 thread(s)... [2026-08-23 09:57:58 ICT] <main> INFO: Checksum calculations are complete, elapsed time: 0 d 0h 0m 0s. [2026-08-23 09:57:58 ICT] <main> INFO: Creating reservations for build upload: b7ac46de-45fe-4fa6-b0f6-6fea35038d8f [2026-08-23 09:57:58 ICT] <main> DEBUG: creating upload file... [2026-08-23 09:57:58 ICT] <main> DEBUG: SMART-CLIENT: getCurrent(); using pinned data center = contentdelivery01.itunes.apple.com [2026-08-23 09:57:58 ICT] <main> INFO: Package upload progress: 0.00% completed [2026-08-23 09:57:58 ICT] <main> INFO: Transfer Metrics Summary: [2026-08-23 09:57:58 ICT] <main> INFO: bytes transmitted: 0 [2026-08-23 09:57:58 ICT] <main> INFO: tx-xxxxxxxxx.pkg-swinfo.plist16166255377348903097.tmp transfer metrics: [2026-08-23 09:57:58 ICT] <main> INFO: bytes transmitted: 0 [2026-08-23 09:57:58 ICT] <main> INFO: Starting checksum calculations for 1 file(s) using up to 1 thread(s)... [2026-08-23 09:57:58 ICT] <main> INFO: Checksum calculations are complete, elapsed time: 0 d 0h 0m 0s. [2026-08-23 09:57:58 ICT] <main> INFO: Creating reservations for build upload: b7ac46de-45fe-4fa6-b0f6-6fea35038d8f [2026-08-23 09:57:58 ICT] <main> DEBUG: creating upload file... [2026-08-23 09:57:58 ICT] <main> DEBUG: SMART-CLIENT: getCurrent(); using pinned data center = contentdelivery01.itunes.apple.com [2026-08-23 09:57:59 ICT] <main> DEBUG: Stopped file monitor [2026-08-23 09:57:59 ICT] <main> DEBUG: Transport HTTP failed after 0 bytes, trying next transport. Error: could not upload file: tx-xxxxxxxxx.pkg-swinfo.plist16166255377348903097.tmp [2026-08-23 09:57:59 ICT] <main> DEBUG: Upload phase transition: CLOSED -> INITIAL [2026-08-23 09:57:59 ICT] <main> ERROR: All transport types failed for file: tx-xxxxxxxxx.pkg-swinfo.plist16166255377348903097.tmp Package Summary: 1 package(s) were not uploaded because they had problems: /Users/xxxxxxxxx/xxxxxxxxx/../xxxxxxxxx_Image/xxxxxxxxx.pkg - Error Messages: All transport types failed for file: tx-xxxxxxxxx.pkg-swinfo.plist16166255377348903097.tmp [2026-08-23 09:57:59 ICT] <main> DBG-X: Returning 1 Not too sure if anyone ever see my issue and how you solved it?

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.

Hello, I’m having a recurring TestFlight issue. This is already the third time it has happened. All of my TestFlight builds are automatically marked as Expired, and I’m unable to submit a new processed build for External Testing. App Store Connect returns: HTTP 422 ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING Beta Contract is missing. My Developer Program membership and agreements are active, with no pending agreements. The issue happens directly in the App Store Connect website, with no third-party service involved. Has anyone else experienced this? It seems like a TestFlight backend / Beta Contract provisioning issue. I’ve already contacted Apple Support multiple times, but the problem keeps returning. Thanks.

App stuck in "Waiting for Review" for 3 days — anyone else? My app has been sitting in "Waiting for Review" status for 3 days now with no update. No rejection, no request for more info, nothing. Has anyone else run into this recently? Just trying to figure out if this is a known delay right now or something specific to my submission.

Hi everyone. I'd like to have your opinion on a new update that I have made for my xDesk app. particularly this new update enhance the sharing, creation of custom data sheet and can also record and transcribe what is being said during registration, can scan documents and... more. Really, I'd like to have your opinion. if you are interested the public TestFlight link is: https://testflight.apple.com/join/KathTdzq

Hello Apple Developer Community, I am experiencing a TestFlight issue with my iOS app and would appreciate any guidance. App Information: App ID: 6801854699 Bundle ID: az.idrak.liseyi App Version: 1.0.9 (14) Platform: iOS Team ID: W24294ZD96 Apple Developer Program membership: Active until December 11, 2026 Free Apps Agreement: Active Paid Apps Agreement: Active Issue: I uploaded build 1.0.9 (14) to App Store Connect using Codemagic. The build processes successfully and appears in the internal testing group. However, when an internal tester opens TestFlight and attempts to install the app, TestFlight displays: “The requested app is not available or doesn't exist.” At the same time, Codemagic reports the following API error: POST betaAppReviewSubmissions returned 422: Beta contract is missing for the app App Store Connect also previously displayed a message saying that I needed to renew my Apple Developer Program membership when attempting to create an external testing group. However, my membership is active until December 11, 2026, and all required agreements are active. Steps to reproduce: Upload build 1.0.9 (14) to App Store Connect using Codemagic. Wait for the build to finish processing. Add/select the build for TestFlight internal testing. Open TestFlight on an iPhone using an internal tester account. Attempt to install the app. TestFlight displays: “The requested app is not available or doesn't exist.” Codemagic reports: “Beta contract is missing for the app.” This issue appears to be related to a backend synchronization or Beta Contract problem. Apple Developer Support has already escalated this case to their technical team under case number 20000139248466. Has anyone experienced the same Beta Contract / TestFlight availability issue, or knows how this can be resolved? Thank you.

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

I keep on missing TestFlight users' screenshot and crash feedback because there are no notifications. Is there a setting somewhere that I am missing?

Hi everyone! I'm back again! 😄 A few months ago I posted here after submitting my first iOS app, after previously publishing it on Google Play. That experience was really helpful, so I'm hoping to get some advice from the community again. I've just submitted my new app, Vaqui, and it's currently Waiting for Review. Vaqui is an expense-sharing app for groups, mainly designed for trips. For example, three friends travel together and pay for different things: Pepe pays for the hotel. Sandra pays for groceries. Marcos pays for dinner. Everyone participates in different expenses. Vaqui calculates the resulting balances and suggests who should transfer money to whom. The app supports multiple currencies and stores the exchange rate used when an expense is recorded. The important part is that Vaqui does not process or hold money. It doesn't provide a wallet, banking account, payment processing, cards, or financial transactions. If someone owes another person money, Vaqui simply tells them something like: "Marcos owes Sandra $15,000." They make the actual transfer themselves using their bank or payment provider, outside Vaqui. The users can then mark the payment as made/received inside the app so the group knows what has already been settled. This made me wonder about something before the review starts: Would an app like Vaqui normally be considered a financial-services app by App Review, simply because it calculates debts/balances between users? Or is it generally treated as an expense-management / expense-sharing utility as long as it doesn't actually process, hold, or transfer money? I'm asking because I want to make sure I've understood the relevant App Review guidelines correctly rather than discovering during review that I've misunderstood something obvious. 😅 The current App Store Connect information is: App: Vaqui Bundle ID: mobi.todoapp.vaqui Apple ID: 6802352647 Status: Waiting for Review Platform: iOS / Flutter If anyone has submitted an app with similar functionality, I'd really appreciate hearing about your experience. Thanks! Greetings from Córdoba, Argentina 🇦🇷 And yes... once again I'm waiting for that little "In Review" notification. 🤞😂

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

Hello, I apologise for posting here. I know this forum is not a support channel, and I would not have posted if I had another way to reach App Review. Apple ID: 6759336435 Submission ID: 59a73f4a-e83b-4fa4-96dc-4c4b6a0ebcc4 Version reviewed: 1.0 (3) In review since: August 10, 2026 Rejection received: August 20, 2026 Our first submission was rejected under Guideline 4.3(a), on the basis that the app shares a similar binary, metadata or concept with apps previously submitted by a terminated Apple Developer Program account. We have no connection to any terminated developer account. RocketIO is not related to any other app, including the other apps on our own account. It is a separate product that we have been designing and writing for several years, on a different technical foundation: 114,817 lines of Dart across 139 files in Flutter, plus the Swift we wrote for the iOS tunnel host and the Network Extension, 187 tests, and 32 fully translated languages. We believe the binary match is a false positive. RocketIO statically links a publicly available open-source proxy core, as every app in this category does. That core is the largest part of the compiled binary, so any two apps linking the same open-source library will share a large amount of identical compiled code no matter how different their own source is — exactly as apps linking OpenVPN or WireGuard do. We cannot remove it, because it is the reason the app exists. RocketIO is also a bring-your-own-configuration client rather than a VPN service. It ships with an empty server list and does nothing until the user supplies a configuration for infrastructure they already own. We operate no servers, sell no subscriptions and carry no traffic. Among the protocols we have implemented are several that very few clients support on any platform, including DNSTT (DNS tunnelling), AnyTLS, ShadowQUIC, Mieru and Juicity, some of them added only recently. We replied in Resolution Center with all of this in detail, and asked which app or account the similarity was matched against, so that we could respond to the specific finding rather than guess. We are still waiting for a response. We have deliberately not resubmitted. We did not want to place another submission in the queue while this conversation is open, and we did not want to send back something that could reasonably be read as unchanged. We have been waiting since August 10, and we will be honest that it has been a difficult wait. We put years of work into this app and we have users who are looking forward to it, and at the moment we cannot tell them anything, because we do not know what specifically we are being asked to change. Could someone from App Review please reply to us there? We are glad to provide our source repository and its full commit history, to take a call at any time convenient to you in English, and to demonstrate the app live. Thank you for your time.

Hi, I'm running into an issue with TestFlight internal testing. Setup: App: Fito: Your Fitness Companion Bundle ID: com.yapizak.fitpet App Apple ID: 6804411842 Team ID: R562RBY637 Issue: A build was uploaded and assigned to our internal testing group ("beta"). When our tester tries to install the app from TestFlight, they get: "The requested app is not available or doesn't exist." When trying to submit a build (on the "What to Test" screen before Submit for Review), TestFlight shows: "Before you can use TestFlight to distribute beta builds of your app, you must renew your Apple Developer Program membership." However, my Membership Details page shows the membership as active, renewal date July 11, 2027, auto-renew ON. The Free Apps Agreement is also Active. I've already: Verified Pricing and Availability is set up (175 countries) Verified export compliance is answered (No) Verified code signing is correct (Automatic, App Store distribution) Uploaded a fresh build with a new build number Nothing has resolved it. This looks like might be a sync issue on Apple's side. Has anyone else run into this or found a workaround? Thanks in advance.

Hi everyone, I’m currently preparing the launch of Ritmo, a new iOS dating app for active people, and I’m looking for a few developers/users who would be willing to test it on TestFlight. I’d especially appreciate feedback on: Onboarding Profile discovery Likes and matching Messaging Notifications Overall UX and bugs It should only take around 10 minutes. TestFlight: https://testflight.apple.com/join/qGbXXeph Any feedback would be really helpful. Thanks!

Feedback: FB24471051 All TestFlight builds on my account fail to install. Team ID UJ83XWKNFQ, bundle ID com.adspike.pakmandidos. Device console shows: failureReason: Error Downloading Install Data, terminalReason: 1, fullError: (null), deltaError: (null), installDate: (null) I pulled the install log from a sysdiagnose taken immediately after a failed attempt. mobile_installation.log.0 shows successful App Store installs on the same device (com.google.Drive and net.whatsapp.WhatsApp, Aug 22 17:09). The log spans Aug 22 17:09 to Aug 23 08:56 and covers several failed TestFlight attempts, but contains no entries for my bundle ID at all. MobileInstallation is never invoked, so the build payload is not reaching the device. Ruled out: Two devices, two different Apple IDs Wi-Fi and cellular, after a network settings reset Freshly uploaded builds across multiple different apps on this account Apple Distribution certificate valid and freshly installed Membership active, agreements complete App availability set to all countries and regions No configuration changes preceded the issue Builds also appear to be expiring well before the 90-day limit. Separately, an App Store submission has been in Waiting for Review for over two weeks with no status change. Possibly the same root cause. Has anyone seen this resolved, and is there a channel that reaches the team responsible for TestFlight build delivery? Code-level support explicitly excludes App Store Connect issues.

Hello, I apologise for posting here. I know this forum is not a support channel, and I would not have posted if I had another way to reach App Review. Apple ID: 6799505220 Submission ID: 0a07b03d-56c9-45b4-b9b2-7ecbeb9ada0e Our submission was rejected under Guideline 4.3(a). We investigated and found the cause on our side: a server-side configuration fault meant the reviewed build was served the shared server pool used by our other apps, so it displayed a worldwide server list it was never designed to show. The finding was correct for that build. It was a defect, not the product. We have corrected it and verified the correction, and the corrected build is uploaded and attached to the version in App Store Connect. We have deliberately not pressed Submit for Review. We did not want to place another submission in the queue and take review time from other developers while this conversation is still open, and we did not want to send back something that could reasonably be read as unchanged. We would rather agree the right next step with App Review first. We replied in Resolution Center with all of this and are still waiting for a response. Could someone from App Review please reply to us there? Thank you for your time.

Hello, I am building an multiplatform app for iOS and macOS that uses CloudKit. I want give prerelease versions of my app to testers in my team. I want those builds to use the CloudKit development environment, as some of the schema is still experimental and subject to breaking changes. However, when I distribute my app via TestFlight, the iCloud container environment is automatically set to production, even though in my entitlements file I've set the iCloud container environment to development. I also tried the 'Release Testing' distribution method, but also with this option the container environment is overridden and set to production. Does anyone know how I can distribute a release build for internal testing that uses the CloudKit development environment?

To the Apple Review and Developer Support Teams, I am writing to request guidance and assistance regarding a persistent rejection my React Native application is facing under Guideline 2.1 - Performance (In-App Purchases). My app has been rejected multiple times with the following specific note: "The In-App Purchase products in the app still exhibited one or more bugs which create a poor user experience. Specifically, the subscription screen failed to load any subscription plans. Review the details and resources below to troubleshoot this issue." The screenshot provided by the review team shows a completely black screen where our paywall options are intended to populate, indicating that the product array is returning completely empty during the review process. The Dilemma: We are completely unable to reproduce this behavior on our end. Everything functions flawlessly within our TestFlight builds across multiple physical test devices and various sandbox tester accounts. On TestFlight, the paywall renders instantly, local pricing fetches immediately via SKProductsRequest, and test transactions process without a single error. Our Current Implementation & Verification: Product Status: All subscription products are explicitly marked as "Waiting for Review" in App Store Connect with one In-App product Rejected for not being attached with a bin but I've since submitted the app once again. All the subscriptions and the in-app product have been actively attached to this specific app submission version. Agreements: The Paid Apps Agreement is active, signed, and fully up to date within our Agreements, Tax, and Banking configurations. Identifiers: We have strictly verified that the hardcoded product identifiers in our React Native codebase match the App Store Connect product IDs exactly. Because this error only occurs within the App Review environment and never in TestFlight or local sandboxes, we are at a loss for how to debug or resolve this issue. Could the App Review team or the Developer Support technical team please clarify if there is a known environment mismatch, storefront routing discrepancy, or specific network configuration (such as IPv6 handling in the review sandbox) that would cause production-ready StoreKit products to return an empty array exclusively to the reviewer? Any direct guidance, logs, or steps on how we can successfully surface our plans to your review team would be deeply appreciated. Review Environment Submission ID: 5a35279c-1621-4972-b6c6-7c1fb202b2f0 Review date: May 20, 2026 Review Device: iPad Air 11-inch (M3) Version reviewed: 1.0.2 (8) Thank you for your time and assistance.

I built a mobile tower defense game solo in Godot and it's on TestFlight now. Free, no ads, no purchases, no account. The design bets on tower interactions rather than a large roster. Four towers, twelve permanent upgrades. Hex Totem does damage over time and increases damage taken, so it multiplies everything else in range. Amplifier Nodes buff nearby towers and can be built to stack with each other. Rapid Shooter can go rate-focused or mark targets so every other tower hits harder. The specific thing I want feedback on: my own testing could not distinguish three of the Rapid Shooter upgrades in terms of how far a run got. Either they are genuinely interchangeable and the design needs work, or my testing was too crude. I need people who will run the same map several times with different upgrade choices and tell me whether it felt different. At the end of each run there is a Send report button. One tap, sends the build and per-wave results, no personal information. A run takes about ten minutes. iPhone, iOS 16 or later. https://testflight.apple.com/join/XpQY7W3j Known gaps: no sound yet, and everything is drawn procedurally so there is no art.

Hello, Our entire developer account is currently blocked by a server-side issue. All TestFlight builds are failing to download or update across all test devices. Our internal logs indicate a backend contract mismatch/missing issue. Phone support holds are unresponsive, completely halting our development cycle. We have filed a formal engineering ticket under Feedback ID: FB24429619. Could a forum moderator or Apple engineer please pull this ticket and escalate it to the backend infrastructure team to re-provision our account? Thank you!

My Apple Developer Program membership was successfully renewed days ago. The Developer Account shows the membership as active, but App Store Connect/TestFlight still reports that my Developer Program membership needs to be renewed. message "Before you can use TestFlight to distribute beta builds of your app, you must renew your Apple Developer Program membership."