“eskimo”

[quote='816877021, Pushpak-Ambadkar123, /thread/816877, /profile/Pushpak-Ambadkar123'] inquire about the process for obtaining approval for the following entitlement in my iOS/macOS app [/quote] There is no approval process for this. Most NE entitlements, including the one for content filters, are available to all (paid) developers. Note Historically there was an approval process for this but that’s not been the case for almost 10 years now. See Network Extension Framework Entitlements. There are, however, significant deployment restrictions for content filters on iOS. I cover those in TN3134, which I mentioned in my reply on your previous thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I just wanted to stop by and drop some links: There’s a previous DevForums thread about this issue. And Cyrille created Swift Forums thread as well. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. For lots of additional info about notarisation, see Notarisation Resources. Specifically, it links to a Q&A with the notary service team that’s quite instructive. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='816946021, hellnola5, /thread/816946, /profile/hellnola5'] when iOS or iPad OS connected to a Wi-Fi with captive portal [/quote] Is this a captive network that you control? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Right. The submission form has two options: Swift Playground 4.6 or later Xcode 26 or later (with a note saying “Xcode app playgrounds are run in Simulator.”) In the first case, your submission must necessarily be run on an iPad. In the second, your submission will be run on the simulator, not a real device. There are some caveats here: In the first case, the Swift Playground app doesn’t yet include support for the iOS 26 SDK )-: See this thread. In the second case, the form doesn’t currently say whether it’ll be an iPhone on iPad simulator. See this thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Let’s focus this discussion on your other thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Regarding the deployment target issue, see this thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='816935021, Rayane_Dev, /thread/816935, /profile/Rayane_Dev'] My question is can I submit a MyApp.xcodeproj file … ? [/quote] No. The rules are crystal clear about this: Your submission must be an app playground (.swiftpm) in a ZIP file. My understanding is that the Foundation Models framework works just fine in an app playground, but you will have to raise your deployment target to iOS 26. See this thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Indeed, @concurrent is introduced by SE-0461, which I referenced above. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

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

Its redirecting to my own thread Oh gosh, sorry. I juggle a lot of threads and sometimes I lose track of the context )-: the pop-up does not specify if the playground will be run on an iPad simulator or an iOS simulator Indeed. I’ve always just assumed it would be an iPad simulator because that’s equivalent to what you get when you run an app with the Swift Playground app on iPad. However, you’re correct that the submission form doesn’t say that explicitly. My general advice here is that you strive to make your app work well on both iOS and iPadOS. That is, after all, what we expect of ‘real’ apps. If you can’t do that then my only immediate suggestion is to use the Comments box to note this. However, I’m also going to do a little digging to see if I can clarify our policy here. ps It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo

It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. I had to switch to Objective-C for the language to find the list Right. This is because Swift isn’t importing the C API directly, but rather the C APIs are marked as refined for Swift and there’s a Swift API that wraps them. If you rummage around in the headers you can see how this actually works, via the APPLE_ARCHIVE_SWIFT_PRIVATE macro. Curiously, you can access all this stuff from Swift by adding a double underscore prefix: guard let pathList = __AAPathListCreateWithDirectoryContents(/foo/bar, nil, nil, nil, 0, 0) else { … handle the error … } Not that I recommend that you do that. Using low-level C APIs like this from Swift isn’t much fun. Moreover, it puts you way off the beaten path. So, if you find something that you can’t do from Swift but can do from C, I recommend that you: Do it from C, and then call that C code from Swift. File an enhancement request against the Swift API e

[quote='877265022, bandf, /thread/816475?answerId=877265022#877265022, /profile/bandf'] I have already submitted the issue via Feedback Assistant … FB22021943. [/quote] Thanks. [quote='877265022, bandf, /thread/816475?answerId=877265022#877265022, /profile/bandf'] I intentionally chose to raise the matter here as well. [/quote] That’s not a problem. But in that case it’s best to lead with the bug number. That’s helpful for both your intended audiences: Apple folks can check on the state of your bug. Non-Apple folks know that they don’t have to file their own bug. But if they want to track the state of this issue they can choose to file their own bug and ask that it be marked as a duplicate of yours. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

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='816702021, Pavel, /thread/816702, /profile/Pavel'] I need to develop a … Transparent Proxy … that sends data to the host application for analysis. [/quote] You mean the container app, right? [1] If so, this architecture is a concern. A transparent proxy operates system wide, so: There may be 0, 1, or more active GUI login sessions. Each active GUI login session can be running an instance of your container app. So if multiple users are logged in and they each run a copy of your container app, what are you expecting to happen? This architecture also informs your XPC architecture. A NE sysex, which operates much like a launchd daemon, can’t connect to a named XPC endpoint advertised by an app because the system wouldn’t know which app to connect to [2]. Given the above, the only architecture that works is for your sysex to advertise the named XPC endpoint and for your apps to connect to it. And that’s exactly what’s demonstrated by the Filtering Network Traffic sample code. There are a couple of things t