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

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;

Hi, I uploaded my app to TestFlight successfully, and the build shows as Validated and Testing. The tester invitation is also accepted. However, when I try to install it from TestFlight on my iPhone, I get: “Your app could not be installed. The requested application is unavailable or does not exist.” The app is version 1.0.0 (39), with a minimum iOS version of 15.0. The app is signed with an Apple Distribution certificate and an App Store provisioning profile. Has anyone experienced this issue or knows what might cause it?

Hi, I uploaded my app to TestFlight successfully, and the build shows as Validated and Testing. The tester invitation is also accepted. However, when I try to install it from TestFlight on my iPhone, I get: “App could not be installed. The requested application is unavailable or does not exist.” The app is version 1.0.0 (39), with a minimum iOS version of 15.0. The app is signed with an Apple Distribution certificate and an App Store provisioning profile. Has anyone experienced this issue or knows what might cause it?

Early Access via TestFlight: https://testflight.apple.com/join/Qsvxk5Mh What is it: https://leok7v.github.io/ChatOKF/ Open Source: https://github.com/leok7v/ChatOKF A capable AI assistant that lives on your iPhone and iPad. The model runs on your device's own chip, so nothing you type is uploaded and nothing is logged. Once a model is downloaded, ChatOKF works in airplane mode. No account. No sign-in. No subscription. No ads, no analytics, no telemetry. WHAT YOU CAN DO Ask anything: check the math on a loan, plan a week of dinners, untangle a confusing letter. Show it a picture: a photo of a menu, a street sign or a whiteboard, straight from your library. Some models also listen to audio and watch video, frame by frame. Hand it a document: a PDF, a Word file or a spreadsheet. It reads the tables inside and answers from the file, and one tap opens the page to check it. Watch it think: the stronger models reason before they answer. Read the reasoning, tap Quick Answer to cut it short, or switch thinking off for speed. Let it look things up: Wikipedia, today's headlines, the weather and web search are tools it can use, each behind its own switch. Keep going: it suggests a sensible next question; swipe right to ask it. Keep what it gives you: answers are typeset, tables and mathematics included. Search and rename your chats, share one as a PDF, and bring a deleted chat back within thirty days. Talk instead of typing: tap the microphone and speak, and have replies read aloud in one of eight voices made on your device. MEMORY YOU CAN READ Tell it to remember something and it writes a short note, and the chat says what it wrote. Later questions are checked against your notes first, whichever model is answering. Every note is listed under Memories, to read or to delete. One switch, Total Recall, turns it all off. WHERE YOUR WORDS GO Nowhere, unless it looks something up. With Wikipedia on, your question is matched to an article on your device and only that article is downloaded. With web access on, the model's search terms go to a search engine and the pages it chooses are fetched. Settings, Privacy says exactly what leaves your device for each one. PICK YOUR MODEL Several open models are offered, and the list shows only what your device can hold, so every one you see will run. Gemma 4 E2B and E4B: they see pictures, hear sound and watch video. Qwen3.5 2B and 4B: good with tools and longer answers. Ternary Bonsai 1.7B: small and fast, for devices with less memory. GOOD TO KNOW The first launch downloads a model, from about half a gigabyte to a few gigabytes. Use Wi-Fi; after that, no network is needed. Devices with more memory are offered stronger models, and newer chips answer faster. Answers are generated and can be wrong. Check anything that matters. ChatOKF is written in Swift on Metal, and its source is on GitHub. Models are provided by their authors under their own licenses, including the Gemma Terms of Use.

The UI only says "There was an error processing your request". The network response is: POST /iris/v1/betaAppReviewSubmissions → 422 ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING In Business → Agreements, all agreements are active and there is nothing left to accept. The build is processed and valid. Re-uploading, bumping the version and creating a new app version change nothing, so it looks like the account's beta contract flag didn't update after renewal. We contacted Developer Support over a week ago (Distribution → TestFlight) and haven't heard back. Could someone from Apple check the account's beta contract status or pass this to the App Store Connect team? Error ID: c9e61135-7a2f-4f52-bc39-bd3437d94440

I am trying to add testers to External Tester groups for a couple of our iOS apps and after adding them it shows "No Builds Available". This is despite the app being available to that External Tester group with other people having already installed the latest version of the app which is "Available" and not expired. Can someone please fix this? It is so frustrating the number of times I try and release apps to TestFlight and there's some issue blocking me, completely out of my control and I have to rely on someone at Apple fixing something on this terrible AppStoreConnect system.

