🛠 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

🛠 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.

✨ New

App Catalog 1.11.0

• Add to Microsoft Intune: Admin Mode can now upload an app straight to your Microsoft Intune tenant, no need to download a package and create the app in Intune yourself. Just open Admin Mode, select an app, and choose Upload next to Microsoft Intune. The first time, an administrator grants a one-time consent so App Catalog can manage apps in your tenant; after that, every upload is a single click. As with the Package deployment tool, the uploaded package isn't the app itself, it runs the Catalog Agent to install the app, so it always stays up to date from App Catalog.

  • More information: Microsoft Intune and Admin Mode

👀 Changed

App Catalog 1.11.0

• Update from the notification: Clicking Update now on an update reminder now installs the updates right away in the background, instead of opening the Catalog App. It's a faster, less disruptive way to stay up to date. Tapping the notification itself still opens the Catalog App on the Updates section, so users who want to review or update granularly can still do so.

  • More information: User deferrals & interaction

• New command syntax: The Catalog Agent now uses clear subcommands, for example catalog install nl.root3.support, catalog update and catalog uninstall nl.root3.support. Behind the scenes we've migrated to Swift Argument Parser for more robust, reliable argument parsing and built in help functions.

  • Run catalog help or catalog help SUBCOMMAND to view all available options.

  • Your existing scripts and MDM policies keep working unchanged, the familiar dash-style commands (catalog --install, catalog -u, catalog --update) will continue to work.

  • More information: Catalog Agent CLI

🛠 Fixed

App Catalog 1.11.0

• Minor UI improvements: The Settings window no longer resizes when switching tabs, plus small toolbar refinements.

• Uninstall App Catalog improvements: Added easier methods to cleanly remove App Catalog and all of its components from a Mac.

  • More information: Uninstalling App Catalog