macOS doesn’t handle significant errors and failures well, burying them away in the log. It needs to report them to the user through a new sub-system.
macOS 10.14
In Mojave and Catalina, tampering with the contents of an app bundle risks breaking signature checks. Here’s how to work around that.
For once, Mojave’s privacy protection worked in favour of the user, in stopping Zoom’s old app from regaining access to your camera and microphone.
How deeply does macOS check a signature? What are all the static code validation flags? Should my app leave macOS to perform signature checks?
Are iCloud Drive, CDs and DVDs, and partitions on the same storage really suitable places for you to back your Mac up?
Part of Apple’s preparations for Catalina, this contains a list of major apps which are only 32-bit and will stop working when you upgrade to 10.15.
The apps claim my Mac is running an old version, but that the newer version was installed weeks ago. How come?
How checks differ when an app is launched from a new path, and the effects of gross changes to the Resources folder, and small changes to code.
Zoom is a popular videoconferencing system, used apparently by about 750,000 companies and several million individuals around the […]
Why signature checks are so complex, and a walk through log entries of a notarized app launching normally in macOS 10.14.5.
