“eskimo”

[quote='877011022, Pushpak-Ambadkar123, /thread/815498?answerId=877011022#877011022, /profile/Pushpak-Ambadkar123'] will it work with WebKit as well … ? [/quote] Hmmmm, that depends on what you mean by “WebKit”. If you’re talking about WKWebView (WebView in SwiftUI) then I expect, like Safari, it’d get filter support because it loads web content using URLSession. If you’re talking about the WebKit open source project, that’s not something I support and thus I’ve not looked at it. [quote='877011022, Pushpak-Ambadkar123, /thread/815498?answerId=877011022#877011022, /profile/Pushpak-Ambadkar123'] I am trying to implement a solution that would block urls from the block list on the browsers installed on iOS device. [/quote] Can you clarify what you mean by that? But, just so we’re on the same page about Network Extension’s capabilities, it supports two scenarios: Implementing a URL filter — This allows you to block pages loaded by URLSession and anything layered on top of it, including WebKit’s web views and Safar

[quote='876864022, SwiftieDog, /thread/797007?answerId=876864022#876864022, /profile/SwiftieDog'] I know this may sound like a why question [/quote] Two points: If you think that Mac users need more warnings than they already get — keeping in mind the one presented when the app saves a VPN configuration — you are welcome to file a bug about that. If you think that Apple should document this policy officially, you can file an enhancement request against the documentation. A good place for this sort of stuff is the Apple Platform Security guide. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

It seems like you created a specific thread for this question. [This was a mistake, as explained below — Quinn, 2026-02-25] Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='816333021, agorneanu, /thread/816333, /profile/agorneanu'] Any idea what's wrong with my machine? [/quote] Oh, there are so many possibilities )-: In Testing a Notarised Product I encourage folks to do their Gatekeeper testing on a Mac that’s “never seen [their] product before”, and this is an example of why I give that advice. Development machines see many builds of a given app, including ‘broken’ development builds, and that exercises lots of edge cases in Launch Services and the trusted execution system, not all of which are handled correctly. If you create a new account on the problematic machine, does it have the same problem? Expanding on ssmith_c’s comments: [quote='876858022, ssmith_c, /thread/816333?answerId=876858022#876858022, /profile/ssmith_c'] Check the system log to see if there are any further details on the reasons why. [/quote] I have lots of general hints and tips about the system log in Your Friend the System Log, and trusted execution specific stuff at the end of Resolving Trusted

Lemme see if I understand you correctly: You submit a notarisation request with notarytool submit. While the request is in progress, you can see it in the notarytool history list. At some point it disappears from that list. Presumably this is when the notarisation request completes, but it’s hard to be sure about that from the outside. Once that happens, you can no longer get info about that request using notarytool info. Is that right? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Please file a bug about this, making sure to attach a sysdiagnose log taken shortly after reproducing the problem. Once you’re done, post the bug number and I’ll pick things up from there. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

First up, please re-test to confirm that you’re still having the problem. The notary service is quite reliable IME, and when I do see errors like this they often get fixed based on internal monitoring. If you confirm that you’re still having the problem, please file a bug about it and then post the bug number here. Finally, I often find that folks can work around issues like this by switching from app-specific password authentication to key-based authentication. So, in addition to filing that bug, you should try that switch to see if it can get you back notarising again. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='816507021, EdwardD20, /thread/816507, /profile/EdwardD20'] how would that be passed to WeatherKit? [/quote] I don’t think there’s any way to do that. [quote='816507021, EdwardD20, /thread/816507, /profile/EdwardD20'] The only thought I have is that they would need to compile the code on their own … [/quote] Right. Now, compiling things from scratch can be a bit of a pain, so another option would be for you to distribute an unsigned app and have folks re-sign it. However, that’s tricky because the WeatherKit service is tied to your App ID, which is in turn tied to your bundle ID. So it’s not just a case of re-signing the app. There’d have to be some process for customising the bundle ID and then re-signing. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I just posted a response on your other thread that clarifies our position here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I want to clarify the overall situation here. The Apple Developer Forums are primarily focused on helping developers with Apple APIs, developer tools, and so on. We’re not really set up to help folks with ‘user-level’ questions, even those from advanced users like yourself. For that, I recommend that you bounce over to Apple Support Community, run by Apple Support, and specifically the Business and Education areas. Questions like this fall into two categories: Developers who are trying to create products based on macOS’s built-in services. Users who are trying to configure those services. From a developer perspective, the presence of built-in services, in this case Postfix, is considered an implementation detail, not an API. If you want to build a product that runs a mail server, you should embed your own copy of Postfix rather than relying on the built-in one. And if you want to run that as a daemon, it will naturally have a different launchd job label. From a user perspective, it’s fine to use these built-i

You’ve structured your post like a bug report, so I want to make sure you understand the role of Apple Developer Forums in that case. Our primary focus here is helping folks write code using Apple APIs, use Apple developer tools, and so on. If you want to file a bug, the correct place to do that is Feedback Assistant. So, if you haven’t already filed a bug about this, please do that now. Once you have a bug on file, please post the bug number here, just for the record. For lots of info about the bug reporting process, see Bug Reporting: How and Why? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Hmmmm, if multiple folks are hitting this [1] then it’s clearly not a client-side problem. Given that, I’m going to tweak my advice somewhat. In addition to seeking help via the channel I described above, I also recommend that you report this as a bug against the Developer website. Once you’re done, please post your bug number, just for the record. IMPORTANT Normally I recommend against filing ‘me too’ bugs, but in this case I think that’s warranted [2]. noyna, froglike6, and others, please file your own separate bugs and post the bug numbers here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Indeed, I just saw another thread about it. [2] Because I want to make sure we capture the full breadth of the issue.

You’re not the first person to hit this. See this thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='874040022, DTS Engineer, /thread/812429?answerId=874040022#874040022'] If and when there’s news, I’ll post an update here. [/quote] I’ve been closely following this issue internally. Unfortunately, I don’t have any good news to share. And given that submissions close in less than a week, I think the only reasonable option is for you to develop your submission based on the current choices, namely: Swift Playground 4.6.x as it’s currently shipping Xcode 26 or later, with the submission running in the simulator I’m sorry I don’t have better news )-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Your submission can rely on iOS 26 features. However, that does mean that you’ll need to choose the Xcode option when submitting, because Swift Playground doesn’t currently support the iOS 26 SDK. Regarding that last point, I wanna point you at this thread, where I’ve promised to post updates if and when they occur. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com