Also, in the second resource (StackOverflow question+answer) the guy who answered - referred to the above "customizing_the_appearance_of_notifications" as "iOS only, not available on MacOS" - but he didn't say why he thought that.

Wow, THANK YOU! Could you please add few more details ? In what doc/TechNote - can I find these facts (what's supported and what isn't)? dev. on the basis of guess-work is slow and inefficient. Your suggested 2-point design allows POLLING on status, which is what I try to eliminate via two-way connection. Currently I maintain "named" service one-way + unnamed back-connection, but keeping the pair alive is tricky and error-prone. NSProgress? bi-directional? How!?

I bow to DTS god. Thank you so much. As a person who bought and read the full original "Inside Macintosh" series, I got spoiled early on, believing in Apple Documentation, and its completeness of description. Each subsystem, from "conceptual" to "programming tasks" to "reference". Nowadays I simply can't find the information anymore, and much of the remaining information is deemed "deprecated", "retired", "archives" and other words describing neglect. Thank god YOU still remember.

Supporting: BOOL accessibilityPermissionsGranted = AXIsProcessTrusted(); checks app can use Accessibility APIs on other apps, while [[UNUserNotificationCenter currentNotificationCenter] getNotificationSettingsWithCompletionHandler:^(UNNotificationSettings * _Nonnull settings) { BOOL TCCGranted = (settings.authorizationStatus == UNAuthorizationStatusAuthorized); }]; tells app can send user notifications. APIs exist for Camera, Microphone etc. WHY NOT FDA?

Sad to say I didn't. I found a workaround though. I added a concurrent operation-queue on which I perform the calls to [NSWorkspac isFilePackageAtPath:] I also Implemented an "Asynchronous NSOperation" for my main ES evaluation, that supports a timeout (based on the ES deadlines). My AUTH event handler asynchronously dispatches [NSWorkspac isFilePackageAtPath:] and blocks awaiting result - up to my timeout. Now my ES client is never kicked.

Hi, sorry to interrupt, but for me - this doesn't run even on a Mac (Ventura 13.6.6 + Xcode 14.0 (14A309)) It runs - but yields no log entries (empty 'entries'). I also tried an Obj-C form of this - with same results. I choose to "run as root" in the debug scheme of Xcode. It's a "command line tool" simple project, signed "Mac Development".

I now found out that this restriction (single reply-block that must be the last argument) also rule out any XPC protocol method that has variadic argument list... like (instancetype)stringWithFormat:(NSString *)format, ... NS_FORMAT_FUNCTION(1,2); because such args must also reside at the end of the definition... Yikes. Now choose between reply-block (must have one!) and variadic method (without it, my method will be SO ugly, with NSArray of optional args and so on).

Thank you so much. Could you please reveal what fts is, in which MacOS Framework it resides, and where are the headers/documentation for it? First time I hear the acronym...

But wouldn't "Persistent, system wide" permission of "Full Disk Access" cover this - to the point the "transient, process lifetime" permission won't be needed (and won't trigger the dialog) ??