eskimo

[quote='808875021, dhoelzl, /thread/808875, /profile/dhoelzl'] Am I missing something? [/quote] Other than that certificate revocation checking is a tangled mess? No )-: I’ll likely have more to say about this in a bit — I’m just checking on some details internally — but I wanted to reply now and ask about your high-level goal here. Why are you doing explicit revocation checking? What behaviour in your product will change based on the result? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='867992022, pepipox, /thread/808699?answerId=867992022#867992022, /profile/pepipox'] The whole concept already works if launched from Xcode as root. [/quote] Running code as root from Xcode is very tricky. It puts you in a mixed execution context, where you’re running as user ID 0 but your non-BSD execution context is that of the GUI login session. Weird things happen in that case. In this case those weird things seem to be beneficial, but in reality they’re just misleading )-: [quote='867992022, pepipox, /thread/808699?answerId=867992022#867992022, /profile/pepipox'] My idea is that the user launches some app [/quote] If you have a GUI app and you’re using Personal VPN, why not call NEVPNManager directly from it. Why do you need these extra running-as-root bits? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Right. You certainly have a bunch of options for that, but it’s hard to say exactly which one is best. For example, I played around with the -all_load flag and it seem to do pretty much what you wanted. However, that’s a really heavy hammer, in that it pretty much disables all dead stripping. Whether that matters depends on your exact circumstances. Again, I recommend that you read the ld man page to learn more about these options. It’s terminology is… well… dense, so you might want to avail yourself of An Apple Library Primer. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='868001022, Hylus-Arbor, /thread/808897?answerId=868001022#868001022, /profile/Hylus-Arbor'] maybe the Accessibility is compromised in the same way with 26.1 [/quote] Yes. This bug seems to affect a wide range of privileges controlled by System Settings > Privacy & Security. I haven’t explored the full list, but others have noticed that it also affects Screen & System Audio Recording, so it wouldn’t surprise me if it affected Accessibility as well. [quote='868001022, Hylus-Arbor, /thread/808897?answerId=868001022#868001022, /profile/Hylus-Arbor'] I updated my own Mac from 15.7 to 26.1. [/quote] My recommendation is that you test this stuff in one or more VMs. That way you have direct control over what system software is installed, and you can revert to a known ‘clean’ snapshot between each test. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

The only DTLS APIs on iOS are those in Network framework. But you’re not using that, right? Rather, you’re using BSD Sockets? Presuming that, there are at least two layers between the system delivering a UDP packet to the socket buffer and you receiving a DTLS message. Specifically: You have to implement some sort of mechanism to learn about data arriving on the socket. You can do this using select, kqueues, Dispatch sources, and so on. You have to implement DTLS on top of UDP. A failure at either of these levels could result in the problem you’re seeing. Given that, my advice is that you try to set up a test case that eliminates them. First, use an RVI packet trace to ensure that the packet was actually delivered to the iOS device. IMPORTANT It’s possible that this RVI setup might mask the issue. If that’s the case, lemme know, because it would be an interesting data point in and of itself. Next, get DTLS out of the picture. Just for testing purposes, set up a simple UDP echo server and ping it on the VoIP w

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. I notice that when a wired network adapter is connected, an additional network interface named enX appears Yep. there are other network interfaces also named enX affect my judgment. Right. This boils down to how you distinguish between different interfaces types. I have info about that in Extra-ordinary Networking > Network Interface APIs > Network Interface Type. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’m glad to hear you’re making progress here. [quote='868028022, MoLotus, /thread/808485?answerId=868028022#868028022, /profile/MoLotus'] The only obvious difference … is the passing of the constant integer to the constructor [/quote] I dug my test project out of the trash and removed those priority values. It still exhibits correct behaviour [1]. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Although the order of foo{,Waffle} and bar{,Waffle} lines were swapped.

[quote='868011022, chrismuench, /thread/769472?answerId=868011022#868011022, /profile/chrismuench'] it is clearly still a bug in Xcode 26 [/quote] Absolutely. There’s no argument about that. [quote='868011022, chrismuench, /thread/769472?answerId=868011022#868011022, /profile/chrismuench'] which leads to deployment failure from my Visual Studio on my PC. [/quote] With Xcode, you don’t need to explicitly install the profile because the system picks it up from the embedded.mobileprovision file embedded within the built app. I don’t know enough about how Visual Studio builds and installs apps to offer any insight into why that’s not working for it. My advice is that you escalate this via the support channel for that tooling. ps 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. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='809007021, veer_dutta07, /thread/809007, /profile/veer_dutta07'] do we need to wait for the cancellation of these pending receives? [/quote] This is very much like my answer on your other thread about listeners: The system doesn’t care, but there might be reasons for you to care. The connection will hold a strong reference to your receive closure until it calls it. After that, it will release that reference. If the closure references the connection, which is very common, then that forms a retain loop. However, that’s not a problem because, in general, you shouldn’t rely on releasing the last reference to cancel the connection. Rather, you should call cancel() on it. That’s guaranteed to complete all the outstanding receives which breaks any retain loops they might’ve formed. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='867955022, veer_dutta07, /thread/808957?answerId=867955022#867955022, /profile/veer_dutta07'] I might not be able to open the listener on the same port because it is still busy [/quote] Right. That’s what I meant by “bad things might happen” in my previous post. [quote='867955022, veer_dutta07, /thread/808957?answerId=867955022#867955022, /profile/veer_dutta07'] are there any implications other than this? [/quote] Probably. The one that springs to mind relates to Bonjour service advertisement, but I wouldn’t be surprised if there were others that I’ve not thought of. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

premak, Thanks for helping out here! Earlier I wrote: [quote='865550022, DTS Engineer, /thread/806222?answerId=865550022#865550022'] I recommend that you recheck FB20929578 in a few days time. [/quote] I was being deliberately cryptic there because I wanted to see what was officially shared before I made any comments here on the forums. Now that that’s happened, I can talk about the resolution. FB20929578 was resolved as not to be fixed. It’s unusual for us to ‘break’ existing software products [1] like this, so it’s not something we do lightly. In this case, the motivation for the macOS 26.1 change was to address a security vulnerability. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Well, in this case it’s the installer package, not the software itself, but that’s a distinction without a difference.

[quote='867976022, artur1986, /thread/803413?answerId=867976022#867976022, /profile/artur1986'] To this day, I haven't received a single response from Feedback Assistant. [/quote] That’s not unusual. In general, you’ll only hear from Feedback Assistant if they need more info or when the issue is resolved. That’s what happened here, modulo the delay caused by the above-mentioned holiday. [quote='867976022, artur1986, /thread/803413?answerId=867976022#867976022, /profile/artur1986'] Who should I contact to get this information? [/quote] I don’t have any suggestions for you here (if I had, I would’ve included them in my previous email). The information you’re looking for relates to Apple internal processes and we generally don’t talk about those publicly. I’m sorry these aren’t the answers you’re looking for, but they are the only answers I have. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='867979022, teapeagee, /thread/808618?answerId=867979022#867979022, /profile/teapeagee'] Apple still need to remove Ruby 2.6 though [/quote] Unfortunately it’s hard to do without breaking folks. We actually talk about this in the macOS Catalina 10.15 Release Notes. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

FB21232935 Thanks! ps 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. This duplicate comment brought to you … Indeed. Sorry about that. It’s a known issue with the comment system (i. 98940414)-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. For lots of additional info about notarisation, see Notarisation Resources. Specifically, it links to a Q&A with the notary service team that’s quite instructive. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com