“build disappears”

Since I have changed of iPhone (yesterday) to run my draft application, I systematically, and instantaneously get a message The application failed to launch., i.e. the application successfully built and was downloaded to the new iPhone (Iphone 17 pro - iOS 26.4). I have checked that this new iPhone is well registered on my list of authorized devices. Could you help me to fix this issue ? Here is the verbose attached to the failure: The application failed to launch. Domain: com.apple.dt.CoreDeviceError Code: 10002 User Info: { BundleIdentifier = com.laurent-guise.ble-laser; DVTErrorCreationDateKey = 2026-03-30 07:59:46 +0000; IDERunOperationFailingWorker = IDELaunchCoreDeviceWorker; } The request to open com.laurent-guise.ble-laser failed. Domain: FBSOpenApplicationServiceErrorDomain Code: 1 Failure Reason: The request was denied by service delegate (SBMainWorkspace). User Info: { BSErrorCodeDescription = RequestDenied; FBSOpenApplicationRequestID = 0x3868; } The operation couldn’t be completed. The process fa

The title says it all, and I've filed FB FB22353950 that includes an Xcode 26.4 Screen Saver test project, QT movie demonstrating the error, and a PDF with complete steps to build and test. I'm asking here just to learn if this sounds familiar. The SS built on 26.4 fails in 26.4, works fine on 26.3.1. I'll supply the test files if there's interest. Thanks.

Reference: FB21797091 / Related to thread 807695 Hello, I have already submitted a report regarding this issue via Feedback Assistant (FB21797091), but I would like to share the technical details here to seek further insights or potential workarounds. We are experiencing a technical regression where Universal Links and Shared Web Credentials fail to resolve for Internationalized Domain Names (IDN) specifically on iOS 16 and later. This issue appears to be identical to the one discussed in thread 807695 (https://developer.apple.com/forums/thread/807695). Technical Contrast: What works vs. What fails On the exact same app build and iOS 16+ devices, we observe a clear distinction: Standard ASCII Domain (onelink.me): Works perfectly. (Proves App ID and Entitlements are correct) Internal Development Domain (Standard ASCII): Works perfectly. (Proves our server-side AASA hosting and HTTPS configuration are correct) Japanese IDN Domain (xn--[punycode].com): Fails completely. (Status: unspecified) Note: This

Hello Xcode 26.0.1 (17A400) Missing some Metal components When building a program using Metal, it induces an unexpected error : “error: error: cannot execute tool 'metal' due to missing Metal Toolchain; use: xcodebuild -downloadComponent MetalToolchain Command CompileMetalFile failed with a nonzero exit code” Which terminates the build The fix given “xcodebuild -downloadComponent MetalToolchain” using sudo does not work Did someone find a work around or could resolve the issue? Many thanks Jean MacBook Air M4; macOS 26.0.1; Xcode 26.0.1

I recently released version 8.5.4 (build 188) using Cloud Build. During testing via TestFlight, the app worked correctly on an iPhone 6 running iOS 12.5.8. However, after the app was published on the App Store, I found that the same version does not open at all on iOS 12 devices. Previously, earlier versions (such as 8.5.3) were functioning properly on iOS 12. My app’s minimum deployment target is set to iOS 12.0. This issue appears only with the App Store version, while the TestFlight version works fine on the same device. Due to this, I have paused the phased release of version 8.5.4 to prevent further impact on users still running iOS 12. I would like guidance on the following: 1. Has there been any recent change or limitation affecting apps targeting iOS 12 on the App Store? 2. Is there a way to prevent iOS 12 users from downloading version 8.5.4 while allowing them to continue using version 8.5.3? 3. Is there any recommended approach to ensure compatibility or restrict distribution base

Hi, I’m looking for clarification on TN3134: Network Extension provider deployment, specifically iOS deployment requirements for: packet tunnel provider DNS proxy provider From the documentation: Packet Tunnel Provider App extension (min iOS 9.0): per-app mode requires a managed device DNS Proxy Provider App extension (min iOS 11.0): supervised devices only App extension (min iOS 11.0): per-app mode requires managed devices Issue I implemented a DNS proxy using NEDNSProxyManager. Works as expected in debug builds on a local device Fails to configure when distributed via TestFlight Console Output (TestFlight build) error 10:05:39.872258-0500 nehelper The production version of *** is not allowed to create DNS proxy configurations. Use MDM to create DNS Proxy configurations for the production version of ***. Question Is it possible to distribute a DNS proxy provider for use on non-MDM / non-supervised devices? If not: Is the limitation strictly enforced at distribution/runtime? Is a packet tunn

We have 8 consecutive notarytool submit submissions for the same .dmg artifact all stuck In Progress with no movement and no logs available. Submission IDs (all Recall-0.3.6-arm64.dmg, Team ID: H9S7XRPUCA): Diagnostic evidence: notarytool log on all 8 returns exit 69 (log not available) — no rejection reason, no processing output The app bundle submitted as a ZIP (same binary, same signing, submission d21e9fea) was accepted in 41 seconds at 2026-03-27T02:15Z A separate probe submission of a small signed binary on the same team (fcf018c5) was accepted in ~5 minutes All prior Recall DMG builds (0.1.0–0.3.5) processed normally in ~8 minutes on this same team Normal processing time for this team/account is ~8 minutes Conclusion: Content and signing are clean. Account queue is healthy. The issue appears specific to the DMG submission path for this build. Requesting Apple investigate the stuck DMG submissions and advise on next steps.