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.

Our iOS app uploads successfully to App Store Connect and appears in TestFlight, but it crashes immediately on launch. App name: Axioma Pay Bundle ID: uk.co.axiomapay.app Distribution: TestFlight Framework: Expo / React Native Device tested: iPad via TestFlight The app installs, the icon appears, but tapping Open causes an immediate crash. One earlier build displayed this runtime message: Cannot read property 'ErrorBoundary' of undefined Crash logs show the app aborting on the React Native ExceptionsManagerQueue with SIGABRT / EXC_CRASH. We do not currently have a focused minimal Xcode sample project because this is an Expo/EAS React Native production build. We can provide .ips crash logs and App Store Connect/TestFlight build details. Can Apple help confirm whether this crash appears to be caused by: App Store/TestFlight processing, provisioning/signing/entitlements, an iOS runtime issue, or an app-side React Native JavaScript startup exception? Latest TestFlight build crashes immediately after launch.

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.

Across two completely separate App IDs under the same Apple Developer Team, calling registerForRemoteNotifications() (via a standard push-notification plugin wrapping this exact API) resolves successfully — but afterward neither application(:didRegisterForRemoteNotificationsWithDeviceToken:) nor application(:didFailToRegisterForRemoteNotificationsWithError:) is ever called. No token, no error. Registration just stalls permanently. Environment Xcode 26.4.1 Distribution: TestFlight (App Store distribution profile → production APNs environment) iOS on all test devices: current release The key finding This isn't specific to one app. I reproduced the identical failure on: Our primary app's App ID, which has existed for a while and had Push Notifications enabled after initial creation. A brand-new, throwaway App ID created from scratch specifically to test this, with Push Notifications capability checked at creation time (no toggling after the fact, no history at all). Both show the exact same symptom: register() resolves, then silence — no callback of either kind, ever. Since this reproduces identically on an App ID with zero prior history, it rules out anything specific to one app's configuration or App Store Connect record, and points at something at the Team level with APNs backend authorization. What I've ruled out Entitlements/provisioning are correct and matching, verified via direct inspection of the signed binary: codesign -d --entitlements :- MyApp.app and the provisioning profile's own entitlements: security cms -D -i MyApp.app/embedded.mobileprovision | plutil -extract Entitlements xml1 -o - - Both show identical, correct values — aps-environment: production, correct application-identifier, correct team-identifier. Reproduced identically across: 2 separate App IDs (one long-standing, one brand new) 2 different physical iPhones 2 different WiFi networks 2 different accounts/user sessions within the app Already tried with no change in behavior: Enabling Push Notifications after initial App ID creation, vs. checking it at creation time on the fresh App ID Toggling the capability off/on and regenerating the provisioning profile Generating multiple fresh App Store distribution profiles Confirmed the Distribution certificate referenced is correct and valid Client code confirmed correct via instrumented logging at every step (permission check → permission request → listener attachment → register() call). Every step up to and including register() resolving completes exactly as expected. The stall is strictly after that point, entirely on the OS/APNs side. What I'm trying to determine Given this reproduces on a completely fresh App ID with no history, I believe this points at something about how APNs backend authorization is provisioned for this Developer Team as a whole, rather than any individual App ID's configuration. Has anyone seen this exact symptom — registration call succeeding but zero callback of either kind — and found a resolution that wasn't visible from anything in the Developer Portal or Xcode? Filed as Apple Developer Support case 20000117948923 — happy to share any additional diagnostics.

所请求的app不可用或者不存在

