Jamf App Catalog Notification For Updates Behaving Strangely

user-tQjKoYlRTJ
New Contributor

We have recently deployed notifications that will notify a user that an application deployed from Jamf App Catalog is due an update. These notifications have been created through configuration profiles. The user receives three notifications:

  1. Notifies the user to close out within the next four hours so that the app can update.
  2. If the user hasn't closed out the app manually, following the four hour time period, notifies the user that the app will close to update. The application then should automatically close out after 10 seconds.
  3. Following the update, notifies the user that the app has updated successfully and will restart.

We have noticed an issue with the second notification that it is applying a 60 minute countdown before it automatically closes out the application, giving a "Minutes remaining: 60" at the end of the notification despite us not adding this as an instruction as part of the plist for the specific application.

The plist is written as:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0">
<dict>
<key>notify</key>
<integer>86400</integer>
<key>notify_message</key> <string>An update for Edge is available. You can manually quit the application to update or Edge will automatically close and update in 4 hours.</string>
<key>deadline</key>
<integer>14400</integer>
<key>deadline_message</key> <string>Edge will quit to complete the update. The application will automatically relaunch once the update is complete.</string>
<key>quit_delay</key>
<integer>10</integer>
<key>relaunch</key>
<boolean>True</boolean>
</dict>
</plist>

The message the erroring notification is showing is: 

"Edge will quit to complete the update. The application will automatically relaunch once the update is complete.

Minutes remaining: 60"

I'm not seeing any reason why that minutes remaining part of the notification should be apparent. What have I missed?

0 REPLIES 0