Thanks for the reply: the good people of Stack Exchange fixed it (but then told me to delete the question as not being as good fit for the site....) In short: the way Timer.scheduledTimer is used has changed***. Someone supplied me with a different formula for using it, and that seems to have fixed it. I removed the sleep, and it seems to not be a problem without it. Anyway, the leak is fixed. *** What do you want to change things for? Things are bad enough as they are!

OK, Apparently, you need to add a "Package.swift" file with some boilerplate, but the Package Manager doesn't do that when it adds a package to your project.

If I copy the Argument Parser Frameworks from the Build folders to /Library/Frameworks, then my executable CLI tool works without error. But obviously, I want to build one executable, without having separate components to install and maintain. How do you embed the Package in the executable?

ArgumentParser is listed in the Sidebar under Package Dependencies, but it's not under Frameworks. Should it be? Also, assuming I get it working, am I going to embed all the example code and documentation in my CLI tool? I'm on Ventura 13.2 beta and Xcode 14.1, btw.

One other thing which might be relevant: under Target > General > Frameworks and Libraries, I have the Argument Parser listed, but the "Embed" status is empty. I can't find a way to alter that.

This is still broken in Ventura. If I remember correctly, the function did return in Monterey, briefly. But I still can't get any executables to run as PDF Services. I've tried compiling Swift scripts and 'signing' them in various ways; python3 scripts; Automator applications, etc, etc. They all work fine when called outside of the print service.

That font is installed on every Apple OS, so you can reference it without bundling it in your app. Just assume that it will be available.

File a report, and restore the previous release / build. You could check all the relevant security settings have been granted to all relevant processes.

Ah: Number 1 is pretty straightforward, using the viewWillDisappear method, to add a stop command. Still can't find anything about the 2nd question.

OK, I need to change the Scheme, under Product menu, to get the app to build again. I was having a nightmare with build settings, but that seems to have calmed down.

"normally domain should not be nil (you risk a crash in filters)" What should it be? "you get the same result, because of the cast as!." The same result as what? "Result is optional, but cannot be nil, it is forced unwrapped" If it cannot be nil, then why does it need to be optional? And why is it Any, and not 'actual' QuartzFilter? And what about the two different types of property? In your function, the result is a force unwrapped Any -- so why does it return an Optional? I guess this is just a complaint about the way that Apple has chosen to do things, which doesn't really seem to have any benefit, but I suppose I'll have to live with it. More exclamation marks!!!

To add to this, not even shell scripts running as PDF Services, can save files.

I've found a fix until Apple decides to slacken off its evil grip over my computer. ;-) In Automator, make an Application that runs your shell script. Raw scripts, Print plug-ins, workflows or other kinds no longer work as PDF Services. This works for me with my python directly in the Automator "Run Shell Script" action. Whether it will let you pass control to a separate process, I don't know.

My python scripts that run as PDF Services don't work in Big Sur anymore. Console is full of Sandbox deny messages for python Library files. I'm guessing Apple has prevented PDF Services from executing python or other code. "For security reasons". Tsk.

I've sent Feedback, so an Apple technician should be responding and fixing this right away! Ahahaahahahaha.