I am looking for help diagnosing a Sign in with Apple failure that occurs after Face ID and before a credential is returned. Environment iPhone 15 Pro iOS 26.2 Xcode 26.3 TestFlight distribution builds Team ID 42U……D944 Bundle IDs com.vybers.vybers-ios com.vybers.vybers Reproduction Install the app from TestFlight. Tap Sign in with Apple. Complete Face ID. Face ID succeeds but the authorization sheet reports that registration could not be completed. The app receives no ASAuthorizationAppleIDCredential and no identityToken. The same behavior occurs Across multiple builds. On multiple physical devices. With multiple Apple IDs. In both Bundle IDs belonging to the same team. In Apple's official Juice sample app using the official Sign in with Apple flow. Control experiment The same iPhone successfully signs in with Apple in a newly downloaded unrelated App Store app. The relevant device log captured immediately after the failure includes Apple server response HTTP 200 AppleIDAuthSupport setError 2M2 missing bad password SRP authentication with server failed AKRemoteViewController did complete with authorization null AKAuthenticationServerError Code=-24000 The “bad password” text is confusing but the Apple ID works in unrelated apps and the failure happens after successful Face ID. The application server is never contacted because no credential or identityToken is produced. Could this be caused by a team-scoped Sign in with Apple/AuthKit registration or synchronization problem rather than by the client implementation or server-side token verification In particular I would appreciate guidance on Checking the Sign in with Apple registration for the team. Checking whether multiple client IDs in one team can become stale or out of sync. Whether an individual Developer Program membership changes any requirement for this flow. Which diagnostic information Apple needs to investigate the AuthKit backend response. I can provide the full Team ID build details signing entitlements and a sysdiagnose through a private support case.

Im trying to add my build for review yet there is no upload option listed. does anyone have any suggestions or experience with this if so what did you do to res this proble?

Hi everyone, We've been stuck on this issue for several days and would really appreciate any guidance from anyone who has encountered this before. Issue Our app uploads successfully to App Store Connect, appears in TestFlight, and the build status is Ready for Internal Testing. However, every internal tester receives the following error when trying to install the app through TestFlight: Could not install . The requested app is not available or doesn't exist. Environment Apple Developer Program: Individual Distribution: Internal TestFlight Framework: React Native (Expo SDK) Build Service: Expo EAS Build Submission: Expo EAS Submit Platform: iOS What we've already verified The app builds successfully. The IPA is signed successfully. Build upload to App Store Connect succeeds. Build processing completes successfully. The build is assigned to an Internal Testing group. Internal testers have accepted the invitation. The bundle identifier is correct. Distribution certificate and provisioning profile are valid. We generated fresh builds and submitted them again. We recreated the App Store Connect app and submitted a new build. We also regenerated signing credentials where applicable. The issue persists across multiple builds. Additional Information During eas build, Apple successfully authenticates, registers the bundle identifier, creates the distribution certificate and provisioning profile, and the build completes without errors. eas submit also completes successfully, and the build appears in TestFlight. The failure only occurs when attempting to install the app from the TestFlight app. Error Could not install . The requested app is not available or doesn't exist. Has anyone experienced this issue recently? Is this likely a TestFlight/App Store Connect backend issue, or is there any App Store Connect configuration that we may have overlooked? And this is our active case id for the support: 102930164003 Any suggestions would be greatly appreciated. Thank you!

My TestFlight build has been in Waiting for Review since June 27, 2026 for more than a month. It was submitted for Beta App Review to enable public testing for external testers. Submission ID: f83d8d76-b239-48a8-8776-e93f4d03d5df Could someone please check whether the submission is stuck or if any additional action is required from my side? Thank you.

Hi, is anyone else having this issue? My new iOS builds finished processing successfully, but they only show “Expires in 90 days” and I can’t select them for internal or external testing. Export compliance is already completed, and I’ve also tried creating a new group, uploading another build, and refreshing App Store Connect, but nothing changed. Internal testing is still stuck on the previous build as well. Is this a current TestFlight/App Store Connect issue?

I see the status of the build as Complete in TestFlight and I have made an internal group but I can't find the button to add a new build to the group. Where is the button for that?

