“eskimo”

You asked this is the Networking Q&A and I discussed it internally with the team. Unfortunately we don’t have a good answer for you. The folks in the Q&A tend to be specialised in their specific area, so we don’t have anyone who can create a summary like this. But hey, isn’t that what LLMs are for? (-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Apple Developer Forums is primary focused on code-level questions, so we can’t really help you with issues like this. You have a couple of options here: You can seek help from Apple Support. If you think that iOS is behaving incorrectly, you can file a bug about that. For the latter, see Filing a Wi-Fi Bug Report for hints and tips about… well… filing Wi-Fi bugs. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

There are limits to how much we can answer questions like this. See tip 3 in Quinn’s Top Ten DevForums Tips. However, if you want to see the shortcut expose specific information then my advice is that you file an enhancement request outlining your requirements. If you do file a bug, please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I see you also asked this question on Swift Forums, and I’m glad that are answers were aligned (-: [quote='890992022, newwbee, /thread/829805?answerId=890992022#890992022, /profile/newwbee'] Thanks for the effort of pointing other typos and providing a working code, much appreciated!! [/quote] You’re welcome. But I should stress that my part of this is super easy. I just sit back, wait for Xcode 27 to get into beta, and then write the code in a largely functional Xcode and Swift. The folks working on this stuff don’t have that luxury. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’ll be interested to hear what other folks have to say about this. About all I can say definitively [1] is that Apple doesn’t have any tools for it. I’ve seen reports online of folks have great success using GenAI tools to help with this task, but I don’t have any personal experience I can share. However, if you search the ’net for terms like GenUI objective-c to swift you’ll find lots of hits. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Actually, maybe not definitively, because I haven’t yet had a chance to get up to speed on all the stuff we announced yesterday O-:

[quote='829491021, K. Hiroshi, /thread/829491, /profile/K.+Hiroshi'] 1- I understand that codesign is required even for static frameworks, is it correct? [/quote] No. It’s recommended, but not required. [quote='829491021, K. Hiroshi, /thread/829491, /profile/K.+Hiroshi'] 2- Should I update the distributed files when the certificate expires? Does this depend on whether it is static or dynamic? [/quote] One of my colleagues has been researching this specific, so I’m going to ask them to chime in with the details. [quote='829491021, K. Hiroshi, /thread/829491, /profile/K.+Hiroshi'] 3- When is the signature verified? [/quote] By Xcode at build time. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='830682021, gugulete, /thread/830682, /profile/gugulete'] Any plans to update them? [/quote] We can’t talk about The Future™. See tip 3 in Quinn’s Top Ten DevForums Tips. So, if you’d like to see this improve, I recommend that you file a bug against each of the samples. Please post your bug numbers, just for the record. [quote='830682021, gugulete, /thread/830682, /profile/gugulete'] What is best approach for adopting Swift 6 on such sample code? [/quote] I don’t think it makes sense to try to port the samples to Swift 6. There’s quite a substantial task. Rather, I think it’s better to extract the core concepts from those samples that are relevant to your app, and then adapt those concepts to Swift 6. If you have questions about the specifics, I’d be happy to answer them. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

CrashReportExtension and MetricKit perform very different functions, but in terms of symbolication I don’t think there’s any need for you to make a change here. In general, it’s better to symbolicate off device, which means recording a list of Mach-O image UUIDs and load addresses. MetricKit gives you that, so there’s no reason to deal with the complexities of CrashReportExtension. CrashReportExtension makes sense if you want to do something much more custom, for example, if you want to reach into the corpse (ewwww!) and extract state that’s not available in the standard crash report given to you by MetricKit. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

There aren’t any question marks in your post, so it’s not clear what your actual question is. I suspect you’re looking for feedback on your RunLoopExecutor package. If so, yeah, I’ve been down that path myself a few times and your code looks very like my first version. The biggest issue with it is that it relies on Thread being thread safe, which is not the case (much to my surprise). Hence your need for that nonisolated(unsafe). In my quest to get around that I eventually created something much more complex. Sadly, it’s still requires unsafe stuff, but I bounded that to one thing that I consider to be safe (passing CFRunLoop references between threads) and two things that I consider to be Safe Enough™ (calling CFRunLoopSourceSignal and CFRunLoopWakeUp from another thread). Needless to say I’m not really happy with that result, and that’s one of the reasons I’ve not shared my code more widely. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo +

[quote='830107021, rlaures, /thread/830107, /profile/rlaures'] Does Virtualization.framework support delegating a Thunderbolt/PCIe device to a Linux guest VM running on Apple Silicon? [/quote] No. If you’d like to see such support added in the future, I encourage you to file an enhancement request describing your requirements. Please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I hate to be the bearer of bad news but… [quote='830748021, CSJudd, /thread/830748, /profile/CSJudd'] What is the intended supported mechanism for a third-party app to save and restore window Space assignments on macOS? [/quote] As far as I know there are no APIs that let you achieve this goal. It sounds like your existing app relied on a bunch of implementation details, and those are subject to change without notice and, more importantly, without there necessarily being any equivalent replacement. [quote='830748021, CSJudd, /thread/830748, /profile/CSJudd'] Feedback: FB23017010 [/quote] Thanks for that. That’s likely to get treated as a compatibility bug, although I can’t guarantee that it will result in any changes. I also recommend that you file an enhancement request for an actual API to achieve what you’re trying to achieve. And if you do file that, please post your bug number, just for the record. Honestly, it would be good if you could go back in time and file this ER years ago, before you started down

There are many different potential causes for this, so it’s hard to offer a concrete suggestion as to why this is failing. My advice is that you debug your code to see where things are going wrong. Once you have a rough idea of what’s failing, we may be able to advice more concrete suggestions. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='830940021, rbmanian75, /thread/830940, /profile/rbmanian75'] But is there a way to merge back stacked image to base image? [/quote] No, but that would make a fine enhancement request (-: Please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

The latter. Although it’s a good idea to put your question in a relevant subtopic, add appropriate tags, and so on. I have a bunch of suggestions in Quinn’s Top Ten DevForums Tips. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I think that’s a typo. Certainly, there’s nothing about await? in the Swift Evolution proposal for this much-requested feature, namely SE-0493 Support async calls in defer bodies. Moreover, it’s not the only typo in that code. For example, it uses both fileName and filename. Here’s a code snippet that compiles with Xcode 27 beta: import Foundation class FileHandle { init(_ fileName: String) { fatalError() } func write(_ data: Data) async throws { fatalError() } func close() async { fatalError() } } func exportData(at url: URL, to fileName: String) async throws { let log = FileHandle(fileName) defer { await log.close() } let (data, _) = try await URLSession.shared.data(from: url) try await log.write(data) } Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com