Adding support for Mojave’s new privacy system is mandatory for apps which need to access protected data. How easy is that?
Advice on preparing for and using Mojave for all who go beyond using standard off-the-shelf apps – scripting, automating, building from source, or full-blown Xcode development.
Giving an app Full Disk Access doesn’t. The only way to give an app access to some protected data is by trying to access that data, but when macOS crashes that app, the user is stuffed.
Doesn’t writing so much to the unified log result in performance penalties? So how can Apple expect us to use the log and Signposts to measure performance?
At first I thought it was my mistake. Then it looked like a simple error in the interface. But this bug in Mojave’s signposts is more complex. Here’s a workaround.
When the user wants to access protected data using an app which doesn’t have the entitlement, the result is at best confusing, and could end up with a crash.
I’m all in favour of better security, so long as it doesn’t make my life any more difficult. Does Notarization fulfil that?
A detailed exploration of how to use Signposts to investigate performance of your code, and the limitations of Apple’s tools.
If you’re running Mojave and using a scripting language which can’t itself access Signposts, Blowhole now gives you access to them.
Apple tells us not to use hard-coded colours like .black, but sets the default for scrolling text views to .black, causing text to be rendered in black on dark grey when in Dark Mode. Here’s a simple and universal fix.