Mojave’s privacy features remain essentially undocumented. Apple hasn’t explained how command tools negotiate TCC’s protection. Why not, and what should we do?
Mojave
Calling command tools from Swift changes with macOS 10.13 and 10.14 with the deprecation of some of the Process class. Solutions aren’t as clean as they should be.
Apple has intentionally made it very hard to troubleshoot problems with privacy protection. Here’s a new feature to help, in a new version of Taccy.
It has been one of the oldest problems on Macs, when a document shows with the wrong icon. Why, and how to fix it?
You try to open a document – in this case, one of Firefox’s bookmarks – and nothing happens. What could be wrong? It turns out it’s a bug, of course. But where?
A broken Combo updater, and total lack of release notes (even for developers) may make 10.14.3 look bad, but as development of 10.15 gathers pace, prospects are good for macOS.
Why do the Open File and Save File dialogs normally behave differently with respect to tagged folders? It’s a question of semantics.
Have you given up with the Legacy Software section in System Information? It’s getting more useful, and probably an escalating nudge on the part of Apple. Here’s why.
Three bugs may have been fixed in 10.14.3: About This Mac’s Storage bar (at last), App Store glitches showing apps need to be redownloaded, and some black on grey text.
When installing the 10.14.3 update, Software Update’s progress bar mislead, and the process became confusing.
The Eclectic Light Company 