Hi, I’m trying to test an independent watchOS app on an Apple Watch Series 6 Cellular that is set up for a child using Apple Watch For Your Kids (Family Setup). My current environment: Apple Watch Series 6 Cellular watchOS 26.6 The Watch is set up for a child using Apple Watch For Your Kids / Family Setup Xcode 26.6 Parent iPhone running iOS 27.0 Developer Mode is enabled on the parent iPhone The Family Setup Watch does not appear as a development device in Xcode/CoreDevice There is no Developer Mode option visible on the Family Setup Watch For comparison, I also have another Apple Watch used for normal development, and that Watch can be detected by the development environment. The issue appears specific to the child’s Family Setup Watch. I would like to understand the Apple-supported development and testing workflow for this configuration. Specifically: Is an Apple Watch set up using Apple Watch For Your Kids / Family Setup expected to be available as a direct Xcode development device? If direct Xcode deployment is not supported, can an independent watchOS app be installed and tested on a Family Setup Watch through TestFlight? If TestFlight is supported, what is the correct workflow for installing the beta on the child’s Family Setup Watch / child Apple Account? Is there another Apple-supported testing or distribution method developers should use for this scenario? I’m specifically asking about an independent watchOS app that can operate without the parent iPhone nearby, rather than a Watch app that depends on an iPhone companion app. I’d also appreciate clarification on the distinction between direct Xcode development deployment and TestFlight/App Store distribution for Apple Watch For Your Kids. Thank you.

Hi there, Recently I've created a beautiful drink logging app, Abvy. You log what you drink and it shows an estimate and a possible range of the alcohol in your system over the evening. It has plenty of disclaimers that the measurements are only estimates and to never use them for driving decisions Since 26 August I've had the same rejection six times: "marketed as a blood alcohol content calculator but does not have associated hardware... apps that rely solely on software... are not appropriate." Meanwhile Beta App Review approved all the builds submitted. I had an App Review appointment today. The rep read the same paragraph back to me and said to appeal, which I've done. It was really frustrating. The published 1.4 doesn't mention blood alcohol at all, and university and public-health apps with the same kind of estimate are on the store today (Stay in the Blue from the University of Michigan, Virtual Bar from the Foundation for Advancing Alcohol Responsibility). Not to mention dozens of other, apps who do the exact same thing but are approved. Has anyone actually got past this on the App Store side? What changed for you? What can I do to fix this? Really care about Abvy and think it's an amazing app.

SUMMARY TestFlight installation and external beta review submission are blocked for ITNRY. External submission returns ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING through both the App Store Connect website and the public App Store Connect API. Apple Developer Support case: 102968975728 Submitted: 19 September 2026 I have not yet received a response. APP AND BUILD DETAILS App: ITNRY: Private Trip Planner App Store Connect app ID: 6747810116 Bundle ID: com.c0defr1ft.ITNRY Version 5.5, build 1: Build ID: ace0e146-a828-49cd-8773-351f12dfc4b0 buildAudienceType: APP_STORE_ELIGIBLE processingState: VALID expired: false Version 5.5, build 2: Build ID: 4cb01458-8df0-44f5-810c-5a9769a2980d buildAudienceType: INTERNAL_ONLY processingState: VALID expired: false The external review submission described below uses build 1, NOT the internal-only build 2. STEPS TO REPRODUCE — APP STORE CONNECT Open ITNRY → TestFlight. Add version 5.5, build 1 to an external testing group. Complete the requested test information. Select Submit for Review. Actual result: “There was an error processing your request. Please try again later.” The failed network response contains: HTTP 422 ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING “Beta contract is missing for the app.” STEPS TO REPRODUCE — PUBLIC API Send an authenticated request to: POST https://api.appstoreconnect.apple.com/v1/betaAppReviewSubmissions Request body: { "data": { "type": "betaAppReviewSubmissions", "relationships": { "build": { "data": { "type": "builds", "id": "ace0e146-a828-49cd-8773-351f12dfc4b0" } } } } } Actual response: HTTP 422 { "errors": [ { "id": "d916bbd9-4cff-4a05-8f0c-7432ec8db5d3", "status": "422", "code": "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title": "Beta contract is missing for the app.", "detail": "Beta Contract is missing." } ] } Request ID: EYMVAZWCULILULIFKLQDUQ5DXI Timestamp: 19 September 2026, 17:32:43 UTC ADDITIONAL SYMPTOM — INTERNAL TESTFLIGHT The build is visible in TestFlight, but installation fails with: “The requested app is not available or doesn’t exist.” The iPhone’s Media & Purchases account matches the account assigned as an internal tester. TestFlight has also displayed an old email address previously associated with the same Apple Account. It is unclear whether this is related to the contract error. DIAGNOSTIC CHECKS ALREADY COMPLETED GET /v1/apps/6747810116/betaLicenseAgreement returns HTTP 200 and the following betaLicenseAgreements resource: 8289bafa-8347-4a7a-a2b4-86b580758220 Listing betaLicenseAgreements filtered by this app also returns that resource. Its agreementText was initially empty. As a troubleshooting attempt, I successfully populated it through the API and verified that the change persisted. External submission still returned the identical BETA_CONTRACT_MISSING error afterward. This establishes that the per-app betaLicenseAgreement resource exists. It does not establish whether that resource is the contract referenced by the submission error. EXPECTED RESULT An authorized internal tester should be able to install the assigned build. An eligible external build should submit for beta review, or App Store Connect should identify a specific outstanding requirement and provide an actionable way to resolve it. IMPACT AND REQUEST The issue blocks TestFlight installation and external beta review submission. Please investigate the contract validation/provisioning state for this app/account, identify which contract is reported missing, and advise whether any developer action is required. Please also determine whether the internal installation failure shares the same cause. Please link this report to Developer Support case 102968975728.

