Hi everyone, I'm building an app in Xcode 16.4 with a minimum deployment target of iOS 12. The last time I built with this configuration was November 2025 — that build worked perfectly fine. I'm aware that builds from Xcode 16.4 will no longer be accepted by Apple after April 28, 2026, so I decided to push one final update before that deadline. Here's what I did: Built the app with no changes to build settings Uploaded to TestFlight Tested on iOS 12, iOS 26, and a few other versions — everything looked good Passed App Review Published to the App Store Now users on iOS 12 are reporting that the app crashes immediately on launch. Users on iOS 13-26 are unaffected. We've effectively lost a significant portion of our users overnight. We'd really like to restore functionality for them before April 28 — after that we plan to raise the minimum deployment target anyway. There are no crash logs available, as the app appears to never reach application code at all. Below are the relevant logs from Console.app: default 16:33:49.012231+0400 SpringBoard Bootstrapping MY_BUNDLE_ID with intent foreground-interactive error 16:33:49.021533+0400 SpringBoard [MY_BUNDLE_ID] Bootstrap failed with error: <NSError: 0x280f59aa0; domain: BKSProcessErrorDomain; code: 1 (bootstrap-failed); reason: "Failed to start job"> error 16:33:49.021748+0400 SpringBoard Bootstrapping failed for <FBApplicationProcess: 0x101cb4070; MY_BUNDLE_ID; pid: -1> with error: Error Domain=BKSProcessErrorDomain Code=1 "Unable to bootstrap process with bundleID MY_BUNDLE_ID" UserInfo={NSLocalizedDescription=Unable to bootstrap process with bundleID MY_BUNDLE_ID, BKSProcessExitReason=0, NSLocalizedFailureReason=Failed to start job, NSUnderlyingError=0x280f58780 {Error Domain=NSPOSIXErrorDomain Code=3 "No such process" UserInfo={NSLocalizedFailureReason=The process failed to exec, NSLocalizedRecoverySuggestion=Consult /var/log/com.apple.xpc.launchd/launchd.log for more information, NSLocalizedDescription=Unable to get valid task name port right for pid 241}}, BSErrorCodeDescription=bootstrap-failed} default 16:33:49.021934+0400 SpringBoard Adding: <FBApplicationProcess: 0x101cb4070; MY_BUNDLE_ID; pid: -1> default 16:33:49.022111+0400 SpringBoard <FBApplicationProcess: 0x101cb4070; MY_BUNDLE_ID; pid: -1> exited. default 16:33:49.023325+0400 SpringBoard Removing: <FBApplicationProcess: 0x101cb4070; MY_BUNDLE_ID; pid: -1> default 16:33:49.039576+0400 assertiond Submitting new job for "MY_BUNDLE_ID" on behalf of <BKProcess: 0x100d119f0; SpringBoard; com.apple.springboard; pid: 48; agency: SystemShell; visibility: foreground; task: running> default 16:33:49.039982+0400 assertiond Submitted job with label: UIKitApplication:MY_BUNDLE_ID[0xed03][58] error 16:33:49.040128+0400 assertiond Unable to obtain a task name port right for pid 241: (os/kern) failure (0x5) error 16:33:49.040286+0400 assertiond Failed to start job with error <NSError: 0x100c3f180; domain: NSPOSIXErrorDomain; code: 3; reason: "The process failed to exec"> { description = "Unable to get valid task name port right for pid 241"; failureReason = "The process failed to exec"; recoverySuggestion = "Consult /var/log/com.apple.xpc.launchd/launchd.log for more information"; Has anyone encountered this recently? Any help would be greatly appreciated. P.S. I tried rebuilding from scratch without any code changes and uploading a fresh build to TestFlight — but now it won't even launch from TestFlight on iOS 12.

