locked
RTM Known Issue: ToastNotificationHistoryChangedTrigger only sends Removed and Added change types (Expired or Cleared are sent as Removed) RRS feed

  • Question

  • Issue: When using ToastNotificationHistoryChangedTrigger, events like a toast notification expiring, or the user clearing all of the notifications for an app, both incorrectly trigger the background task with ChangeType of Removed instead of Expired or Cleared.

    Repro steps for Cleared

    1. Set up ToastNotificationHistoryChangedTrigger
    2. Send some toast notifications
    3. Open Action Center and dismiss the entire app's notifications (instead of dismissing individual toasts)

    Expected: Cleared is the ChangeType received by the background task
    Actual: Removed is used instead

    Repro steps for Expired

    1. Set up ToastNotificationHistoryChangedTrigger
    2. Send a Send a toast that has an expiration time a few mins in future
    3. Wait till toast expires and disappears

    Expected: Expired is the ChangeType received by the background task
    Actual: Removed is used instead

    Note that the rest of the scenarios work correctly - Added works (Added is only triggered when you send a push notification, since in a local notification case, it'd be useless to trigger your background task for something your own code did).

    Thursday, November 19, 2015 6:41 PM
    Moderator

Answers

  • Status: Fix pending for RS1

    Workaround: In most cases, you shouldn't even need to check the ChangeType. For example, if you're simply keeping your badge and toast notifications count in sync, when your background task is triggered, simply query how many notifications are currently in Action Center and update your badge accordingly.


    Thursday, November 19, 2015 6:45 PM
    Moderator