🛠 Fixed

• Macs could silently stop checking for updates: The update schedule was registered once during installation, and that registration could fail without reporting an error, most often when the package was installed while nobody was logged in. Nothing retried it, so the Mac never ran a scheduled update check again while continuing to look healthy in every other way. The schedule now ships as a regular background service inside the installer package, so installing and upgrading behave the same whether or not a user is logged in. Affected Macs recover automatically once they receive this version.

  • More information: Update schedule not found

• Permanent update prompt for apps without a version: Command line tools, uninstallers and anything that isn't an application bundle could show an update that never went away, because installing it couldn't change the outcome. These are now skipped, matching what the catalog command line tool already did.

• App locations matched imprecisely during scanning: Excluded locations are now matched on path components instead of as text, so a folder whose name merely begins with an excluded path is no longer skipped.

👀 Changed

• The command line tool leads with its subcommand syntax: The documentation, built-in help and generated deployment scripts now use the subcommand form, for example catalog install nl.root3.support. The familiar dash-style commands such as catalog --install keep working, so your existing scripts and MDM policies need no changes.

  • More information: Catalog Agent CLI

👀 Changed

• Background services now ship inside the installer package: The configuration files that start App Catalog's background services are no longer created on the Mac during installation. They now travel inside the signed and notarized installer package and are simply copied into place. Because nothing is generated or modified on the Mac itself, endpoint security tools (such as EDR/XDR solutions) can verify that every file comes straight from the notarized package, and installations no longer trigger false alerts in these tools. Existing installations are updated automatically, no action needed.

🛠 Fixed

• Background services on macOS 27: On macOS 27, App Catalog's background services could fail to start after installation, stopping update checks, notifications and app installs. This is now fixed. You may need to manually update devices from App Catalog 1.11.0 to 1.11.1.

👀 Changed

• Extra protection for background services: On macOS 14 and higher, App Catalog's background services now only start when they're signed by Root3.