Hi all ! I'm a new developer on iOs and I' struggling to get my IAP subscription working in sandbox. I've got it working in debug mode on my test env, where I purposely activate the subscription when in my test backend. So that part works. But now, I want to test in testflight with sandbox user credentials. And I see conflicting instructions. My developer account has accepted the Paid Apps Agreement. I've created a subscription group with localized description in both language my app supports. In that group, I've created 2 products with description, duration, pricing, localized name and description and a review screenshot. At that stage, the subscription is at the state "ready to submit". From what I read, I then need to submit them as part of a version submission to activate the IAP. So I did. But then the app was rejected because IAP don't work. I later found out that I need to attach the IAP to the submission, but I couldn't do it, because the IAP where now in "developer action needed". And even after modifying them to reset the state of the localization, the locale are pending submit, but the subscription is still in developer action needed. So in the end, I re-created 2 new subscriptions (with 2 new product ids). At this point, I see posts and replies in reddit and other places that specifically says that the IAP need to be reviewed and approved by apple to be usable in sandbox. But I also see others that specifically says the opposite, that the IAP only need to be in ready to submit. So which is it ? If I submit again the app, I'll end up with subscriptions that are unusable that I can't get back to ready to submit without sending them for review. Thanks for any hints !

As shown in the image, my application was working normally, then suddenly this happened. I've sent an email to support but haven't received a response yet. Has anyone else experienced this?

Hello, I’m experiencing two issues which I believe may be related to a single root cause: TestFlight Installation Error When I try to install my app via TestFlight for testing purposes, I receive the following error message: “Could not install app. The requested app is not available or doesn’t exist.” Unable to Add Build to External Testers When I attempt to add a build to an external testers group, I see the following error in the network tab after submission: { "errors" : [ { "id" : "95d240bd-94bd-4653-8d60-8dc691d6e3dc", "status" : "422", "code" : "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title" : "Beta contract is missing for the app.", "detail" : "Beta Contract is missing." } ] } I have reviewed and completed all required forms under Business → Agreements, and there are currently no pending alerts or agreements requiring action. At this point, I’m unable to proceed with testing my application and would greatly appreciate any guidance or suggestions. Additionally, I have an open support case that has not yet received a response: Case ID: 102855791526 Area: Distribution / TestFlight Thank you in advance for your help.

I'm unable to submit builds to TestFlight or install them on my device for my app "TalkBee" (Bundle ID: com.talkbee.app). Error when submitting for beta review: { "status": "422", "code": "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title": "Beta contract is missing for the app." } When trying to install via TestFlight app on iPhone, I get: "The requested app is not available or doesn't exist." What I have verified: All agreements (Free Apps + Paid Apps) are Active Bank account is Active (SAR) Tax forms (W-8BEN) are Active Build uploads successfully via Transporter Individual developer account, I am the Account Holder Existing Apple Support Case: 102857454011 (no resolution yet) This is blocking my app release. Any help would be appreciated.

Starting today, we have been seeing this error message. This is a blocker for my team and any help is appreciated Things I've investigated: Testflight Apple status page is green Our signing certificate is valid/ unexpired Provisioning profile is valid/ unexpired There are no pending Apple account agreements Doesn't seem to matter if user also is a member of my company's Apple Business Manager developer team Cellular data is turned off Date/ time is correct User was unable to install app using a personal gmail account and unregistered device User was able to use Testflight to install a third-party app outside of our corporate account Uninstalling/ reinstalling Testflight didn't help

Same scenario described here: https://forums.developer.apple.com/forums/thread/738942 User clicked accept for an internal tester invitation sent to their work apple id on their personal device which was signed in with their personal apple id. This seems to have redeemed the code to the users personal account. However, the user has removed themselves from testing the app and we're trying to get their work apple id registered but the invite code that keeps being sent is coming back saying invalid. Things we've tried: We located the last build the user installed on their device and expired the builds deleted / readded the work apple id to internal testing group It's still sending the same invitation code from TestFlight and saying that the code cannot be redeemed.

Hello, I created an app using the latest version of Xcode (16.2), and I'm having a problem testing this app on my iPhones. I created this app just like all the others I've made for my clients, including one on (03/24/25), but when I went to upload another App to App Store Connect on (03/26/25) I couldn't test it on my phone. Points to consider: The app runs perfectly on the Emulator. All my terms and agreements with Apple are up to date. I tried to download the apps through Testflight on 2 different devices, iPhone 7 Plus (iOS 15.8.1) and iPhone 15 Pro Max (iOS 18.3.2), and I was unsuccessful in neither attempt. I can send my app to the internal testers, but when I click download, the following message appears: Could not install [APP NAME]. The requested App is not available or doesn't exist. I imagine this problem is with Apple itself, I have already contacted support, but I need to resolve this urgently for my customers. Has anyone experienced this and resolved it?

