“eskimo”

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

[quote='816770021, sardinelee, /thread/816770, /profile/sardinelee'] At the OS level, the only error codes we receive are: … -1005 … -1001 [/quote] Right. These are NSURLErrorNetworkConnectionLost and NSURLErrorTimedOut, respectively. They are transport errors, meaning that the HTTP request failed because something went wrong with the underlying TCP/IP transport connection (TCP for HTTP/2 and earlier, QUIC for HTTP/3). There’s more info about the -1005 error in QA1941 Handling “The network connection was lost” Errors. The -1001 is pretty straightforward: The transport connection stopped moving data and eventually the HTTP request timed out. Given the above, you need to look for problems deeper in the TCP/IP stack. I usually start an investigation like this with an RVI packet trace, which lets you see what’s happening on the ‘wire’ as far as iOS’s TCP/IP stack is concerned. I suspect you’ll find that the Wi-Fi has simply stopped delivering packets. The critical factor here is that it’s limited to iPhone 17 and

Submitting your app with a warning is better than not submitting it at all. But obviously it’s better to not have warnings. AFAIK this warning is generated by you adding an Asset Catalog (.xcassets) to your playground. What happens if you remove that? 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

[quote='816782021, alexfromapex, /thread/816782, /profile/alexfromapex'] Has anyone gotten Postgres to run in a sandboxed app? [/quote] Not personally, but I can shed some light on the App Sandbox side of this. System V IPC is a compatibility API an macOS. We recommend against using it in new code. Given that, it shouldn’t come as a big surprise that it doesn’t have a good story regarding the App Sandbox. The alternative, Posix IPC, works in the App Sandbox as long as you conform to the naming guidelines described in App Groups Entitlement [1]. So, to make this work you’ll need to: Sign your executables to claim access to an app group. Configure the library to use Posix IPC. With a name that’s authorised by that app group. I don’t have any expertise with this specific third-party library, so I’ve no insight into the last two. I’m happy to help with the first. I have lots of background on that in App Groups: macOS vs iOS: Working Towards Harmony. Share and Enjoy — Quinn “The Eskimo!” @ Developer Techn

It sounds like you’re trying to create an App Store Connect API key. When you do that, you get one shot at downloading the key itself, but the Issuer ID and Key ID are visible on App Store Connect indefinitely. An Issuer ID is a UUID, for example, c055ca8c-e5a8-4836-b61d-aa5794eeb3f4. A Key ID is a 10-character identifier, for example, T9GPZ92M7K. For more info on how to create these keys, see Creating API Keys for App Store Connect API. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='816646021, yyzzcc, /thread/816646, /profile/yyzzcc'] Who or how can I find out what going on with it. [/quote] The canonical escalation path for entitlement requests is Apple > Developer > Contact Us > Development and Technical > Entitlements. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='877236022, Lancelotbronner, /thread/816736?answerId=877236022#877236022, /profile/Lancelotbronner'] now there's a target for the XPC service [/quote] Right. XPC doesn’t let you establish a connection between arbitrary processes. Rather, the process advertising the named XPC endpoint must be known to the system. I talk about this a bunch in XPC and App-to-App Communication; see XPC Resources for a link to that. Note that this only affects the connection direction. XPC connections are bidirectional, so the communication direction can go the other way, or in fact go both ways. XPC Resources has a link to another post that discusses that. [quote='877236022, Lancelotbronner, /thread/816736?answerId=877236022#877236022, /profile/Lancelotbronner'] I have an issue with MTLSharedTextureHandle not being Encodable [/quote] It conforms to NSSecureCoding, indicating that it’s intended to be sent across an NSXPCConnection rather than the newer XPCSession. AFAICT there’s no generic way to transfer such an object via

I chatted with my Core Bluetooth colleague about this, and we’re not entirely sure how the failure you’re seeing can be caused by your execution context. Which isn’t to say that it’s not the case, just that the connection isn’t obvious. I usually debug problems like this in small steps. For example, in your case: I would build my agent as an app, with a menu bar and everything. I’d run that from the Finder (or Xcode) and see if Bluetooth behaves in that case. I’d then set it to run as a launchd agent, but still with the menu bar. And re-test Bluetooth. If that works, you know that the launchd agent context isn’t the cause of your issue. Finally, I’d then switch it to run without a menu bar by setting LSUIElement. And re-test Bluetooth again. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='877143022, Pushpak-Ambadkar123, /thread/815498?answerId=877143022#877143022, /profile/Pushpak-Ambadkar123'] prevents access to specific URLs by blocking any websites included in a predefined block list across all browsers installed on an iOS device. [/quote] URL filter is a good option there. Most iOS web browsers [1] are based on the built-in WebKit and thus honour URL filter restrictions without any additional work on the browser’s part [1]. [quote='877143022, Pushpak-Ambadkar123, /thread/815498?answerId=877143022#877143022, /profile/Pushpak-Ambadkar123'] and eventually browser shows error including organization name. [/quote] To reiterate, that’s not something supported by URL filter out of the box, and I encourage you to file an enhancement request for that feature. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] This isn’t the case on macOS, where it’s common for web browsers to not use WebKit (and also not

[quote='877058022, crewshin, /thread/816045?answerId=877058022#877058022, /profile/crewshin'] the option in Xcode is all I need? [/quote] Correct [1]. [quote='877058022, crewshin, /thread/816045?answerId=877058022#877058022, /profile/crewshin'] there is another issue on my side that I need to track down. [/quote] I have a bunch of helpful links in Network Extension Resources. Specifically, check out Debugging a Network Extension Provider. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Assuming that: You’re creating one you’re part of a paid developer team. See Developer Account Help > Reference > Supported capabilities (iOS). You’re creating a packet tunnel provider. You’re not concerned with MDM deployment.

[quote='877124022, rbmanian75, /thread/815676?answerId=877124022#877124022, /profile/rbmanian75'] The bug still exist in Tahoe 26.4 Beta 2 also. [/quote] Yep. That gels with my understanding )-: However, please do continue testing with new beta releases as we seed them. [quote='877124022, rbmanian75, /thread/815676?answerId=877124022#877124022, /profile/rbmanian75'] They are asking me to find another workaround. [/quote] I can’t see any better way to work around this in an App Store app, where all the components are necessarily sandboxed. I recommend that you continue to explore App Review options. See here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='877059022, 9labs, /thread/816046?answerId=877059022#877059022, /profile/9labs'] I’ve filed a support request through the Developer Support channel. [/quote] Cool. But just to reiterate the point I made above, I’d appreciate you filing a bug about this and posting the bug number here. Oh, and apropos that, lemme tag in @noyna and @froglike6 Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='877018022, vishalsehgal, /thread/815465?answerId=877018022#877018022, /profile/vishalsehgal'] We wanted to reduce the kernel overhead of assembling bytes that receiveMessage(completion:) does. [/quote] I have two things to note about this. First, there’s no guarantee that your network connections are being run by the kernel. Our platforms have a user-space networking stack and Network framework will choose that over the in-kernel stack in many common cases. Second, I’m concerned about this concept of “assembling bytes”. In general, UDP datagrams shouldn’t be fragmented and thus there’s no assembling of data at all. A packet arrives, it contains the full UDP datagram, and the content of that datagram is delivered to you. If you’re building something that does fragment UDP datagrams — that is, it sends datagrams that are larger than the path MTU and thus are subject to IP fragmentation — then it’d be better to work on not doing that rather than trying to worry about optimising this path. Moreover, even