Repository navigation
Self Update Function
App Auto-Patch can update to a newer version when one is detected on GitHub. This functionality can be configured via Managed Configuration Profile or Command Line Triggers
As of 3.6.1, SelfUpdateEnabled and SelfUpdateFrequency are resolved before the self-update check, including on a Mac's first run before a local preference file exists. A managed SelfUpdateEnabled=false therefore prevents that initial self-update as expected.
App Auto-Patch 3.7.1 does not queue the appautopatch Installomator label during discovery or background patching. That label is ignored the same way swiftdialog and dialog are, so a background run does not update App Auto-Patch itself. The self-update check on this page remains the path that updates AAP.
App Auto-Patch 3.7.0 can authenticate GitHub API requests for a higher rate limit. See GitHubAPIAuthEnabled and GitHubAPIToken under Configure Settings.
<key>SelfUpdateEnabled</key>
<true/> | <false/>
<key>SelfUpdateFrequency</key>
<string>daily|weekly|monthly</string>
Force Self Update Check
This will trigger a one-time self-update check
--force-self-update-check
Enabling and Disabling
[--self-update-enabled] [--self-update-disabled]
Frequency
--self-update-frequency=daily|weekly|monthly
- Version Comparison Methods
- Configure Settings
- Populating App Labels
- Command Line Options/Triggers
- Self Update Function
- Business Hours
- Process Recovery
- Deployment Methods
- Workflows
- Scheduled Discovery / User-Driven Patching
- Jamf Pro Deployment
- Jamf Self Service Example
- Intune & Mosyle Deployment Example
- Reporting
- Webhooks
- Jamf Pro Extension Attributes