Changes since Mojave are subtle. No new fields have been added to the log format, and code-level access is largely undocumented. Console remains at version 1.1.
log
When working on my new log browser Ulbow, I came across a bug in Consolation version 3.2 which […]
I continue to be amazed at the number of Mac users who, since Sierra introduced the new unified […]
Using only free tools, it isn’t difficult to get a log excerpt which will tell you, or someone else, exactly what occurred at the time.
You can use Signposts readily from scripting languages, shell scripts, even within 3rd party apps, with the aid of these tools.
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.
How deeply does macOS check a signature? What are all the static code validation flags? Should my app leave macOS to perform signature checks?
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.
Why signature checks are so complex, and a walk through log entries of a notarized app launching normally in macOS 10.14.5.
In Mojave, the unified log can contain up to 27 different fields, of which Consolation gives access to 26. Do you wish that to change?
The Eclectic Light Company 