“eskimo”

[quote='882312022, dopey, /thread/820940?answerId=882312022#882312022, /profile/dopey'] We are actually seeing seeing this happen in practice. [/quote] OK. [quote='882312022, dopey, /thread/820940?answerId=882312022#882312022, /profile/dopey'] it's not deterministic. [/quote] Right. It’s hard to say what’s going on without more logging, but the most likely cause is a memory pressure exit, and that’s very non-deterministic. [quote='882312022, dopey, /thread/820940?answerId=882312022#882312022, /profile/dopey'] I will open a bug and post the bug number. [/quote] Much appreciated. Ideally this would include a sysdiagnose log taken: On a device with extra CryptoTokenKit logging enabled (see below) Shortly after seeing the problem But that might be hard to get, so you should feel free to file a bug with only your ‘kill ctkd’ step as evidence. On the logging front, our Bug Reporting > Profiles and Logs only has a CryptoTokenKit profile for iOS. However, you can install that profile on macOS, and I think it’ll ju

[quote='882371022, Arebus, /thread/820871?answerId=882371022#882371022, /profile/Arebus'] I thought it would be easier to write a CLI than … [/quote] Yeah, I know what you mean, but recently I’ve moved away from that approach: For low-level stuff, I tend to put the test code into a unit test. This is just as easy to debug as a command-line tool, but it has the advantage that, as you exercise various code paths, you build up a corpus of unit tests that ensure that things continue to work in the future. For GUI stuff, I lean into Xcode’s preview feature. Or just do my experimentation in an target. And there’s Xcode’s UI testing support. I don’t use that a lot but, in my defence, UI stuff isn’t my focus. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='882274022, Davidbaraff2, /thread/820572?answerId=882274022#882274022, /profile/Davidbaraff2'] Do you know of any off the shelf VPNs that can be configured in the way you describe? [/quote] No. But my expertise is in VPN APIs, not VPN products. [quote='882274022, Davidbaraff2, /thread/820572?answerId=882274022#882274022, /profile/Davidbaraff2'] If you could point me [at code to] open sockets that will only use cellular [/quote] To start you off: Extra-ordinary Networking > Network Interface Techniques > Binding to an Interface explains how to bind a socket to a specific interface. Extra-ordinary Networking > Network Interface APIs > Network Interface Type explains how to identify the WWAN interface. [quote='882274022, Davidbaraff2, /thread/820572?answerId=882274022#882274022, /profile/Davidbaraff2'] We have total control of our local network. [/quote] So what happens if you don’t deploy a DHCP server on that network? I would expect that you’ll still be able to communicate with your iPads us

[quote='821109021, JTechHyd, /thread/821109, /profile/JTechHyd'] Are there known issues with aggressive optimization (-O) affecting … ? [/quote] Yes. If you’re using a C-based language it’s very easy to rely on undefined behavior, and the exact behaviour you get can change based on the optimisation level, the compiler version, the OS version, and so on. This is true in safer languages as well, but it’s less common. For example, Swift is generally safer than C but there are still sources of undefined behaviour, including unsafe pointers [1] and concurrency [2]. Is sounds like you’re building this third-party library from source. Is that right? If so, you can dig into the library to see if you can isolate the cause of the problem. This is no different from tackling a hard-to-debug problems in your own code. You can use both build-time tools (like the Clang static analyser) and runtime tools (like the standard memory debugging tools). It’s also possible for problems like this to be caused by bugs in the compiler

[quote='821027021, Pavel, /thread/821027, /profile/Pavel'] For debugging purposes, I am trying to run the daemon's executable directly from the terminal [/quote] This won’t work. For your launchd daemon to work correctly, it must be started by launchd. I explain why that’s the case in XPC and App-to-App Communication. My general advice for debugging a launchd daemon is: Structure your code so that you can do most of your debugging in unit tests, rather than in your daemon. That’ll make your life much easier. To unit test your XPC code, use the technique in TN3113 Testing and debugging XPC code with an anonymous listener. To debug integration issues: Using LLDB’s --wait-for option to attach to the daemon shortly after it starts. There’s a similar option in Xcode, under Debug > Attach to Process by PID or Name. Or if you absolutely need to debug from the first instruction, add the WaitForDebugger property to your launchd property list. See the launchd.plist man page for details. [quote='821027021, Pavel, /th

froglike6, It’s not clear whether your response was addressed to me or Skygreed. If it’s for me, be aware that my comment above was purely administrative. Skygreed added a reply to your thread, so I wanted to make sure that anyone finding this thread was aware of their thread. As to the technical aspects of this issue, and similarly for Skygreed’s issue, I’m not the right person to address that. I don’t have any in-depth experience with HID stuff. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

How are you distributing your programs? Directly, using Developer ID signing? Or via the Mac App Store? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

