Keeping App Auto-Patch up to date
One key, SelfUpdateMethod, sets how App Auto-Patch keeps itself current. It can sit in its own app list and update with your other apps, check for new builds on a schedule of its own, or leave it to your MDM.
InAppList (default) |
BackgroundSchedule |
Disabled |
|
|---|---|---|---|
| What it means | In the app list, updated with your other apps | Checks for new builds on its own schedule | Never updates itself; your MDM deploys new builds |
| Shown in the app list | yes | no | no |
SelfUpdateFrequency |
no effect | daily, weekly or monthly |
no effect |
| Deferrals and deadlines | apply | don’t apply | your MDM’s |
| Counted as a pending update in reports | yes | no | no |
InAppList and BackgroundSchedule both use the Installomator label in SelfUpdateLabel, appautopatch4 by default. Set it only if you host App Auto-Patch in a private Installomator fork. App Auto-Patch ships its own copy of appautopatch4 and uses it when the Installomator on the Mac doesn’t have one, so any InstallomatorVersion works.
SelfUpdateMethod is new in 4.0.0 (125). Its values are case-insensitive, and an unrecognized value is ignored.
In the app list
Section titled “In the app list”This is the default: leave SelfUpdateMethod out of your profile, or set it to InAppList.
App Auto-Patch is listed with the other apps it manages, as App Auto-Patch. When a newer build is available, it updates the way they do:
- when the user clicks Update All, the update button on its row, or Update Selected with its row checked on the Needs Update tab (4.0.0 (129) and later), where it is installed after the other checked apps;
- when deferrals run out or a deadline arrives, like any other pending update in the patch cycle.
The background pass for closed apps (BackgroundPatchClosedAppsEnabled) skips it while App Auto-Patch is running, which is nearly always. If the app has been quit, or nobody is logged in, a pass run by the root helper can install it.
Use this if new builds of App Auto-Patch should follow the same patch cycle, deferrals and deadlines as everything else.
On its own schedule
Section titled “On its own schedule”Set SelfUpdateMethod to BackgroundSchedule, and optionally SelfUpdateFrequency (daily by default):
<key>SelfUpdateMethod</key><string>BackgroundSchedule</string><key>SelfUpdateFrequency</key><string>weekly</string>App Auto-Patch leaves its own app list, and the app checks for a newer build instead:
- When it checks. A check runs once the last one is a whole day, week or month (30 days) old by the clock, so time the Mac spends asleep counts. The app looks every 15 minutes and shortly after the Mac wakes, and waits 5 minutes after it launches. A check that is due while patching is running, or before the helper is ready, runs at the next look. If the check fails, for example with no network, the next try is an hour later.
- What it does with a newer build. With
BackgroundPatchClosedAppsEnabledon (the default), it installs it right away, without asking. The package quits App Auto-Patch, replaces it and opens it again. With that key off, the dashboard shows an Update Now banner instead, plus a notification if the user has already allowed App Auto-Patch’s notifications. - What doesn’t apply. Deferrals, deadlines and the patch cycle don’t apply, and App Auto-Patch isn’t counted as a pending update.
- Where it runs. The checks run in the App Auto-Patch app, not the root helper, so they need a user logged in with App Auto-Patch running.
Use this if App Auto-Patch should stay current on its own, whatever the patch cycle.
A profile change to SelfUpdateMethod or SelfUpdateFrequency takes effect within 15 minutes, without relaunching the app.
Before 4.0.0 (125), the schedule never updated App Auto-Patch. With
SelfUpdateEnabledon (the key that set this method until build 125), the check left out App Auto-Patch’s own label and found nothing, unless Installomator had noappautopatch4label. Its checks also counted only the time the Mac was awake. A Mac on build 124 or earlier with that setting stays on its build, so deploy 4.0.0 (125) or later with your MDM, or turnSelfUpdateEnabledoff until the Mac has updated from its app list.
With your MDM
Section titled “With your MDM”Set SelfUpdateMethod to Disabled:
<key>SelfUpdateMethod</key><string>Disabled</string>App Auto-Patch then never updates itself and isn’t in its app list; deploy each new build with your MDM. On Jamf Pro, the Jamf Pro patch source reports which Macs run the newest build and lets a patch policy update the rest. The quick start’s baseline profile uses this setup.
In the Settings window
Section titled “In the Settings window”The same choice is under Settings › Advanced › Self-Update, as Update App Auto-Patch: In the app list, On its own schedule or Off. Check frequency is SelfUpdateFrequency, and Installomator label is SelfUpdateLabel.
A profile that sets any of the self-update keys, or LockSettings, locks the whole section.
The keys it replaces
Section titled “The keys it replaces”Until build 125, two on/off keys made the same choice, and an older third one overrode the first:
| Deprecated key | Same as |
|---|---|
SelfUpdateEnabled true |
BackgroundSchedule |
DiscoverSelfUpdateLabel false, with SelfUpdateEnabled off |
Disabled |
AppSelfUpdateEnabled |
overrides SelfUpdateEnabled when set |
| none of them set | InAppList |
They still work while SelfUpdateMethod is unset, and App Auto-Patch logs a warning when a profile sets them. When a profile sets SelfUpdateMethod, it wins over them.
Mixed fleets. Macs on 4.0.0 (124) or earlier read only the old keys. A profile for both can set SelfUpdateMethod and keep the old key that matches. For example, set SelfUpdateMethod Disabled together with DiscoverSelfUpdateLabel false. Builds 125 and later use SelfUpdateMethod and log a warning only if the two disagree. InAppList needs no old key, since it is the default everywhere. BackgroundSchedule doesn’t work before build 125 in any case.
A profile beats the Settings window across old and new keys: a profile’s SelfUpdateMethod comes first, then a profile’s old keys, then the Settings window’s choice. Saving the Settings window replaces the old keys’ local values with SelfUpdateMethod.
Checking that it works
Section titled “Checking that it works”The log, /Library/Application Support/AppAutoPatch/logs/aap.log, names the method each time App Auto-Patch launches or the settings change:
SelfUpdateScheduler: SelfUpdateMethod is BackgroundSchedule — frequency=weekly, label=appautopatch4. Last check 2026-11-10T16:05:12Z; next due 2026-11-17T16:05:12Z. A newer build is installed right away.SelfUpdateScheduler: SelfUpdateMethod is InAppList; App Auto-Patch is in the app list and updates with the other apps (label appautopatch4).SelfUpdateScheduler: SelfUpdateMethod is Disabled; App Auto-Patch doesn't update itself, so deploy new builds with your MDM.Each scheduled check logs SelfUpdateScheduler: Checking for AAP self-update via label 'appautopatch4'…, followed by the result. The time of the last check is saved in the user’s preferences:
defaults read xyz.techitout.appAutoPatch LastSelfUpdateCheckDateTo check again sooner, delete that value and relaunch App Auto-Patch. The check runs 5 minutes after launch.
