Guidelines and checklist for scheduled notifications (Windows Store apps)
This topic describes best practices and troubleshooting recommendations for use with scheduled tile and toast notifications and lists any requirements your app needs to meet to be accepted in the Windows Store.
- Follow the recommendations in Guidelines and checklist for tiles and Guidelines and checklist for toast notifications. Consider that guidance when planning the content of your tile or toast notification, as well as how frequently each should be updated.
- Consider using background tasks to update the schedule periodically using the MaintenanceTrigger class. For example, your app can initially schedule notifications a week in advance and then use the MaintenanceTrigger class to continue to schedule successive weeks on an ongoing basis, even without the user launching your app during any given week.
- Consider using a timeZoneChange system trigger to respond to changes to the system clock, such as Daylight Savings Time. By default, scheduled notifications are triggered in Coordinated Universal Time (UTC) and are not updated automatically in response to system clock changes. For example, a reminder app would need to change the scheduled time of the reminders when the system time changes. To do so, your app can use a background task that responds to the timeZoneChange trigger, adjusting its timing appropriately.
Possible cause: More often than not, if you experience problems with tile updates or toast notifications not appearing, the XML content of the notification is formatted incorrectly. Scheduled tile and toast notifications, as with non-scheduled notifications, must conform to the tile and toast XML schemas.
Fix: Test your XML through a local notification as a first step in debugging delivery problems with scheduled notifications. For more information, see Guidelines and checklist for tiles and Guidelines and checklist for toast notifications.
Possible cause: You've exceeded the maximum allowed number of scheduled notifications.
Possible cause: Your notification is scheduled for a time in the past relative to the current system clock time.
Fix: Make sure that the scheduled notification time is in the future. Examine the system clock time.
For general Windows Store requirements, see Certification requirements for Windows apps.
Build date: 11/29/2012