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.

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

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

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

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!

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.

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

Hello, We would appreciate some guidance regarding an unexpected StoreKit currency result in a TestFlight build. Our iPhone language and region are both set to France. The Sandbox tester is also configured for France, and our subscription products have French availability and pricing configured in App Store Connect. In the TestFlight build we diagnosed, StoreKit reports the current storefront as France with EUR: storefront=FRA/143442/EUR However, all 10 subscription products are returned with USD product metadata: products=10/10 formatCurrencies=USD localeCurrencies=USD error=NONE Example: formatCurrency=USD locale=fr_US_currency_USD localeCurrency=USD display=1,99 $US price=1.99 We first observed this through Flutter's in_app_purchase integration. To determine whether the Flutter plugin was involved, we added a native StoreKit 2 diagnostic to the same TestFlight build. The native result was identical: receipt=sandboxReceipt storefront before=FRA/143442/EUR storefront after=FRA/143442/EUR products=10/10 formatCurrencies=USD localeCurrencies=USD error=NONE The issue appears specific to the TestFlight distribution. When the application is installed directly from the development computer, prices are returned in euros on the same device. We also tested with the regular Media & Purchases account signed out and a French Sandbox tester connected. Once the products loaded successfully, StoreKit still returned USD metadata. In another configuration, the application displayed the USD price while Apple's purchase sheet displayed the price in euros. We are using the price and formatting information returned directly by StoreKit. We do not want to infer the currency from the device region or perform a client-side currency conversion, because StoreKit should remain the authoritative source. Could you please help us understand: Is it expected for Storefront.current to report FRA/EUR while Product.priceFormatStyle.currencyCode, its locale currency, and Product.displayPrice use USD? Could a TestFlight or App Store Connect configuration cause product metadata to use a different currency from the current storefront? Is there another account, availability, pricing or distribution setting that we should verify? Is there a recommended way to refresh or invalidate the product metadata used by a TestFlight installation? We have already filed Feedback Assistant report FB24723329, which is currently under investigation. Thank you very much for any clarification or additional diagnostic steps you can suggest.

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

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

Hi, I'm a new Apple Developer program member and over about a 10-day period, I have been blocked from beta testing my app. I have been getting repeated 422's about a TestFlight Beta contract not attached to app 6812131455 . I submitted a Feedback Assistant ticket, FB24795679, where an engineer replied and said things were unblocked. I believe that I was able to get one more build uploaded after that but then the problem recurred and completely blocked me from sharing the TestFlight External beta link with new testers. I am uploading using the Transporter App and then trying to attach in Appstore Connect. I emailed Apple Developer support and they sent me only basic information about what 4xx HTTP status codes were, so I followed up via phone to Developer Support under ticket 102964195981. I've been calling over the past 3 days and a Senior Advisor has not picked up the ticket yet. Diagnostic information is below, including a sanitized HAR file. The error is reproducible, even with new builds, even with going through and confirming all requested data input fields are filled out and agreements are signed (to the best of my knowledge). I am developing an ad-free, free app with a focus on accessibility for the visually impaired. Can someone help me find a durable solution here? Much appreciated--I see others have had this issue. Happy to capture further debug logs to assist in a fix. captured_at_utc source build_number method url http_status error_code error_id x-apple-jingle-correlation-key x-apple-request-uuid x-responding-instance 2026-09-24T15:07:48.547415+00:00 live 116 POST /iris/v1/betaAppReviewSubmissions 422 ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING 7ef85ee6-412e-4535-b8f7-16cb8da406c8 5QSUAQZ4MOELPIGMJXUJD4UBP4 ec254043-3c63-88b7-a0cc-4de891f2817f ac-gateway-api:ac-gateway-api-main-5d674cb558-bp79n:ac-gateway-api-main-5d674cb558-bp79n:-1::::prod failures-422.md failures.jsonl failures.md session.sanitized.har