NWConnection is quite generic, so you shouldn’t be surprised that not all of its options make sense for all connection types [1]. However, in this case the .waiting state does make sense for UDP. Consider a connection created like this: let connection = NWConnection(to: .hostPort(host: example.com, port: 80), using: .udp) If you run this on a device with Airplane Mode enabled, the connection will enter the .waiting state. That’s because it’s waiting for DNS to come online so that it can resolve example.com to find out what addresses it should attempt to ‘connect’ to. But that’s just an example. I suspect that are a number of other cases where you’ll see this. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] The new NetworkConnection API improves this situation, using the Swift type system to vary the operations supported on the connection based on the underlying protocol. However, there are limits to how much you can imp

The 3 in that error is KERN_NO_SPACE, which is a pretty clear indication that the system memory allocator asked for address space and the kernel refused to give it. However, given all the constraints you’ve described, it’s not at all clear why that would be. Weirdly, the code that traps this way is not on the main branch of the Darwin open source, but I found a copy in the rel/libmalloc-792 branch [1]. Now, I don’t have time today to study that code in depth, but I figured you’d find it interesting (-: AFAICT it tries to allocate address space by using mach_vm_map to map MEMORY_OBJECT_NULL, specifying a start that’s after 16 GiB, such that it fits within 64 GiB, with a randomly applied offset. That random bit probably explains why this shows up so infrequently. It’s hard to say why this is failing. You might be able to learn more by running vmmap against the dying process. It’d also be interested to know what address was passed to mach_vm_map (with reference to the source, that’s the ptr_addr value), somethin

MetricKit definitely works on macOS. I’m not sure about how it interacts with Network Extension processes. Let’s start with some basics: Is your NE provider packaged as an app extension or a system extension? If it’s an sysex, are you distributing it directly? Or on the Mac App Store. TN3134 Network Extension provider deployment talks more about NE provider packaging and deployment options. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Coming back to your throughput issue, let me start with a general comment and then return to the specifics of your case. In general, the on-the-wire behaviour is going to vary based on the performance mode: Realtime Bulk In the realtime mode (WAPerformanceMode.realtime), the behaviour is described by Figure 53-1 and its associated text in the Accessory Design Guidelines for Apple Devices, available from Developer > Accessories. In bulk mode (.bulk) the behaviour is adaptive, with allocations ramping up as there’s more traffic. Regarding your specific case, my understanding is that you’re in conversation with other folks at Apple about your product. I can’t discuss those details here on the forums, because this is a public environment. However, those folks asked me to remind you that the were hoping to get some logs from you. The best way to submit those is via Feedback Assistant. Once your done, post your bug number here and I’ll pass it along. Oh, and I also wanted to remind you about filing an ER against

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. Regarding the Stack Overflow thread you referenced, I’m not convinced that the alert is being shown by Apple code. I think that’s related to the third-party tooling involved. Which brings me back to your question. Without knowing which Apple API is involved, it’s hard to be sure whether this alert is coming from the OS or your third-party library. So you have a choice: You could dig into the library yourself to see what it’s going. Or you could discuss this with the library vendor. Alternatively, if you can post a screenshot of the specific alert, I might be able to track it down the Apple side of this [1]. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Assuming the library isn’t trying to deliberately copy the appearance of an Apple alert, which is something I do encounter from time to time.

Glad to hear you’re making progress. [quote='882117022, i12n, /thread/820580?answerId=882117022#882117022, /profile/i12n'] What's the documented behavior if the user has something actively playing on the system music player? [/quote] Sadly, I can’t help you with that. I waded into this thread because I have expertise in the entitlement side of things. Otherwise I’m a complete noob when it comes to MusicKit. I have a couple of recommendations: As I mentioned above, prototype stuff in Xcode, just to get your third-party tooling out of the mix. If you continue to have problems, start a new thread, using the same subtopic and tags as their thread (well, except for Entitlements). Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='882180022, Pavel, /thread/820631?answerId=882180022#882180022, /profile/Pavel'] will macOS automatically bootstrap this Network Extension at boot-time [/quote] Yes. [quote='882180022, Pavel, /thread/820631?answerId=882180022#882180022, /profile/Pavel'] Is there ever a valid use case where these roles should be reversed … ? [/quote] It depends. There are some things that are most definitely problematic. For example, in macOS’s layered architecture the client can’t be ‘below’ the server. For example, you can’t have a daemon client connect to an agent server, or an agent client connect to a server within an app. You’ve already highlighted one key reason why this is problematic: A daemon can run when no user is logged in, so there might be no agent to connect to. Similarly, you can have multiple login sessions, so the connection could be ambiguous. Now in your case you have a daemon and a NE sysex. The latter acts very much like a daemon. Specifically, it runs in the same global context as a launchd daemo

[quote='882177022, hbanzon, /thread/797959?answerId=882177022#882177022, /profile/hbanzon'] I just renewed my paid developer account today [/quote] This thread is about free provisioning, which Xcode displays as a Personal Team. The story for paid teams is different. My general advice is that you read through Developer Account Help > Devices. If that’s not sufficient, you can seek help via Apple > Developer > Contact Us. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com