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.Increased the refresh frequency of local AppBar data via Zappl
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.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.
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.Minor improvements made to the handling of PKG installers.
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.
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.
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.
Fixed a bug with DND mode not being detected in macOS Tahoe.
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.
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.
Added further support for locales and fixed a bug introduced in v2.0.3 with some disk images not mounting.
Added universal support for locales.
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.
Added support for Jamf Self Service+ icons to be shown on update prompts. Improved the update prompt appearance for macOS Tahoe.
Enhanced the download URL retrieval process.
Additional post install checks added for app bundles.
Improvements to the backend code and various log outputs.
Adds support for apps that install into the Userâs Applications directory (~/Applications).
Added additional folder structure checks to the initial error handling mechanism.
Made improvements to PKG signature verification.
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.
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.
Fixed bug where patch day calculations are used when patch day isnât configured.
Added support for Apps which have DMGs nested in ZIP files.
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.
Improved internal backend logic, and fixed some user
full name output bugs.Bug fixes, including a loop bug where
'components could not be verified'.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.
Moved some API infrastructure in our backend system.