Custom timestamps on toasts
By default, the timestamp on toast notifications (visible within Action Center) is set to the time that the notification was sent.
You can optionally override the timestamp with your own custom date and time, so that the timestamp represents the time the message/information/content was actually created, rather than the time that the notification was sent. This also ensures that your notifications appear in the correct order within Action Center (which are sorted by time). We recommend that most apps specify a custom timestamp.
Requires Creators Update and 1.4.0 of Notifications library: You must be running build 15063 or higher to see custom timestamps. You must use version 1.4.0 or higher of the UWP Community Toolkit Notifications NuGet library to assign the timestamp on your toast's content.
To use a custom timestamp, simply assign the DisplayTimestamp property on your ToastContent.
var content = new ToastContent() .AddCustomTimeStamp(new DateTime(2017, 04, 15, 19, 45, 00, DateTimeKind.Utc)) ...
If you are using XML, the date must be formatted in ISO 8601.
You can only use at most 3 decimal places on the seconds (although realistically there's no value in providing anything that granular). If you provide more, the payload will be invalid and you will receive the "New notification" notification.
In general, we recommend that most apps specify a custom timestamp. This ensures that the notification's timestamp accurately represents when the message/information/content was generated, regardless of network delays, airplane mode, or the fixed interval of periodic background tasks.
For example, a news app might run a background task every 15 minutes that checks for new articles and displays notifications. Before custom timestamps, the timestamp corresponded to when the toast notification was generated (therefore always in 15 minute intervals). However, now the app can set the timestamp to the time the article was actually published. Similarly, email apps and social network apps can benefit from this feature if a similar pattern of periodic pulling is used for their notifications.
Additionally, providing a custom timestamp ensures that the timestamp is correct even if the user was disconnected from the internet. For example, when the user turns their computer on and your background task runs, you can finally ensure that the timestamp on your notifications represents the time that the messages were sent, rather than the time the user turned on their computer.
If you don't provide a custom timestamp, we use the time that your notification was sent.
If you sent a push notification through WNS, we use the time when the notification was received by WNS server (so any latency on delivering the notification to the device won't impact the timestamp).
If you sent a local notification, we use the time when the notification platform received the notification (which should be immediately).