eskimo

[quote='874018022, Retouch, /thread/813562?answerId=874018022#874018022, /profile/Retouch'] The error … is just a symptom. [/quote] Right. But: We’re not 100% sure whether it’s a symptom of a bug in your code or a bug in the OS. Even if it’s the latter, the proximity of this error to that failure is useful diagnostic point. My suggestions above should allow you to rule out this being a bug in your code — or at least an ‘obvious’ bug — and generate diagnostic information that will be useful for Apple’s network engineering team to investigate. Now, if you want to file a bug about this now, that’s cool. However, my experience is that weird networking bugs get more traction if you: Provide clear evidence that the issue originates in the system, as opposed to your code. Include a sysdiagnose log with NE logging enabled. Note If you do file a bug, please post the bug number, just for the record. [quote='874018022, Retouch, /thread/813562?answerId=874018022#874018022, /profile/Retouch'] My concern is that the machin

OK. So, there’s no way for your code to plug-in to the VPN On Demand engine. You can configure various parameters that affect its behaviour, but that’s it. This makes sense when you think about it: Your container app is not necessarily running when the VPN On Demand engine does its evaluation. The VPN On Demand engine is what causes the system to instantiate your NE provider, and so your NE provider can’t change the engine’s decisions because it’s not yet running. Note Having said that, such an ability would be cool. If you get to the end of your current investigation and decide that the current setup is insufficient for your needs, you should feel free to file an enhancement request describing your requirements. And if you do that, please post your bug number, just for the record. With that in mind, let’s coming back to your requirements. Earlier you wrote: [quote='873905022, pawanquantum, /thread/813746?answerId=873905022#873905022, /profile/pawanquantum'] we want is to allow the user to manually disconnect

Yay! And thanks for testing this so promptly. I really appreciate it. But just to head off the inevitable follow-up questions: No, I don’t have any information to share as to when the final release of 26.3 will ship. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Your profile isn’t constructed correctly. The Enable-Private-Data is meant to be nested within a System dictionary: System Enable-Private-Data IMPORTANT Don’t enable all private data on a system you care about. While Apple strives not to log anything too precious, it’s hard to guarantee that. I usually do this sort of testing in a ‘victim’ machine. Typically that’s a VM, although that might be challenging given that you’re developing an audio accessory. 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. It works on macOS Cool. is it also possible on iOS? Core WLAN is not available on iOS. For a list of Wi-Fi APIs that are available in iOS, see TN3111 iOS Wi-Fi API overview. I don’t think that any of these return the information you’re looking for. The nearest that I can think of is fetchCurrent(completionHandler:), which returns some details, like the security type, but no channel info. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

OK. But you have the code for the PIRProcessDatabase tool, right? So how about you step through it to see where it throws this error? Keep in mind that PIR Service Example isn’t a set of tools, like Xcode, where you’re limited to just running the tool and that’s that. Rather, it’s sample code for you to explore, and then use the results to inform the development of the server-side of your system. 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. Notarizing the app fixes it Yay! why make them two separate things? There are a bunch of reasons: Code signing has been relevant since Gatekeeper was introduced. Notarisation is a new thing. Code signing is relevant for day-to-day development. Notarisation is only relevant during deployment, and then only when deploying directly, rather than via the App Store. Developer ID code signing, which is primarily for distribution, is still useful without notarisation, for example, allowing you to test your final distribution build prior to notarisation. Notarisation is an online process while code signing is not [1]. That introduces significantly higher latency. Notarisation is generally pretty fast, but it’d be annoying if you had to notarise every time you hit Product > Run. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo +

[quote='873991022, OC_s, /thread/813853?answerId=873991022#873991022, /profile/OC_s'] HomeKit API available amongst the native macOS APIs [/quote] Hmmm, yeah, that certainly seems to be the case. How weird. I don’t support HomeKit, so I’m gonna ask DTS’s resident expert if they have any context for that. Anyway, given that your app is focused on HomeKit, that definitely forces you to use Catalyst. [quote='873991022, OC_s, /thread/813853?answerId=873991022#873991022, /profile/OC_s'] just wanted to save it for possible further interest [/quote] OK. Assuming that you’re only saving it locally. If you’re uploading it somewhere, comments like that definitely set off privacy alarm bells |-: Anyway, with that context let’s look at each of these properties. The name property returns the user-assigned device name. Honestly, I don’t think you should capture this because it’s privacy sensitive. In many cases it’s something like “Eric’s MacBook”. In this respect, Mac Catalyst follows iOS, in that it returns a placeholder

[quote='874020022, dileepachandrasekara, /thread/813571?answerId=874020022#874020022, /profile/dileepachandrasekara'] Are internal comments visible to the reporter … ? [/quote] Yes. If the engineers working on the bug need to get in touch, they can do that via Feedback Assistant. But I don’t need to do that because I can just reply here (-: so my comments on the bug were for them, not you. [quote='874020022, dileepachandrasekara, /thread/813571?answerId=874020022#874020022, /profile/dileepachandrasekara'] Is this the method you were referring to ? [/quote] Yes, but it’s only on NSString, not String. So this fails: let s = Hello Cruel World!.txt let s2 = s.deletingPathExtension // ^ Value of type 'String' has no member 'deletingPathExtension' Instead you have to do this: let s2 = (s as NSString).deletingPathExtension All very suboptimal )-: [quote='874020022, dileepachandrasekara, /thread/813571?answerId=874020022#874020022, /profile/dileepachandrasekara'] would using NSString methods be the more semantically

I’ve been looking for an excuse to explore log quarantine in more depth, so thanks for asking this (-: The logging subsystem definitely has knobs you can twiddle here, but it’s not clear how many of them actually work on the public releases of macOS. I’m gonna do some research and get back to you. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

The inability to add a standalone executable to System Settings > Privacy & Security is a known regression in macOS 26.1. It’s fixed in our 26.3 beta seeds. See this thread for a lot more backstory. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

My general advice is that you avoid Multipeer Connectivity. I explain why, and a lot more besides, in Moving from Multipeer Connectivity to Network Framework. [quote='813963021, PellePepper, /thread/813963, /profile/PellePepper'] In real environments of athletics venues the solution is only stable in a region of about 2 meters [/quote] It sounds like you’re using it to access peer-to-peer Wi-Fi. I have three important notes on that front: Multipeer Connectivity is not the only way to access peer-to-peer Wi-Fi. I talk more about that in TN3151 Choosing the right networking API. If you just switch to Network framework, it might not actually help, because they use the same underlying Apple peer-to-peer Wi-Fi mechanism. OTOH, it might actually help because Network framework gives you great visibility into what’s happening on the ‘wire’ versus Multipeer Connectivity. We also have Wi-Fi Aware, which is a different peer-to-peer Wi-Fi mechanism. Note that Wi-Fi Aware is just there to set up the pairing, and you do th

[quote='813959021, Zaid, /thread/813959, /profile/Zaid'] FB21772424 [/quote] Thanks for filing that. And, yeah, filing a bug report is the best path forward for obvious regressions like this. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

This isn’t something we can help you with here on the forums. Rather, you need to seek help via official channels. For the details, see this post. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com