“build disappears”

First off, to clarify the purpose of this forum and my role at Apple, this forum is specifically to support engineers building products for our platform, not consumer-level support. I'm responding here because I hope the information will be helpful to you and to other engineers working on our hardware. However, I can't comment on if or when this will be fixed, nor am I the right person to try and pass feedback through. Secondly, on the feedback side, I'd appreciate you filling a bug on this and then posting the bug number back here so I can ensure it gets to the correct team. That's the best way to get this feedback to the relevant engineering team. In any case, I can't provide you with a direct solution, but I can confirm that this is basically what's going on: From what I am reading, it appears to be that the M4 Pro has 3 display lanes, and when I plug the first Studio Display XDR, it is using 2 lanes. More specifically, the kernel logic that assigns display pipes to monitors is not particularly so

Thanks for the post, I don’t see what are you selecting to install. Download Directly from the Apple Developer Portal is the recommended way or better use the Apple Store for the release version. Go to the Apple Developer Downloads page. Sometimes the GUI fails, but forcing the macOS software update utility through the terminal works. If Xcode is a beta or internal build, the xcode-select --install command will almost always fail because Apple does not host beta Command Line Tools on the public production update servers. I would recommend to install the Xcode you want from the developer portal if beta or RC and the App Store if you want the latest release version. Albert 
  Worldwide Developer Relations.

I am seeing the same issue. I had another developer try to submit the same build and they got the issue as well, but when they created a new build for submission on their end they were able to successfully submit. So I'm wondering if there is possibly some build issue on my end, but I'm not seeing any indication that is the case from App Store Connect. This is a build that we have distributed through Test Flight that we are now trying to submit for release.

The error comes and goes while its compiling and then doesn't run the app. This typically happens when the code is shared across multiple targets, and one of them has minimal deployment target lower than version 26. Also, if your project has a watchOS app, the FoundationModels framework isn't currently available in watchOS. If that is not your case, I'll be interested in looking into your project, or the build log that contains the error. Best, —— Ziqiao Chen  Worldwide Developer Relations.

I will go ahead and file a request for a Core HID development variant. Perfect, thank you. FYI, I can't guarantee anything will change, but I'd like to get this sorted out as soon as possible, so this might be working relatively soon (at least on paid accounts). One comment here: More broadly, I think it would be very valuable to have a simple user-space API for controller virtualization available to hobbyists and personal developers as well, even if limited to development builds. I've seen a few requests asking about providing this support to the free account tier, not just the paid tier. It's a reasonable suggestion, but I did want to explain that the main reason the development entitlements are restricted to paid accounts is as a form of practical security protection. The idea here is that the underlying details of development signing's limitations: Builds only run on the specific devices that were registered when the signing profile was generated. Registering a device requires extracting

I uploaded a new build of the app and that seems to have resolved the issue. 🤷‍♂️

We see this issue in iOS 26.3 as well, but it can reproduce almost every time if we build the app with Xcode 26.4 and run the app on an iOS 26.3 device. Also sent: FB22305926 with the crash log.

DevForums is primarily focused on APIs, so if you’re building an app that’s affected by this, or a Bluetooth accessory, please let me know. If not, my advice is that you seek help from Apple Support, either directly or on Apple Support Community. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='820849021, AndriiSulimenko, /thread/820849, /profile/AndriiSulimenko'] Is it possible to distribute a DNS proxy provider for use on non-MDM / non-supervised devices? [/quote] No. The table in the DNS proxy section of TN3134 lists two options for iOS: app extension | 11.0 | supervised devices only | 16.0 | per-app on managed devices If you exclude those two options then you have… well… zero options. [quote='820849021, AndriiSulimenko, /thread/820849, /profile/AndriiSulimenko'] Is [this] strictly enforced at distribution/runtime? [/quote] Yes. It’s a privacy policy that’s strictly enforced at runtime [quote='820849021, AndriiSulimenko, /thread/820849, /profile/AndriiSulimenko'] Is a packet tunnel provider the only viable alternative for App Store distribution? [/quote] There are two parts to this question: Do packet tunnel providers work on general user devices? Are there a viable alternative to a DNS proxy. The answer to the first is “Yes.” TN3134 makes that clear. The answer to the second is “No.” TN3

Thank you for your response, Richard. I have a follow-up question to clarify the exact trigger for the launch failure. Could you tell us which of the following scenarios actually causes the app to fail to launch? Built with Xcode 26 (iOS 26 SDK), run on an iOS 27 device — Does the app fail to launch simply because the device is running iOS 27, even though it was built with the older(=26) SDK? Built with Xcode 27 (iOS 27 SDK), run on any OS version including iOS 27 — Does the failure occur across all OS versions, including iOS 27(All OS versions(iOS15 or higher) supported by my app), as long as the app was compiled with the iOS 27 SDK without adopting the scene-based life cycle? Both of the above — Does the failure apply in either case? Understanding whether this is enforced at the OS level (runtime) or at the SDK/build level (compile time) is critical for planning our migration and release timeline. Thank you.