I'm stuck on what looks like a backend / account-level TestFlight issue and want to ask if anyone has seen the same pattern. Symptoms (reproduced across three consecutive builds) App Store Connect ingests and processes each build successfully; it shows as "Testing" in TestFlight with no compliance warnings. Internal TestFlight install fails instantly on every tester device with: ▎ "The requested app is not available or does not exist." Device console (itunesstored) at install time: FAILED: TFBundleInstallation serverFailureReason="Error Downloading Install Data" userFailureReason="Requested app not available or does not exist" buildGroup=(null) phase=Failed previousPhaseDescription=ProcessingInstallInitiateResponse serverCode 200 Submitting the same build for external Beta App Review returns: 422 ENTITY_UNPROCESSABLE code: BETA_CONTRACT_MISSING buildGroup=(null) for builds that visibly show as "Testing", plus a persistent BETA_CONTRACT_MISSING, suggests the beta-contract / build-group record for the app is missing or corrupted on the backend. Already verified clean on the developer side Distribution certificate and provisioning profile valid; entitlements match the binary; codesign --verify --deep --strict passes. Free and Paid Apps Agreements both Active; no pending tasks (Banking, Tax complete). App Information, Pricing & Availability, Age Rating, Content Rights, Test Information all complete; build page shows no warnings. Reproduced with multiple testers on multiple iOS 17+ devices, in a fresh internal testing group, after device-side cleanup (sign-out / reinstall TestFlight). Re-uploading a fresh build does not clear it — so it is not bound to a specific binary. Questions Has anyone seen Error Downloading Install Data + buildGroup=(null) + BETA_CONTRACT_MISSING together on a single app? How did you resolve it? 2. Why does ProcessingInstallInitiateResponse return serverCode 200 while still failing with "app not available", for a build that shows as "Testing"? 3. Is there a documented path to request that engineering regenerate a corrupted beta-contract / build-group record, beyond a standard support case? Any pointers appreciated — happy to share device logs / sysdiagnose if useful.

Hi, I'm completely blocked from TestFlight. Every attempt returns: "status": "422", "code": "BETA_CONTRACT_MISSING", "title": "Beta contract is missing for the app." This is an older account that has used TestFlight fine before. Nothing changed on my end, no account changes, no agreement updates. What I've already checked: Business > Agreements: Paid Apps and Free Apps both Active Tax forms and bank account Active No pending banners anywhere in App Store Connect or developer.apple.com Test Information complete Export compliance answered Build processes to VALID with no warnings Same error on a brand new app with a fresh build, so it looks like the beta contract is detached on the backend rather than an app-level problem. I've filed a support request and haven't heard back. This is time sensitive, I have a client pilot waiting on an external TestFlight link. Is there any way to get this re-provisioned? Apple Support case ID: 20000118605424 Thanks.

The new search bar in TestFlight is a welcome addition—thank you! However, apps now appear to be sorted alphabetically instead of by their latest update. This makes it much harder to find newly updated builds, especially when testing many apps (we have >100). Could you please restore sorting by most recently updated, or add an option to choose the sorting method?

Hello, I am experiencing a persistent TestFlight installation issue affecting multiple unrelated apps under the same Apple Developer account. For all affected apps: Builds upload successfully to App Store Connect Processing completes normally Builds appear in TestFlight Internal and external testing can be enabled Public links generate correctly However, when attempting to install the app via TestFlight, the installation fails with the error: “The requested app is not available or doesn’t exist.” This occurs: For internal testers For external testers Across different Apple IDs Across different devices With newly created apps After incrementing build numbers After re-uploading builds After signing out/in of TestFlight After regenerating provisioning profiles After creating entirely new app entries The issue currently affects: • TubeChat AI – Apple ID 6752591427 • Vibex – Apple ID 6756860663 • vigilAI – Apple ID 6757738356 Since multiple unrelated apps are impacted in the same way, this appears to be an account-level or App Store Connect backend issue rather than a code signing or project configuration problem. Has anyone encountered a similar situation where TestFlight distribution fails across all apps within a developer account? Any guidance would be greatly appreciated.

