“xcode github”

Builds Settings -> All -> Architectures: “Standard Architectures (Apple Silicon, Intel) - $(ARCHS_STANDARD) for both Debug and Release Builds Settings -> All -> Build Active Architecture Only: “No” for both Debug and Release Reinstall MacOS 26.1, Xcode 26.2. Same result: no Universal, only one platform (Silicon or Intel, never both)

Thanks for your post. This is very interesting but I also think we have released many news about why Xcode does not say universal on the template even though they are all universal depending on your target. This thread should be utilized by other developers to provide links to Apple News and videos that explain the path forward. I extend an invitation to anyone who possesses resources and links. I know is confusing if the Xcode template does not say universal, but is all about the target and I would prefer you think about the target after you create the app, so this is still relevant: https://developer.apple.com/documentation/apple-silicon/building-a-universal-macos-binary There is an announcement in this WWDC video about the platforms we are supporting I would recommend you to watch as will answer many questions. Platforms State of the Union - WWDC25 - VideosApple Developerhttps://developer.apple.com · Jun 9, 2025 https://developer.apple.com/videos/play/wwdc2025/102/ The steps outlined belo

@Simpson3568 I am not sure but as per my knowledge submissions created with swift playground can be run on ( or will be run on ) iPad, whereas playgrounds created using Xcode will be run on iOS simulator. For more clarity please read the swift student challenge page on apple developer's website.

Looking at the policy, requirements are for Swift Playground 4.6 or Xcode 26 https://developer.apple.com/swift-student-challenge/policy/ No iOS is specified on that document. I would set the minimum iOS required the Xcode and Swift Playground allow you to set your needs. Albert Pascual
  Worldwide Developer Relations.

While Foundation Models framework can only run on iOS 26.0 or newer, whether you want to set your deployment target to 26.0 is up to you. If you want to keep your app's target at 18.1 for backwards compatibility for people using an older OS, you can use #available checks to gate certain functionality to be available only for iOS 26.0 or newer. Meaning people using an older OS won't get Foundation Models features, but people using a compatible OS will. This article here explains how to do it: https://developer.apple.com/documentation/xcode/running-code-on-a-specific-version

@DTS Engineer I'm experiencing the exact same issue. Is there a fix planned for this? Environment: Xcode 26.2 (24553) (Build 17C52) iOS tested: 18.7.2 and 26.3

The receive(minimumIncompleteLength:maximumLength:completion:) has a lot of options and it works with many different protocols. Given that, coming up with a definitive table of what it will do in every possible case is hard, and I’ve never seen that officially documented in sufficient detail [1]. Given that, I generally stick with protocol-specific recipes: For stream-based protocols, like TCP, I use receive(minimumIncompleteLength:maximumLength:completion:) and then, in the completion handler, I process: The data first, if there is any Then the error, if there is one For UDP, I always use receiveMessage(completion:). This is a great option because UDP datagrams have a limited size that easily fits in memory. For message-based protocols without that convenient limit, things get tricky. You have to use receive(minimumIncompleteLength:maximumLength:completion:) but you then need to worry about the isComplete Boolean and potentially the context. Fortunately, these cases are rare [2]. Notably, this approach is co

As a follow‑up for anyone hitting the same issue: Per Quinn’s advice, I switched to manual signing outside Xcode and followed the “Exporting a Developer ID Network Extension” guidance. The code signing / notarization side now looks correct and works locally: Host app and DNS Proxy system extension are both signed with Developer ID Application for our team (for example, TEAMID1234). com.apple.developer.networking.networkextension in both host and system extension entitlements uses `dns-proxy-systemextension. The app bundle identifier is com.myapp.agent.MyProxy. The installer pkg is signed with Developer ID Installer: MyApp Inc (TEAMID1234), notarized with notarytool (status: Accepted), stapled, and passes `pkgutil --check-signature. On the test Mac (macOS 14.4, Apple Silicon), sudo installer -pkg MyProxy_…pkg -target / succeeds, the app appears in/Applications, and spctl --assess -vvv -t exec reportssource=Notarized Developer ID`. The app launches and the DNS Proxy system extension runs (any

Swift’s superclass initialisation rules are complex, so it’s hard to answer questions like this without seeing a concrete example. Anyway, I most commonly see folks hit this when they’re creating a Cocoa view, so let’s look at that: import AppKit class MyView: NSView { var counter: Int override init(frame: NSRect) { self.counter = 0 super.init(frame: frame) } required init?(coder: NSCoder) { super.init(coder: coder) // ^ Property 'self.counter' not initialized at super.init call self.counter = 0 // A } } This fails because you have to initialise counter before calling super. Moving line A up a line fixes the problem. If you have an example of the other behaviour, please share it. Oh, and this was Xcode 26.2 with the macOS 26.2 SDK. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='816773021, millerswiftdev, /thread/816773, /profile/millerswiftdev'] Does this mean Mac Catalyst … ? [/quote] No. [quote='816773021, millerswiftdev, /thread/816773, /profile/millerswiftdev'] Does this mean … a iPad VM? [/quote] No. There’s no supported virtualisation mechanism for iPad. If you build in Xcode, you should expect that your submission will be run on the simulator. We call that out in the Swift Student Challenge Submission submission form. You can assume that the Xcode and simulator versions will be 26 or later, so it’s fine to use iOS 26 APIs. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com