locked
Windows Push Notification Service (WNS): How to correctly handle response codes?

    Question

  • Hi,

    I am using the Windows Push Notification Service (WNS) to send tile updates and I am not sure how to correctly handle the response codes of the WNS?

    I am already familiar with the WNS for Windows Phone 7 and there exists a documentation (Push Notification Service Response Codes for Windows Phone) of all possible response codes and their combinations. And the required actions (e.g. serverside queing for later retry) are also described.

    I am using Nick Harris WnsRecipe and therefore I would need a complete description like the document mentioned above for the NotificationSendResult type.

    Thanks in advance!

    Bye,

    Sebastian

    Thursday, June 07, 2012 5:09 PM

All replies

  • Dear Microsoft,

    is it possible that a Microsoft employee answers this question? e.g. Nick Harris?

    I have found the following documentation for the response codes: http://msdn.microsoft.com/en-us/library/windows/apps/hh465435.aspx

    But, there is not explained what actions I have to take (if neccessary) for the different response codes.

    For example:

    "X-WNS-NotificationStatus: dropped

    The notification was explicitly dropped because of an error or because the client has explicitly rejected these notifications. Toast notifications will also be dropped if the device is offline."

    If the notification was dropped, how can I distinguish between an error or an rejection by the user? In the case of an error my server might want to retry the operation a few minutes later. In the case of an rejection my server will skip a retry. Or, what does it mean that the toast notifications will be dropped if the device is offline? The documentation told me that the WNS caches notifications by default if the device is offline and delivers the notification as soon as the device is online again!

    Please provide more documentation how to handle all these situations! Otherwise it is not possible to provide a good user experience!

    Thanks in advance!

    Sebastian

    Saturday, June 16, 2012 12:36 PM