[Foxify] Version 1.1.1 (13) Review Hello Apple Support Team, My app's new app version and In-App Purchase appear to be stuck in the review process, and I'd like to check whether there might be an issue with the submission. App Information App Name: Foxify AI - Make Your Own Song. Apple ID: 6761515837. Items for Review: New App Version and New Consumable In-App Purchase. Timeline Submitted: July 21, 2026, at 10:57 AM. As of today (July 27), both the app version and the In-App Purchase have remained in "Waiting for Review" for 7 days. Context We submitted a new app version after addressing the issues raised during the previous review. At the same time, we submitted our first new consumable In-App Purchase, which requires the binary build to test the purchase flow, which has also been stuck for a while and has been rejected a few times due to build rejections and the item itself without a clear reason, so the Apple Review team could test the updated purchase flow together with the new IAP. Normally, both our app updates and In-App Purchases are reviewed within 1–2 days, so this delay seems unusual. Please kindly review the submission. Any guidance or assistance would be greatly appreciated. Thank you for your time and support.

Hello, I uploaded a new build of my app (Air Face), but the latest build does not appear in App Store Connect or TestFlight. The upload completed successfully in Xcode Organizer, but only older builds are shown. I have already waited, refreshed App Store Connect, and confirmed my Apple Developer account. Is there any known issue or additional step required for the latest build to appear? Thank you.

ASC is down and its not yet reflected on the status page. cant upload builds. my apps arent loading and testflight isn't working either

Hello, I'm experiencing a very unusual issue with App Store Connect and would appreciate any advice. Timeline: I submitted version 1.1.2 of my macOS app "Wallpets" for review. I received the notification that the app status changed to "In Review". Shortly after that, App Store Connect became completely inaccessible. A few minutes later, I received another notification that the app was "Rejected". However, App Store Connect is still unusable. Submission ID: 956a336e-1862-4abe-9bbd-c700a654f3df Current symptoms: • On the App Store Connect website, the Apps page displays: "Sorry, something went wrong. Try your request again." and it incorrectly shows "No Apps", even though my app has existed for some time. • The App Store Connect iOS app displays: "App Store Connect is currently unavailable." • TestFlight on macOS also reports: "TestFlight is currently unavailable." • The "View in App Store Connect" link from the rejection email also fails because App Store Connect cannot load. I can still log into my Apple Developer account and the Apple Developer website works normally. The issue only affects App Store Connect and TestFlight. Has anyone experienced this before? Is this likely to be: a temporary App Store Connect backend issue, an account-specific problem, or something that can happen after an app review rejection? I've attached screenshots showing: The review status notifications. The App Store Connect website error ("No Apps"). The App Store Connect iOS error. The TestFlight unavailable error. Any suggestions would be greatly appreciated. Thank you. Update: This issue started immediately after my app entered review, before I received the rejection notification. Additional information: I can successfully sign in to developer.apple.com. Certificates, Identifiers & Profiles are all accessible. The issue only affects App Store Connect and TestFlight.

I'm using TestFlight to test an app with payment/subscription functionality. I created sandbox accounts in AppStore Connect accordingly to be able to test the subscriptions. I'm logged in with the sandbox account. When I try to subscribe in the App the wrong account (this is my actual real AppleID) is used for the subscription although it is recognized that this is just a sandbox subscription. I tried: logging off/on into the sandbox account creating a totally new sandbox account trying to trigger the payment with no logged in sandbox account The result is always: in the payment popup it is stated that the purchase account will be my original AppleID and not a sandbox account. How can I switch the accounts? Is this a bug at Apple's side somehow?

I ran into a strange issue while testing my subscriptions through TestFlight. RevenueCat returned the correct monthly and yearly product IDs, but StoreKit returned zero products. Pricing, availability, agreements, bundle ID, and product configuration were all correct. The problem was the order I added items to the App Review draft. I initially added the subscription products first and the subscription group afterward. What fixed it, Removed everything from the draft. Added the subscription group first. Added the monthly and yearly products afterward. The products then appeared in TestFlight sandbox and purchases worked. No new build or App Review approval was needed. Has anyone else experienced this? I couldn’t find this ordering requirement in Apple’s documentation.