“eskimo”

[quote='825151021, eli-yang, /thread/825151, /profile/eli-yang'] DTS Case 102855668616 [/quote] I just wanted point out that this is not a DTS case ID [1]. Rather, it looks like a case ID from Apple Developer Program Support, aka DevPrograms. That’s good because, as I explain here, DevPrograms is the correct escalation path for this issue. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] DTS case IDs currently have 8 digits.

Since posting the above, I’ve learnt of a new issue, one that is, alas, a showstopper. There are two ways you might use Network framework for this: NetworkConnection — As I mentioned above, there’s a bug that prevents this from working (r. 175046087). NWConnection — I just learn about another bug that prevents this from working (r. 175046087). So, you can’t use QUIC with Wi-Fi Aware through either Network framework API, which means you can’t use it )-: Needless to say, this is disappointing, and we hope to fix these bugs sooner rather later. But, for the moment, there’s no way to make this work. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

You are correct that: This is memory management code. It’s trapped due to a failed assert. Consider this: (lldb) disas -a 0x00007ff821039082 caulk`caulk::alloc::consolidating_free_map::maybe_create_free_node: … 0x7ff8210390a1 <+31>: js 0x7ff8210390f9 ; <+119> … 0x7ff8210390bb <+57>: js 0x7ff8210390f9 ; <+119> … 0x7ff8210390f9 <+119>: ud2 0x7ff8210390fb <+121>: nop As you can see, the instruction at +119 is a ud2, which is the canonical trap instruction for Intel code. There are two ways to get there, which isn’t as helpful as it could be, but the difference doesn’t really matter because both traps are associated with various invariant failures. How reproducible is this? Are you debugging it based on reports coming in from the field? Or can you reproduce it in your office? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

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. No need to keep an Inner synced to Activities at run time right? Correct. Consider what happens if you need to added a wombat field to Activities: You have to add matching field to Activities.Inner. And change init?(rawValue:) to pass that value to the Activities initialiser. And change rawValue to pass the Activities value to the Activities.Inner initialiser. It’s not complex, it’s just bookkeeping. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Given that djibouti tracked this down to an issue in their code, I think it’d be worth your while doing some more investigation on your side of the fence. However, if you can create a small test project that reliably demonstrates the issue, that’d most definitely be bugworthy. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='886263022, nathan-pierce-veertu, /thread/824773?answerId=886263022#886263022, /profile/nathan-pierce-veertu'] FB22649912 [/quote] Thanks. That seems like the best path forward for this. Just to clarify: Is the problem dependent solely on the version of the guest? For example, if you try macOS 26.4 host with macOS 26.5 beta guest, do you still see the problem? Does this only affect your VM product? Or can you reproduce it with other common Virtualization-based apps? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='824896021, rbmanian75, /thread/824896, /profile/rbmanian75'] Is it possible to add shared folders to running VZVirtualMachine [/quote] Yes. Quoting this doc: The VZDirectoryShare on the configuration defines the host directories to expose to the guest. To limit or expose new directories to the guest while the VM is running, you can update the directory share with VZVirtioFileSystemDevice. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

There are definitely limitations here, but there may also be workarounds. See this thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’d like to clarify what you mean by this: [quote='824825021, Habichtsberg, /thread/824825, /profile/Habichtsberg'] I tried AppDelegate applicationWillTerminate … and it works perfectly to wrap up the LiveActivity [/quote] So your -applicationWillTerminate: method is getting call, right? [quote='824825021, Habichtsberg, /thread/824825, /profile/Habichtsberg'] But it does not save the Audio [/quote] Isn’t that a ‘you’ problem? I mean, the system has notified you of termination, and that’s its job done. If you don’t correct save the audio, that’s something for you to debug. Right? Or am I missing something here? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I suspect you’re deadlocking against your self. Consider the crashing thread backtrace: 0 libdispatch.dylib … _dispatch_once_wait.cold.1 + 196 1 libdispatch.dylib … _dispatch_once_wait + 60 2 ChronyControl … AppDelegate.menuWillOpen(_:) + 488 … 43 ChronyControl … one-time initialization function for shared + 36 44 libdispatch.dylib … _dispatch_client_callout + 16 45 libdispatch.dylib … _dispatch_once_callout + 32 46 ChronyControl … AppDelegate.applicationDidFinishLaunching(_:) + 472 Frame 46 is called dispatch_once for something called shared (as indicated by frame 43). That runs through a bunch of logic and eventually gets to frame 2, which is calling dispatch_once again. I suspect it’s doing it for the same shared value, and hence the crash. And both frame 46 and frame 2 are your code. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='824806021, LootyPool, /thread/824806, /profile/LootyPool'] Apple Development: Joseph Salmond (67P4AAZ5TA) [/quote] That 67P4AAZ5TA value is not your Team ID. Apple uses those 10-character codes for lots of different things, and you’ve conflated two common use cases (Team ID and Team Member ID). I explain this in more detail in Code Signing Identifiers Explained. If you want to confirm this, check the Organisational Unit field of the certificate. You’ll see it has your Team ID in there. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I don’t think there’s a good way to do that. I’m not even sure how that’d work, because the only info you can extract from the key is the public key bits, and there’s nothing special about those. Realistically, you need something like App Attest, to give you a signal that the device as a whole can be trusted. Sadly, that’s not available on macOS. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='824780021, JensAlfke, /thread/824780, /profile/JensAlfke'] how can I add custom headers to the HTTP request, like authorization or cookies? [/quote] You can set additional headers using nw_ws_options_add_additional_header (C) or the setAdditionalHeaders(_:) method (Swift). [quote='824780021, JensAlfke, /thread/824780, /profile/JensAlfke'] how to get a meaningful error if the server rejects the HTTP request [/quote] This has come up before, without a great result. See this thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’ve talked to a bunch of differents who’ve seen this problem, and I’m recommending that we focus our conversation on this thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

This keeps coming up, so there’s clearly some sort of problem here. We’re using FB17032197 to track that, but I’ve no info to share as to if and when that’ll be resolved. If you’re having this problem, I encourage you to file a bug with the details and suggesting that it be marked as a duplicate of FB17032197. That’ll have a couple of benefits: If FB17032197 gets fixed, you’ll be notified. The list of duplicates will help the Apple folks involved understand the scope of this issue. On the workaround front, I recently came across an interesting option for this, namely to change the Mach service name during every update. It’s kinda like the idea I talk about in my previous post, but it gets around the objection that I mentioned there, namely, you only need a single service name for any given version of the product. If you’re hitting this issue a lot, it might be worth exploring that option. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @