Overview
A native macOS app that keeps third-party applications up to date by driving
Installomator under a
persistent root LaunchDaemon. The successor to the
App-Auto-Patch shell project,
rebuilt in Swift / SwiftUI for macOS 14+ with the same preference domain so
existing 3.5.0 configuration profiles deploy against 4.x. Check one key:
PatchWeekStartDay counts Sunday as 1 in 4.x, where 3.x counted Monday as 1.
Highlights
Section titled “Highlights”- Keep apps current automatically. Periodic background pass detects apps that have updates available and aren’t currently running and patches them silently. Two scheduler modes: in-process (the default on every Mac, runs while the menu-bar item is alive) or root LaunchDaemon (survives a full app quit, and a user logout when a profile sets it; the example baseline profile does).
- Stage installers first. When an update is detected, its installer is
downloaded before any install, including a background patch of closed
apps, so the install reuses the local copy. On by default
(
WorkflowStageUpdates). - Keeps itself up to date.
SelfUpdateMethodchooses how. By default (InAppList), AAP is in its own app list and updates with your other apps, deferrals and deadlines included.BackgroundScheduletakes it out of the list and checks for new builds on a schedule of its own (SelfUpdateFrequency), andDisabledleaves it to your MDM. Both updating methods use theappautopatch4Installomator label, and AAP brings its own copy of it for an Installomator that doesn’t have it. See Keeping App Auto-Patch up to date. - First-run setup wizard. New users land in a guided three-step flow (approve helper → wait for Installomator → discover apps); already-managed Macs auto-skip it.
- Receipt history. Per-app patching audit trail visible directly under each row on the dashboard — no log grepping required.
- Deferral audit trail. Every user-initiated deferral, focus-mode
suppression, forced deadline install, and patch invocation is recorded as
a timestamped JSON event in
/Library/Application Support/AppAutoPatch/deferral-events/and surfaced in the per-app dashboard disclosure. Answers the “I never saw a prompt” question without log grepping. - One-click diagnostic bundle. Settings → About → Generate Diagnostic Bundle zips logs, redacted prefs, helper state, patching receipts, and deferral events to the user’s Desktop.
- Temporary and persistent notifications. Informational
background-patch toasts use the main app identity as banners.
Action-required alerts (open-app updates, AC-power required,
deferral resume, hard-deadline reminders) post from an embedded
helper, shown in System Settings as App Auto-Patch Notification, under
xyz.techitout.appAutoPatch-persistentso they stay until the user acts. Admins can reroute types withTemporaryNotificationTypes/PersistentNotificationTypes. - MDM-friendly. All preferences honored through the
xyz.techitout.appAutoPatchdomain, with a ProfileCreator/iMazing JSON manifest inProfile Manifests/that covers every managed key.
System requirements
Section titled “System requirements”- macOS 14 (Sonoma) or later.
- Apple Silicon or Intel.
- Admin rights on first launch (to approve the root helper LaunchDaemon).
- Optional: an MDM that can deliver a
xyz.techitout.appAutoPatchCustom Settings payload.
Architecture
Section titled “Architecture”AAP is split across five targets sharing a common framework, plus a test target. Each target has a single, narrow job:
| Target | Role |
|---|---|
AppAutoPatch |
SwiftUI GUI app (dashboard, settings, menu bar, log viewer). User-facing surface. Posts temporary (banner) notifications. |
AppAutoPatchPersistentNotifier |
Embedded LSUIElement helper copied into Contents/Helpers as App Auto-Patch Notification.app. Bundle ID remains xyz.techitout.appAutoPatch-persistent. Posts and cancels persistent alerts, then exits. |
AppAutoPatchService |
XPC service the GUI talks to. Owns Installomator discovery and queues patch jobs into a shared jobs directory. |
AppAutoPatchRootHelper |
LaunchDaemon running as root. Picks up jobs from the shared directory, runs Installomator, writes receipts + helper state, drives the optional helper-mode background-patch scheduler. |
AppAutoPatchCore |
Shared framework: data models, preference loading, version comparator, helper-state schema, logging service. Linked by the other three targets. |
AppAutoPatchCoreTests |
XCTest suite for AppAutoPatchCore. |
| The GUI never runs Installomator directly. Patching always goes | |
| GUI → XPC service → root helper → Installomator, so privilege boundaries | |
| stay clean and the helper alone owns the receipts directory. |