Hi, I’m new here and trying to upload my first two apps to the App Store, but I’m getting stuck in TestFlight. I’ve tried several different ways to export my apps, both with Expo and Xcode, but it makes no difference. My apps get stuck in Ready to Submit. When I add Internal Testing (my self) I receive an email saying I can start testing the app, and I can see it in TestFlight, but when I tap on it I get the following error: Unable to install AppName. The requested app is not available or does not exist. I contacted Apple Support over a week ago, but I haven’t received any response. Any suggenstions? Thanks, Jonas

We submitted our test flight build Thursday night, it's been over 60 hours. Does anyone have any suggestions on how to expedite this? I contacted support by going through Distribution -> TestFlight although it might be seen as a generic testflight question. The expedited app review route seems like it's only for AppStore.

We are having trouble analyzing our app's size. When we evaluate the app size locally, it might show a decrease, but after uploading it to TestFlight, we sometimes see the exact opposite result. Evaluating this is very complex. We suspect this discrepancy is due to server-side optimizations by Apple, but there is a lack of clear documentation and articles explaining the process. Can anyone help clarify why this happens and how to measure it accurately?

With respect to the warning, "90725: SDK version issue." Does this only affect new submissions to TestFlight, or would existing submissions be shut down after April 28? For instance, if we were to submit a new version of our app to TestFlight on April 15th, would that build be valid for test users for 90 days? Or would those builds be made invalid as of the 28th? Any input or clarification would be greatly appreciated. Thanks! Kevin Jordan Ephibian, Inc.

Hi everyone I recently build an app and deployed it through app store connect and testet it on TestFlight. Everything worked fine up until build 1.0.3. Since then I have not been able to install the app on my phone through TestFlight - even though build and submission runs through successfully on eas, expo and app store. I have tried deleting and reinstalling the TestFlight from my phone. removing and adding back myself as tester. checking logs and commits from the shift from build 1.0.3 to build 1.0.4. I can see I changed "name" and "slug", so I tried removing the app from app store connect and added a new one with new build and submission. Ran through successfully but still could not install the app through TestFlight on my iPhone. I have also tried reaching out to Apple Developer Support, but I have not heard from them. Has anyone tried something similar?

Hi, I’m running into a persistent issue in App Store Connect related to TestFlight and app reviews, and I’m hoping someone has seen this before. Around two weeks ago, I started getting the following error when trying to create external TestFlight builds: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING Since then: I cannot create any external TestFlight tests Internal TestFlight builds appear, but cannot be downloaded (“The requested app is not available or doesn’t exist”) My apps do not progress properly through review One app got stuck in “In Review” for ~10 days; I eventually withdrew it and resubmitted it At this point, I cannot update two existing apps, and I can’t start testing a new app at all Important details: This is an individual developer account I am the Account Holder All contracts appear active and valid The issue affects multiple apps, not just one Nothing changed on my side (no contract updates, no account changes) before this started happening. I’ve already reached out to Apple Developer Support multiple times, but unfortunately haven’t received any response so far, which makes it unclear how to proceed. Has anyone experienced this issue or found a resolution? Any insight would be greatly appreciated. Thanks!

When I submit the app to TestFlight beta review I get the error show on UI. (I filled all filed info in Beta Infomation) There was an error processing your request. Please try again later I was inspected Safari to see the detailed error and I got the below error. Failed to load resource: the server responded with a status of 422 () and the detailed javascript error componentStack: undefined errorCode: undefined message: "API Response Error: TF_BETA_APP_REVIEW_RESPONSE" stackTrace: "status code: 422 --- api correlation key: NZEKCTWMNANXDZVTRD3V4GNE3U" Anyone can tell me the problem and how to fix it. Many Thanks.

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.

