Compatibility of my apps with Mojave: details and advice

I have spent a lot of time working with beta-releases of Mojave to try to ensure that as many of my apps as possible are not just compatible with Mojave, but work well with it and use its new features. However, some of them access features that have been removed, or changed greatly, and in the worst case one or two don’t work. Here’s an updated list giving details of their compatibility with Mojave.

Current apps available from Downloads here:

  • 32-bitCheck 1.6 (check 32-bit apps etc.) – fully compatible, notarized.
  • alisma 1.1 (Finder alias command tool) – fully compatible.
  • Apfelstrudel 1.1 (Unicode normalisation toolkit) – fully compatible.
  • Aquiline Check 1.0b2a (QuickLook cache privacy) – fully compatible but no longer needed, as Mojave fixes the vulnerability.
  • Bailiff 1.2 (iCloud menubar control) – fully compatible.
  • Blowhole 8 (make log entry, command tool) – fully compatible.
  • Cirrus 1.1 (full iCloud toolkit) – fully compatible.
  • cmpxat 1 (compare xattrs, command tool) – fully compatible.
  • Consolation 3.0b16 (log browser) – fully compatible.
  • DeepTools 1.1 (preserve versions) – fully compatible.
  • DelightEd 1.0b2 (Rich Text editor) – fully compatible, notarized.
  • DispatchRider 0.3b1 (task scheduler) – not checked yet.
  • DispatchView 1.0 (inspect DAS and CTS in log) – incompatible; I will fix this later.
  • Dystextia 1.4 (obfuscate text with Unicode) – fully compatible.
  • HelpHelp 1.1 (Help book toolkit) – incompatible; I currently have no plans to port this app to High Sierra or Mojave due to the change in information available from the Help system.
  • KeychainCheck 2.0a4 (advanced check Keychains) – fully compatible apart from log extracts, which don’t work in High Sierra or Mojave yet.
  • LockRattler 4.12 (check security systems) – fully compatible, notarized, Mojave support page.
  • Nalaprop 1.0b5 (parse text into parts of speech) – requires Mojave, notarized.
  • PermissionScanner 1.3 (check Home folder permissions) – fully compatible, notarized.
  • Precize 1.4 (file info including Bookmarks) – fully compatible, notarized.
  • RepairHomePermissions 1.0 (repair Home folder permissions) – fully compatible.
  • Revisionist 1.2 (document versions toolkit) – fully compatible, notarized.
  • Rosettavert 1.1 (text encoding conversion) – fully compatible.
  • RouteMap 1.0b1 (Signpost harvest, analysis) – fully compatible.
  • RunConsolation 1.1 (runs Consolation in ordinary user mode) – not checked yet.
  • RunT2M2 1.0 (runs Time Machine check in ordinary user mode) – not checked yet.
  • Scrub 1.0b1 (clean sensitive files) – fully compatible.
  • SearchKey 1.1 (search metadata (full)) – fully compatible.
  • SearchKeyLite 1.1 (search metadata (basic)) – fully compatible.
  • SystHist 1.4 (list update history) – fully compatible.
  • T2M2 1.4 (Time Machine check) – fully compatible, additional APFS support, notarized.
  • Taccy 1.0b5 (check app privacy settings) – fully compatible.
  • unorml 2.1 (Unicode normalisation command tool) – fully compatible.
  • UTIutility 1.0b2 (UTI and type designator tool) – fully compatible.
  • Whither 1.0 (Signpost generation) – fully compatible.
  • Woodpile 1.0b6 (top-down log browser) – incompatible, and requires significant revision before it will be usable. I will be tackling this in the coming weeks.
  • xattred 1.0b9 (extended attribute (xattr) toolkit) – fully compatible, notarized.

Dark Mode

Apple demonstrated a new Dark Mode at WWDC, in which most of the GUI becomes near-black, and showed how developers need to modify their apps in order to support Dark Mode. As I revise my apps for full compatibility, I am ensuring that they also work well in Dark Mode. Those marked as being fully compatible above have now been so revised.


I am getting each notarized over the coming weeks, where that is possible. Notarization is only voluntary in Mojave, but as it offers users much improved security, I will try to get all my apps duly notarized by Apple. There is currently no equivalent accreditation available for command tools.


Another new feature demonstrated by Apple at WWDC is added privacy for mail, calendars, address books, and more. This applies principally to PermissionScanner, Precize, and xattred, although any app which tries to access folders containing such personal data will trigger the feature.

When you use an app which tries to access those protected data, a dialog appears seeking your consent. You can either leave it until that dialog appears, or you can pre-empt this by adding the app to the list of permitted users of the data. If you want to use any of these tools on all files (with appropriate permissions), I strongly recommend that you give them access to all your files before running them in Mojave.


To do that, open the Security & Privacy pane, select Privacy, then in the left select the Full Disk Access item. Click on the padlock and authenticate, then add the apps to that list using the + tool, as shown at WWDC.

Most of my other apps, even those which work quite low down in macOS, are not intended to access protected folders and files. When you use them, you may see protected folders locked away with No Entry signs on them. You can alter this behaviour by adding them to the Full Disk Access list, but I do not recommend that you do so unless you really need to.

Aquiliner and Bailiff include a feature which runs them automatically at startup: if you enable that in Mojave, you will need to consent to them scripting System Events in the Automation list of Privacy. This is described in their documentation and Help windows.

I am progressively adding a new command to the Help menu in each of my apps, Privacy settings, which shows you at a glance what is recommended and possible in Mojave’s Privacy settings.

At worst, Mojave will deliberately crash an app which tried to access protected items without your approval. This is not because the app has a bug or fault, but to protect your private data. If you do experience such crashes, and don’t know how to resolve them, please contact me for advice. Mojave’s privacy protection is strong, but is also a marked change in behaviour from previous versions of macOS. You may find my new app Taccy helpful in discovering an app’s privacy settings and working out what to do.

Accessing logs

I recommend that you use the latest version of Consolation 3 if you want to access Mojave’s logs. Woodpile isn’t completely broken by Mojave, but is largely dysfunctional at present. Its feature to create logarchives is broken, though, and clicking on that button will cause the app to quit unexpectedly. If you want to make a logarchive, I recommend that you do so either using the button in Consolation 3, or the log collect command in Terminal.

Consolation cannot access Mojave logarchives unless it is running on Mojave, which is also true for the log command in Terminal. If you do create a logarchive in Mojave, you will therefore only be able to access it from Mojave.

Reporting problems

If you encounter problems with any of my apps, in Mojave or elsewhere, please leave a comment here, or send it to me by email (my address is in the About page). I can’t fix what I don’t know about.

Last updated: 23 October 2018.