Notes
This is a pre-release version of Nudge created by GitHub Actions.
Nudge.app has been signed and notarized. The package has been signed, notarized and stapled.
By default Nudge looks for a com.github.macadmins.Nudge.json
file located in /Library/Preferences
. If you would like to use an alternative path, please read the README or the WIKI
About the LaunchAgent
This is a basic launch agent that opens Nudge twice an hour, every 30 minutes.
If you would like to reduce the amount of times Nudge launches per day, it is recommended to create your own LaunchAgent.
Changelog
Added
- Nudge "Suite" package that includes the Logger LaunchDaemon, Nudge 30 minute LaunchAgent and Nudge.app
- The Nudge application is identical to the standard package which is signed and notarized.
- The package is signed, notarized and stapled, similarly to the standard package.
- The Nudge application is identical to the standard package which is signed and notarized.
- Changlog in GitHub Actions
- Blurring feature when the user is passed the required installation date.
- Many many thanks to @bartreardon for this feature!
- Blurring will dynamically enable a blur for all of the user's screens until they click on the
Update Device
button.
- If the user adds or removes a screen during Nudge's current session, after the next re-activation event, the blur will dynamically modify to the new screen count.
- Many many thanks to @bartreardon for this feature!
- Danish localization
- Added basic localizations for new Notification Center UX
- Help on this would be appreciated
- Help on this would be appreciated
Arguments
-bundle-mode
argument to launch Nudge with a built-in json. Not for use in production.
-print-profile-config
argument to print out the current profile preferences applied to nudge. Nudge will not run when passing this argument.
-print-json-config
argument to print out the current json preferences applied to nudge. Nudge will not run when passing this argument.
Keys
acceptableApplicationBundleIDs
- The application names using assertions which Nudge allows without taking focus. You can specify one or more applications. To find the names please run
/usr/bin/pmset -g assertions
in Terminal while the application is open and running.
- The application names using assertions which Nudge allows without taking focus. You can specify one or more applications. To find the names please run
acceptableAssertionUsage
- When enabled, Nudge will not activate or re-activate when assertions are currently set.
- When enabled, Nudge will not activate or re-activate when assertions are currently set.
acceptableCameraUsage
- When enabled, Nudge will not activate or re-activate when the camera is on.
- When enabled, Nudge will not activate or re-activate when the camera is on.
acceptableScreenSharingUsage
- When enabled, Nudge will not activate or re-activate when screen sharing is active.
- When enabled, Nudge will not activate or re-activate when screen sharing is active.
aggressiveUserFullScreenExperience
- When disabled, Nudge will not create a blurred background when the user is passed the deferral window.
- defaulted to on
- When disabled, Nudge will not create a blurred background when the user is passed the deferral window.
customDeferralDropdownText
- This allows you to custom the "Defer" button.
---
- This allows you to custom the "Defer" button.
attemptToBlockApplicationLaunches
- When enabled, Nudge will attempt to block application launches after the required installation date. This key must be used in conjunction with
blockedApplicationBundleIDs
.
- When enabled, Nudge will attempt to block application launches after the required installation date. This key must be used in conjunction with
blockedApplicationBundleIDs
- The application Bundle ID which Nudge disallows from lauching after the required installation date. You can specify one or more Bundle ID.
- The application Bundle ID which Nudge disallows from lauching after the required installation date. You can specify one or more Bundle ID.
terminateApplicationsOnLaunch
- When enabled, Nudge will terminate the applications listed in blockedApplicationBundleIDs upon initial launch.
- When enabled, Nudge will terminate the applications listed in blockedApplicationBundleIDs upon initial launch.
Please note that with these three options, the user will be notified through Notification Center, but only if they approve the dialog. It is recommended to deploy an MDM profile for this to force user notifications, otherwise Nudge will ask the user upon the next launch to allow notifications.
Changed
- If a full screen application is already running prior to Nudge's initial launch and the user has not passed the required installation date, Nudge will wait until the user has moved to another application or change the full screen state of the current application before triggering it's first activation. This is due to poor behavior with full screen applications.
- CMD+N and CMD+M are now banned if Nudge is the primary window on a macOS device
- Nudge no longer exits 0 when there are issues it detects and instead exits 1
- Refactored all log logic to reduce lines of code
Fixed
- Improved Dutch localization
- Improved Norwegian localization
- Fixes the bug around people moving Nudge to a different desktop space and bypassing nudge event
- Fixes to non-Gregorian calendars and custom deferrals
Changes
- db2903f - Update README.md
- 0961445 - Merge pull request #376 from evansimm/main
- 3dd50a6 - first successful build of xcode 14 beta
- e51a00c - build on xcode 13.4.1 and macos 12
- 57dbdc6 - Add com.apple.ScreenSaver.Engine to acceptableBundleIDs
- 8eb8041 - Log/defer Nudge activation when screen is locked
- efcd143 - Safely unwrap frontmostApplication after screen unlock
- 832bb5b - use python3 to build munkipkgs