eskimo

See this thread, and specifically this post, which explains why this works in during development but fails when you deploy. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Hey Jens, it’s been a while. [quote='813998021, JensAlfke, /thread/813998, /profile/JensAlfke'] which appears to be for exactly this use case [/quote] Yep. [quote='813998021, JensAlfke, /thread/813998, /profile/JensAlfke'] my attempts always return a BadReference error (-65541). [/quote] Yeah, this is not an easy API to use correctly. There are two parts to it: Actually calling the DNSServiceReconfirmRecord API. Deciding what record data to pass in. That kDNSServiceErr_BadReference error suggests you’re having problems with the first step, not the second. Regardless, I have suggestions for both of these in this post. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I admire your dedication to this task! It’s hard to offer definitive advice without knowing more about how FileMaker loads plug-ins, but I suspect you’re being blocked by library validation. I downloaded that plug-in and took a look. First, I confirmed that it’s based on native code: % file BaseElements.fmplugin/Contents/MacOS/BaseElements BaseElements.fmplugin/Contents/MacOS/BaseElements: Mach-O … bundle … Next, I looked at its code signature: % codesign -d -vvv BaseElements.fmplugin … Authority=Developer ID Application: Goya Pty Ltd (GUZF844KMZ) … If your runtime is loading this is the traditional manner — that is, loading the plug-in bundle into your process’s address space — then library validation is an issue. Specifically: To distribute your app directly, you must notarise it. Notarisation requires the hardened runtime. The hardened runtime enables library validation by default. Library validation ensures that your app’s process will only load code signed by Apple or by your team. So, your app tries to

Thanks for opening a forums thread about this. [quote='813973021, TChrist, /thread/813973, /profile/TChrist'] More details can be found on the Feedback with the ID FB21649104 [/quote] And thanks for filing that. Based on the analysis in that bug report, my understanding is that: This is a known issue. We believe it’s fixed in macOS 26.3 beta. Please try reproducing this with the latest 26.3 beta seed and let us know how you get along. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Blah. Sorry about not replying earlier. You replied as a comment and it’s easy for me to miss that )-: See Quinn’s Top Ten DevForums Tips for this and other titbits. Anyway, I hope you attended despite not receiving a reply here; it was a fun (virtual) event. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I don’t have an answer for you, alas, but I encourage you to follow this thread because, if anything changes, I’ll post an update there. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

FYI, I’m concentrating discussion of this issue on this thread. If anything changes, I’ll post an update there. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

The sticking point here is that we don’t have a Swift Playground app that supports the iOS 26 SDK. I’m covered that issue on this thread. If anything changes on this front, I’ll post an update there. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

See my response in your specific thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I don’t have an answer for you, alas, but I encourage you to follow this thread because, if anything changes, I’ll post an update there. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I just wanted to update this thread to cover two points: This is being discussed internally, but I still don’t have any info to share as to how/when/if it might be resolved. Sorry. I’m going to use this thread as the ‘lead’ thread for this issue. If and when there’s news, I’ll post an update here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I don’t have time to try this for myself today, but my understanding is that this problem (r. 164272589) is resolved in the latest macOS 26.3b3 (25D5112c) seed. If you have access to beta seeds, I encourage you to try this for yourself and reply here with the results. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’ve found that it’s quicker to resolve archiving issues when we share small working examples. To that end, I took the BorderModel and FrameModel classes from this post and wrote the following code to exercise archiving and unarchiving: func main() throws { let borderModel = BorderModel(showBorder: true) let models = [FrameModel(count: 1), FrameModel(count: 2)] let archiver = NSKeyedArchiver(requiringSecureCoding: true) defer { archiver.finishEncoding() } archiver.encode(borderModel, forKey: borderModel) archiver.encode(models as NSArray, forKey: models) let archive = archiver.encodedData let unarchiver = try NSKeyedUnarchiver(forReadingFrom: archive) defer { unarchiver.finishDecoding() } assert(unarchiver.requiresSecureCoding) guard let borderModel2 = try unarchiver.decodeTopLevelObject(of: BorderModel.self, forKey: borderModel), let m = try unarchiver.decodeTopLevelObject(of: [NSArray.self, FrameModel.self], forKey: models), let models2 = m as? [FrameModel] else { throw POSIXError(.ENOTTY) // Need a better

Thanks for all that info. [quote='873820022, dylandylandylan, /thread/813642?answerId=873820022#873820022, /profile/dylandylandylan'] apologies for my extra-long answer [/quote] Au contraire, that’s exactly the sort of info I need (-: First up, let’s talk about how the API should work. The NETunnelProviderManager APIs are asynchronous for a reason: They’re not supposed to complete until they’re done. In your first example, either one of the following should be true: Either removeFromPreferences() should not return [1] until the tunnel is closed. Or the open tunnel shouldn’t get in the way of the system establishing the new settings. The fact that you have to add arbitrary delays is clearly a bug IMO, and I encourage you to file it as such. Given that you can easily reproduce this, I recommend that you enable extra NE logging via the VPN (Network Extension) for macOS instructions on our page Bug Reporting > Profiles and Logs and attach a sysdiagnose log taken shortly after seeing the issue. Please post your