Hello, Our team is completely blocked from distributing builds via TestFlight due to the following backend API error: { "errors" : [ { "status" : "422", "code" : "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title" : "Beta contract is missing for the app.", "detail" : "Beta Contract is missing." } ] } Account & App Details: • App ID: 6817838147 • Existing Case IDs: 102986964055, 102986683221 • Agreements, Tax, and Banking: All Active and signed This appears to be a known backend desync where the TestFlight Beta contract is detached from our account/app. Could an Apple engineer or moderator please help escalate this to internal App Store Connect engineering to re-provision/re-attach our TestFlight beta contract? Thank you.

My company has sent us the "You're invited to join a development team." invite email for app testing. Clicking it leads to this page: "Sign in to accept your invitation You have been invited to join a team in the Apple Developer Program. As a member, you'll have access to resources, such as beta software and App Store Connect, for creating and distributing apps for Apple platforms." Clicking "Sign in with Apple Account", however, simply leads back to/refreshes the same page. There appears to be no way out of this loop. How do I accept this invite?

To learn best practices for before and after submitting your app for review, visit App Review Help.

not able to redeem the invite in TestFlight receiving below error The apple account you are currently signed with does not matching the one which is associated to this invitation you can sign in to testflight with the original apple account or request new invitation from developer

Hi everyone, I’m unable to select my developer team or upload my app to App Store Connect from Swift Playgrounds on my iPad. Both of these actions produce the same error: Open the app project → Team & Bundle Identifier → Team. Select Upload to App Store Connect. The error reads: “Failed to Fetch Teams Your session has expired. Please log in.” No team appears for me to select, so I cannot proceed with uploading the app. My account status: Apple Developer Program membership is active. Paid Apps Agreement is Active. Bank account is Active. I can sign in to App Store Connect through a browser. Activating the Paid Apps Agreement and banking information did not resolve the error. I reported this to Apple Developer Support on September 15 and provided a screen recording showing both failures. A Senior Advisor has now recommended asking in this forum. Has anyone encountered this exact error and resolved it? Is there a specific way to refresh the developer-account session used by Swift Playgrounds, or any diagnostic information I can collect to identify the cause? Thank you.

Hello, We are troubleshooting product discovery for three consumable In-App Purchases in our first iOS game, ION RUSH. All three remain unavailable in TestFlight. Environment and result: Physical iPhone 13, iOS 27.0.1 (24A446). App version 1.0 (80), installed through TestFlight. Direct native StoreKit 2; no RevenueCat or other purchase SDK. Product.products(for:) returns zero products before application filtering, without throwing an error. Earlier independent development-build diagnostics also returned zero products for batch and individual StoreKit 2 requests; SKProductsRequest reported all three identifiers as invalid. Checks completed: Product IDs exactly match App Store Connect: nova_pack_5, nova_pack_15, nova_pack_40. The explicit bundle identifier matches the app record and code; In-App Purchase is enabled for the App ID. All three consumables show Ready for Review, have prices and localizations, and are available in all 175 configured territories, including the US. Developer membership, Paid Apps Agreement, bank account and tax forms are active. The Account Holder checked the Developer account for outstanding agreement signatures; none were visible. The Developer Program agreement was accepted September 29. Tax forms were submitted October 3 and now show Active. The financial setup was only recently completed, so delayed activation remains a possibility. The release scheme has no local StoreKit Configuration override. TestFlight reinstallation, device restart and repeated product refreshes did not restore the products. A re-export of the exact build 80 archive with the original App Store Connect signing settings selected an explicit App Store profile with beta-reports-active=true and get-task-allow=false. This checks the signing configuration; the original uploaded IPA was not available for direct inspection. Selected storekitd messages from October 4, 2026 (UTC+3): 09:59:22.963356 Requesting Media API product batch ["nova_pack_15", "nova_pack_40", "nova_pack_5"] 09:59:22.990339 summary for task success {transaction_duration_ms=1, response_status=200, cache_hit=true} 09:59:22.991595 Ignoring empty product response The request targets amp-api.sandbox.apple.com/v1/catalog/us/in-app-purchasables with the correct bundle and product IDs. Its account mediaType is com.apple.AppleMediaServices.accountmediatype.appstore.beta. A second request one second later produced the same HTTP status, cache flag and empty-product message. We did not capture the raw HTTP response body. Local StoreKit configuration tests work, but we understand this does not validate the live Sandbox catalog. We also understand that prior IAP review approval is not required for Sandbox testing. Questions: What additional developer-side check would distinguish incomplete account activation, product configuration or cached catalog state in this situation? Has anyone resolved this after completing agreements/banking/tax, especially when the products were created before financial activation? What exact action or elapsed time resolved it? If all TN3186 checks pass, what evidence and official escalation route should we use to request investigation of the app-to-product catalog association? Related reports: https://developer.apple.com/forums/thread/849165 (same storekitd messages, but after membership lapse/renewal; our situation differs) https://developer.apple.com/forums/thread/844545 (zero StoreKit 2 products and invalid StoreKit 1 identifiers after TN3186 checks) We can provide further redacted diagnostics and account details privately to Apple. Thank you.