Hello everyone. We have an app that has been on the App Store for several years, originally distributed for iOS and iPadOS only. Recently, we enabled Mac (Designed for iPad) and started distributing macOS-compatible builds. Current situation: The app is available and downloadable from the macOS App Store and runs correctly on Apple Silicon Macs. The same app/build appears in TestFlight on macOS, but cannot be installed. TestFlight shows the message: “This app can only be tested on an iOS device.” This suggests the app itself is Mac-compatible, but TestFlight is treating the build as iOS-only. Environment and checks performed: Mac is Apple Silicon. App Store Connect app-level availability for Mac (Designed for iPad) is enabled. The app is not Mac Catalyst; it is a UIKit iOS/iPadOS app. Distribution is done via GitLab CI. CI uploads use an App Store provisioning profile (Apple Distribution), not development or ad-hoc. iPhone and iPad TestFlight installs work as expected. Info.plist verification: UIRequiredDeviceCapabilities was originally present (armv7) and has since been: removed entirely, build number incremented, new builds uploaded to TestFlight. No other hardware capability requirements are declared. LSRequiresIPhoneOS = true remains unchanged. No other plist keys that should exclude macOS are present. CI / build considerations: The same uploaded build is accepted by App Store Connect and distributed successfully on the macOS App Store. This tells us the binary itself is valid for macOS, but TestFlight applies additional or different eligibility checks. At the moment we think that TestFlight eligibility may depend on build metadata, scheme/configuration flags, or internal App Store Connect state that differs from App Store distribution. Questions: Are there known cases where a build is valid for macOS App Store distribution but not eligible for macOS TestFlight installation? Does anyone know if TestFlight applies stricter or different platform gating than the App Store for “Mac (Designed for iPad)” apps? Are there specific build settings (e.g. SUPPORTS_MAC_DESIGNED_FOR_IPAD, TARGETED_DEVICE_FAMILY, scheme/config mismatches) that can affect TestFlight macOS eligibility independently of App Store eligibility? Is there an authoritative way in App Store Connect to inspect why a specific TestFlight build is marked as “iOS-only” for macOS? Any insight into TestFlight-specific eligibility rules for “Mac (Designed for iPad)” would be appreciated, especially given that App Store distribution for macOS is already working. I hope we're missing something very basic, and not that the app can't be tested as is for the mac, because it's useful to have our QA team test it on the mac.

Hi there everyone! ELB owner of VIBERELIC here. NOTE: I tried posting this a couple times now but it keeps getting taken down - I am not too sure why. I haven't received any explanation and I am pretty certain that I am posting in the correct place for TestFlight Apps. Anyways, let's try this again! ✦ I am really excited and proud to finally share with you all what I have been working on for the past month! My flagship app "WilderDEX!" is finally at the point where it can be tested by the public. I hope you guys have pets because this is the perfect app to document their personalities! It's basically a real-life Pokemon PokeDEX! With WilderDEX!, you have the ability to collect animals using unoccupied "LIFE-CUBES". You get 1 LIFE-CUBE each day that you successfully collect an animal. From there, you can trade your occupied LIFE-CUBE with others users, generate unique digital cards + share them on social media straight from the app, see where in the world and by whom different wildlife was discovered, unlock a plethora of achievements, and participate in the leaderboard ranking system! Please help test the app and provide any feedback you possibly can. It is incredibly valuable for the improvement of the app before it's official launch. Report any glitches you encounter, performance issues, and ideas you may have that could improve the app from it's current state! I have a lot more ideas that I am planning on implementing once everything is certified working and stable. Please let me know if you have any questions! Thank you for your interest, and HAPPY COLLECTING! Test here : https://testflight.apple.com/join/8vmVfRrb all rights reserved © 2026 viberelic ✦ ventures ✦ Above : A Uniquely Generated WIlderDEX! Digital Kitty Card

Hello, I have an internal TestFlight build for my app PewPewApp (Apple ID 6760741808). The build is processed, assigned to an internal group, and the tester invitation is accepted. The build status shows Ready to Test / Testing in App Store Connect. However, installation from TestFlight fails with: “The requested app is not available or doesn’t exist.” Could you please check whether there is an account-level or backend TestFlight distribution issue affecting this app/build? Thank you.

Hi everyone If it possible, to receive a test flight code regards