“build disappears”

[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.

However, This UI glitch We have noticed not only on Toolbar but wherever we are using dropdown(Menu+Picker) throughout the app. It created different shapes while disappearing such as circle and capsule. In iOS 26.0 it shows capsule and iOS26.2.1 it shows circle like UI while disappearing. Is this existing issue in XCode/iOS26, If yes, When we can expect the fix from Apple?

Thanks for the update. Just to clarify: Starting from April we must use Xcode 26.X to upload apps to the App Store (using older Xcode versions will fail). In addition, Xcode 26.X deployment target is iOS 15+. So, no option to release apps targeted to older iOS versions? If this is the case, why this isn't blocked during the Xcode build process? or even during the App Store processing? Also, what about the apps we already published a week ago with target deployment 12.0?

Thank you for filing the feedback, @newwbee. We responded to your feedback privately a while ago, but I want to include the response here, too, for anyone else that might have the same question and stumbles upon this. SwiftUI’s Settings scene is designed to help you build a first-class Mac settings experience that follows Apple’s Human Interface Guidelines at https://developer.apple.com/design/human-interface-guidelines/settings#macOS Toolbars within Settings scenes use a style appropriate for a typical macOS settings window, which displays centered tabs to group related settings. (Please refer to Settings windows in apps like Safari and Mail as an example.) People also typically expect macOS application settings to be applied as soon as the setting is changed, without the need for a “Save” button. To create a bespoke settings experience for your app, you can use a regular Window scene, which uses a default toolbar style that you’d be familiar with in an application’s main and document windows. You w

I just renewed my paid developer account today and I'm still getting this issue. I'm hoping I can build and test on my current iPhone but I'm stuck because I get this error message. Some assistance will definitely be helpful

Update: After extensive investigation I have identified what appears to be the root cause of the 401 Invalid Bearer Token error on my Intel Mac, and I want to share the findings in case they help others reporting similar issues on M1 and M4 machines. WHAT I FOUND (Intel Mac - x86_64): The Claude Agent binary that Xcode downloads is the darwin-arm64 build regardless of host architecture. On my Intel Mac this binary physically cannot execute, which fails silently and surfaces as a 401 error. Confirmed via terminal: file ~/Library/Developer/Xcode/CodingAssistant/Agents/claude/2.1.14/claude Returns: Mach-O 64-bit executable arm64 — wrong for Intel Mac The IDEChatClaudeCodeVersion preference is hardcoded to the ARM64 download URL: defaults read com.apple.dt.Xcode IDEChatClaudeCodeVersion Returns: darwin-arm64 URL regardless of CPU architecture We also confirmed the darwin-x64 binary exists in Anthropic's distribution bucket and runs correctly on Intel — both in the terminal and as a standalone binary: cur