Internal TestFlight testers have to be App Store Connect team members with a role, but none of the roles fits someone whose only job is installing and testing builds. A QA tester ends up with Marketing, Customer Support, Sales or Developer, and each one gives access they don't need: reports, replying to reviews, or managing builds and certificates. External testing avoids that, but every build then goes through Beta App Review first. For a small team testing daily builds, that delay defeats the point. A "Tester" role would fix it: internal TestFlight access to the selected apps, and nothing else (no metadata, reports, reviews, pricing or certificates). I've filed this as FB25053990. If you want this too, please file your own feedback and mention that number. Duplicates are how Apple gauges demand.

Hi friends, Since yesterday, I'm not able to download any of my apps from TestFlight (while I can for others developers). I'm searching since 2 days now about the reason and I think I've tried everything, so I'm asking if you might have an idea... It occured after adding subscriptions to one of my apps, then I did all of these: Check all contracts on my apple developer account Verify my apple ID in internal testers Install / Uninstall TestFlight app Remove / Re-add myself as tester Try new builds My apps are listed on the Apple Store and not removed from Sales. Did I miss something? The error is mysterious... I also contacted Apple, I'm waiting for their answer. Thank you 🙏

Desde 16 de setembro de 2026, o TestFlight parou de funcionar para o nosso aplicativo e nada do que fazemos resolve o problema. Parece ser o mesmo problema com o contrato beta descrito nos tópicos 814565 e 821498. Aplicativo apploja001: ID Apple 6769057506, ID do pacote com.grupolb.apploja Versão 1.4.3, O que aconteceu Em 16 de setembro de 2026, todos nossos apps expiraram no mesmo segundo. Ninguém da nossa equipe as expirou. As versões 1.4.2 e 1.4.1 ainda estavam validas e foram expiradas. Desde então, nenhum testador consegue instalar nenhuma versão, interna ou externa. As versões 1.4.9 e 1.4.7 são processadas como válidas e estão disponíveis para nosso grupo interno, mas ao clicar em Instalar no TestFlight, aparece a mensagem: "Não foi possível instalar o apploja. O aplicativo solicitado não está disponível ou não existe." Todos os contratos relacionados à área comercial estão ativos, não há pendências e a associação está ativa. As informações do teste (descrição, e-mail para feedback, contato para revisão) e o contrato de licença beta foram preenchidos. A conformidade com as normas de exportação está definida (criptografia não isenta não está ativada). As novas compilações falham da mesma maneira. Apagar o aplicativo do dispositivo antes de instalar resulta no mesmo erro. O sistema de verificação de disponibilidade da Apple não indica nenhuma interrupção. Tenho o caso Nº do caso: 102965543896 aberto desde 16 de setembro de 2026 sem retorno. Alguém da equipe de suporte poderia verificar meu caso;