Compatibility of my apps with Mojave: details and advice

I’ve just had my first marathon testing session of my apps running in the first developer beta of Mojave. For the benefit of those in Apple’s beta-testing programs for Mojave, this article provides information about the compatibility of current versions of my apps. I will keep it updated as I get further information, and Apple releases further betas.

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.0b2 (QuickLook cache privacy) – fully compatible.
  • Bailiff 1.1 (iCloud menubar control) – fully compatible.
  • Blowhole 6 (make log entry, command tool) – fully compatible.
  • Cirrus 1.1 (full iCloud toolkit) – fully compatible.
  • Consolation 3.0b16 (log browser) – fully compatible.
  • DeepTools 1.1 (preserve versions) – fully compatible.
  • 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.9 (check security systems) – fully compatible, notarized. I will be creating a new version with specific support for Mojave’s data file versions ready for the release.
  • Nalaprop 1.0a2 (parse text into parts of speech) – requires Mojave.
  • PermissionScanner 1.2 (check Home folder permissions) – fully compatible.
  • Precize 1.3 (file info including Bookmarks) – fully compatible.
  • 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.0a2 (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.3 (list update history) – fully compatible.
  • T2M2 1.3 (Time Machine check) – not checked yet. Because this requires a fully functional TM setup, I will probably be unable to test this until the release of Mojave.
  • 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 once Consolation 3 has full support for Mojave.
  • xattred 1.0b8 (extended attribute (xattr) toolkit) – fully compatible.

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 expect to complete this well before the date on which Mojave ships this autumn/fall.


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, and address books. This applies principally to Bailiff, Cirrus, 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.

To do that, open the Security & Privacy pane, select Privacy, then in the left select the Application Data item. Click on the padlock and authenticate, then add the apps to that list using the + tool, as shown at WWDC. Using some features in certain apps may also require that they are added to the Systems Administration list there, although I have not yet encountered that.

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, which still seems to work fully, 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: 6 August 2018.