We recently completed an app transfer between two Apple Developer Program teams. Before releasing the first post-transfer version, we need to verify the update behavior from several specific historical versions signed by the previous team. Our main question is not limited to TestFlight: we would like to know Apple's recommended and supported method for reproducing this update path. Could you clarify the following? What is Apple's recommended and supported method for testing an update from a specific pre-transfer version to the first post-transfer release? Can an archived Ad Hoc IPA signed by the previous team be used as the starting version for this test? Can that IPA be updated by a post-transfer TestFlight, Development, or Ad Hoc build signed by the recipient team? Which of these methods most accurately reproduces an App Store update after an app transfer? For a manual Development or Ad Hoc update, is the previous-application-identifiers entitlement required? If it is required, how should the recipient team request a provisioning profile that authorizes this entitlement? Thank you.

Hi, Since mid-September 2026 TestFlight is completely blocked for my account, even though my app is live on the App Store and all agreements are active. Symptoms No tester (internal or external) can install any build. TestFlight shows: "Could not install Beavo. The requested app is not available or doesn't exist." A newly added internal tester sees "No Builds Available" in App Store Connect. Submitting any build to Beta App Review fails with HTTP 422: { "errors" : [ { "status" : "422", "code" : "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title" : "Beta contract is missing for the app.", "detail" : "Beta Contract is missing." } ] } Request UUID: 911b4c7a-1c7f-5b75-5c49-bcf26292fb18 (24 Sep 2026, 16:16 GMT) What I've verified Paid Apps Agreement: Active (Jun 2026 – Jun 2027) Free Apps Agreement: Active (regenerated Aug 19, 2026) Bank account, W-9 tax form and DSA compliance: Active I'm the Account Holder / Admin Builds (1.4.0 (13) through 1.5.0 (20)) are VALID, not expired, min iOS 26.0 ITSAppUsesNonExemptEncryption = NO is in Info.plist (no Missing Compliance) Test Information complete (description, feedback email, marketing and privacy policy URLs, Beta App Review contact) The last builds approved for external testing were in July 2026; nothing since then can be submitted This looks like the same backend issue reported in threads 814565 and 815885, where the Beta Contract entity was not re-provisioned after the agreements were regenerated, and it was fixed by an Apple engineer manually. App details App: Beavo – Apple ID 6781859321 Bundle ID: com.invntio.beavo Team ID: P4C48NFAHR I've also opened a case with Developer Support. Could someone from Apple please re-provision the Beta Contract for this account/app? Thanks!

I see different storefronts in StoreKit product queries and Apple’s purchase sheet when testing through TestFlight. Xcode-installed builds work normally. iPhone — iOS 26.6 (23G71), US Media & Purchases account Both StoreKit 1 and StoreKit 2 return CHN/CNY. The app displays CNY 128 for a non-consumable, but Apple’s sandbox purchase sheet shows USD 29.99 for the same product. This reproduces in a standalone 177-line Swift sample using Product.displayPrice directly, with no third-party dependencies, currency conversion, or local .storekit configuration. Reloading products and signing out of the sandbox account did not resolve it. Mac Catalyst — macOS 26.3 (25D125), China purchase account The original TestFlight app returns USA/USD. Purchasing shows “Account Not In This Store” and asks to switch to China, although the purchase account is already set to China. The Mac symptom has not yet been verified in the standalone sample. Reproduction on the affected iPhone: install via TestFlight, load products and log Storefront.current plus the SK1 storefront, open the purchase sheet for the same product, then compare currencies. No completed purchase is needed. Built with Xcode 26.1 (17B55). Has anyone found a workaround for this TestFlight-only mismatch? Should the app handle storefront updates differently, and which additional diagnostics would help distinguish a device/account-session issue from a StoreKit service issue? Feedback: FB24873070. A focused sample and diagnostic evidence are prepared for Apple Developer Technical Support. Reproduction on other devices/accounts is not yet confirmed.