Skip to main content
Keep up with our Changelog with the RSS Feed.
2026-07-22
Removed deprecated logic that recorded network status following download issues.The Zappl daemon now points directly to the Zappl app path rather than the symlink, ensuring the Zappl app and its icon are correctly displayed under Login Items in System Settings.
2026-07-14
Zappl v3 introduces a completely redesigned user interface, rebuilt in SwiftUI to match AppBar’s look and theme. As part of this, the Zappl agent has migrated from a command line tool to a SwiftUI app, though it continues to support all the same command line options.Update prompts now display each pending update as an app card, alongside a new customisable info popover explaining the update and deferral process. The update progress prompt is smaller and more subtle, and the update completion prompt has been replaced by a native macOS notification. Self Service update prompts have also been deprecated - running zappl -u selfService now redirects users to AppBar instead.A number of preferences have been deprecated, and several new ones added, including enableLiquidGlass, showInfoButton, initialPromptInfoPopover and gracePeriodPromptInfoPopover. Zappl v3 remains backwards compatible with existing configuration profiles - deprecated preferences are simply ignored, and new preferences retain their defaults until configured. If you’re a Jamf Pro customer, it’s recommended you update to the latest JSON schema. For all other MDMs, refer to the updated preferences documentation and sample plist.Because Zappl is now an app rather than a standalone binary, an updated PPPC profile and a new combined Zappl and AppBar Notifications profile are required - without these, users may see permission and notification prompts when Zappl runs. Both are available from our Deploy Anywhere guide. Jamf Pro customers using the Installation Status extension attribute should also update to the latest revision, which checks for the new app bundle path.For full details on everything that’s changed, read the blog post.
2026-06-19
Fix added for a bug introduced in 2.6.0 whereby, on clean installs, on-demand Self Service updates immediately after Zappl is installed do not override the scheduled background stagger check.Please note, Self Service updates are deprecated as of July 14th when Zappl v3 releases - more info.
2026-06-17
Added forward compatibility for the new Zappl v3 preferences to suppress errors caused by the changed preferences. The new schema will be released in the coming weeks, ahead of Zappl v3’s official release on Wednesday, July 1st. For more information on Zappl v3 - click here.
2026-06-02
The download stagger window now applies to scheduled update prompts when background updates are disabled. The dependency between the two keys has also been removed, so downloadStaggerWindow can be configured independently regardless of whether background updates are enabled.To better reflect this behaviour, the preference key has been renamed from backgroundUpdateWindow to downloadStaggerWindow.Additionally, the hourlyCheck preference key has been renamed to backgroundUpdates since background updates now operate on the stagger window rather than a fixed hourly interval.Both old keys are deprecated but will continue to work.If you’re a Jamf Pro customer, it’s recommended you update your Zappl preferences configuration profile to use the latest JSON schema. For all other MDMs, refer to the updated sample plist to see the new key labels in use.
2026-04-23
Increased the refresh frequency of local AppBar data via Zappl
2026-04-20
Official support for AppBar added. Zappl now automatically deploys AppBar when the Automatically Install AppBar preference is configured.--appbar flag added to the Zappl uninstaller binary to allow AppBar uninstalls.
2026-04-15
Prevented Zappl from attempting to download additional components on first run when no internet connection is detected, avoiding misleading errors in the Zappl portal.Improved the handling of post-install scripts during app installations.
2026-03-26
Added a new Background Update Stagger Window option. This option requires the latest JSON schema for Jamf Pro customers. All other customers can refer to the updated preferences document and the sample plist.Added a new feature to automatically clear all entries older than 4 weeks in /var/log/Zappl.log to prevent performance issues when viewing the log.
2026-03-12
Minor improvements made to the handling of PKG installers.
2026-03-10
Fixed a bug introduced in v2.1.1 whereby the Jamf Pro Self Service update prompts do not respect “Horizontal List Mode” when there are multiple pending updates.
2026-03-09
Improved the logging messages sent to AppBar.
2026-02-26
Added further support for the new AppBar menu bar app.
2026-02-25
Fixed an issue where devices without an internet connection would generate misleading errors in the portal. Fixed an issue where devices in trial mode without an internet connection would incorrectly attempt to validate the trial license via the server. Fixed an issue where the Next Prompt date displayed in the portal was incorrect when using the Patch Day Weeks configuration option.
2026-02-17
Added support for the new AppBar menu bar app.Changed default icon logic to fall back to SF Symbol if no Jamf Self Service icon is found and no custom icon is defined.
2026-01-29
Fixed a bug with DND mode not being detected in macOS Tahoe.
2026-01-13
Added support for Zappl to install and run commands outside of a user console session. This allows Zappl to run with integrations which run pre-login (such as Jamf Setup Manager etc) without keychain error prompts.Added more verbosity to Jamf recons being run via Zappl, and added logic to kill any recons which hang.Further security enhancements made to the backend infrastructure.
2025-12-03
Added support for the new “Enable Compliance Reporting” option which allows you to disable report submission to the Zappl portal. This is useful for test devices or environments where portal reporting is not required.This requires the latest JSON schema if you are using Jamf Pro. Other customers can refer to the updated preferences document and the sample plist.
2025-11-26
Added further support for locales and fixed a bug introduced in v2.0.3 with some disk images not mounting.
2025-11-24
Added universal support for locales.
2025-11-10
Enhancements made to the backend infrastructure to improve security and overall performance. As part of this change, Jamf Pro customers who wish to continue to utilise the “Deferrals Remaining” extension attribute must update to the latest revision of this extension attribute.Improvements made to the appearance and default behaviour of update prompts.Improvements made to file download functionality.Added new command line flag to update specific apps on demand. For more info, see the command line options.Added support for the new “Week(s) of Month” option which allows you to specify which weeks in the month users are prompted to update on the configured patch day (e.g. Tuesday on the first week of each month) when “Specify Recurring Patch Day” is configured as your desired Run Frequency Option. This requires the latest JSON schema if you are using Jamf Pro. Other customers can refer to the updated preferences document and the sample plist.
2025-10-13
Added support for Jamf Self Service+ icons to be shown on update prompts. Improved the update prompt appearance for macOS Tahoe.
2025-07-10
Enhanced the download URL retrieval process.
2025-06-17
Additional post install checks added for app bundles.
2025-06-16
Improvements to the backend code and various log outputs.
2025-06-06
Adds support for apps that install into the User’s Applications directory (~/Applications).
2025-05-28
Added additional folder structure checks to the initial error handling mechanism.
2025-05-12
Made improvements to PKG signature verification.
2025-04-28
Fixed bug whereby DMG with EULA installers fail file hash check because we were checking the hash of the converted .cdr image. Resolved by keeping the original DMG and verifying the hash of that before removing it.
2025-04-28
Fixed bug with installs not exiting after deleting the app when the installer hash doesn’t match. This caused a failed install as the app had been removed.
2025-04-17
Fixed bug where patch day calculations are used when patch day isn’t configured.
2025-04-11
Added support for Apps which have DMGs nested in ZIP files.
2025-03-27
Added option to skip automatic permissions setting to allow it to be done with a delay through the post-install script. This is for apps where gatekeeper takes a while to finish verification. Also added logic to allow app installs to make up to 10 API calls daily if the specified app was not found in the offline app catalog.
2025-03-13
Improved internal backend logic, and fixed some user full name output bugs.
2025-03-11
Bug fixes, including a loop bug where 'components could not be verified'.
2025-02-19
Zappl will now conduct 2 App Catalog API calls per day, reducing the network activity from Zappl without affecting the end user experience of effectiveness of Zappl.
2025-01-17
Moved some API infrastructure in our backend system.