Notification payload is invalid (WNS)

Josu 15

Hello,

I have created a simple code to create and register notification template, I have tried several templates, ones from the examples provided from Microsoft and also an empty one. I use property Templates and method CreateOrUpdateInstallacionAsync(...) and it works perfect without errors.

When I try to use this template using SendTemplateNotificationAsync I always receive this error (It's necessary enable EnableTestSend property) "Notification Payload Is invalid", but if I use native methods like SendWindowsNativeNotificationAsync() it works fine, the result is the same using code or using Azure Notification Hub portal option "Test send".

This result is the same despite I use parameters or not, also SendWindowsNativeNotificationAsync works fine with exactly the same payload.

Notification Hub log does not show more info about these errors, using Sevice Bus Explorer the error is the same.

This code works perfectly without errors with GCM/Firebase and Android, but with WNS it does not work.

Any clue?

Thanks.

SnehaAgrawal-MSFT 21,766 Reputation points

2023-03-09T16:56:21.05+00:00
Josu Thanks for asking question! If you are facing issues with sending notifications, you can use the EnableTestSend property to get detailed debugging information. You can use this property while initializing NotificationHubClient to get a detailed status about push notification service errors that occur when the notification is sent.

You can also check the logs in Notification Hubs to see if there is any additional information about the error.

Further to elaborate on EnableTestSendproperty as mentioned in document link: https://learn.microsoft.com/en-us/azure/notification-hubs/notification-hubs-push-notification-fixer

When you send a notification via Notification Hubs, the notification is initially queued. Notification Hubs determines the correct targets, and then sends the notification to the push notification service. If you're using the REST API or any of the client SDKs, the return of your send call means only that the message is queued with Notification Hubs. It doesn't provide insight into what happened when Notification Hubs eventually sent the notification to the push notification service.

If your notification doesn't arrive at the client device, an error might have occurred when Notification Hubs tried to deliver it to the push notification service.

For example, the payload size might exceed the maximum allowed by the push notification service, or the credentials configured in Notification Hubs might be invalid.

To get insight into push notification service errors, you can use the EnableTestSend property. This property is automatically enabled when you send test messages from the portal or Visual Studio client.

You can use this property to see detailed debugging information and also via APIs. Currently, you can use it in the .NET SDK. It will be added to all client SDKs eventually.

To use the EnableTestSend property with the REST call, append a query string parameter called test to the end of your send call.

For example:

https://mynamespace.servicebus.windows.net/mynotificationhub/messages?api-version=2013-10&test
Josu 15 Reputation points

2023-03-09T16:57:09.4833333+00:00
Now I receive a different error: WNS type is required (Parameter 'RequestHeaders').

I am using this:

var template = new InstallationTemplate(); template.Body = content; // String created with notification template.Headers = new Dictionary<string, string>() { { "X-WNS-Type", "wns/toast" } };

It's exactly the same code as above, same notification hub, etc... nothing has changed
Josu 15 Reputation points

2023-03-10T04:22:33.98+00:00

@SnehaAgrawal-MSFT if you read my original comment carefully you will see that I already use EnableTestSend and also I already have tried all the points mentioned in your document.

I start thinking that the problem is in Notification Hub.

Kind regards,

Josu 15

This sample code in a C# console reproduces the error, my error is with MAUI

static void Main(string[] args)
{
var connectionString = "Place your connection here";
var notificationHubClient = NotificationHubClient.CreateClientFromConnectionString(connectionString, "your notification hub", true);
Installation installation = new Installation();
installation.InstallationId = Guid.NewGuid().ToString();
installation.PushChannel = "Place your channel here";

var template = new InstallationTemplate();
template.Body = @"<toast><visual><binding><text>Test +{$(object)}</text></binding></visual></toast>";
template.Headers = new Dictionary<string, string>() { { "X-WNS-Type", "wns/toast" } };
installation.Templates = new Dictionary<string, InstallationTemplate>
                       {
                            {
                                "WindowsToast",
                                 template 
                            }
                        };
notificationHubClient.CreateOrUpdateInstallationAsync(installation);

var props = new Dictionary<string, string> {
{ "object", "Any string" } };
var n = new TemplateNotification(props);
n.Headers.Add("X-WNS-Type", "wns/toast");
var outcome = notificationHubClient.SendNotificationAsync(n).GetAwaiter().GetResult();

Create installation works fine, but send notification produces the outcome error "The Notification payload is invalid"

Kind regards,

Premiaware di Luca Borriero 31 Reputation points

2023-07-19T12:55:50.49+00:00

I have similar issue, from 17 Jul azure stop sending toast Notification message (only toast, all other type working well).

In the azure console, test message

i can see "The Notification payload is invalid", how can fix this issue?
Yury 26 Reputation points

2023-07-24T07:47:49.12+00:00

I have absolutely the same issue!!!
Josu 15 Reputation points

2024-04-16T18:50:13.8233333+00:00

Now, again without any change in code, suddenly I receive this error:

*The token obtained from the token provider is wrong
*
I receive this error from code or using portal test send feature.

I have reviewed secrets and seems anything has expired, any clue?

1 answer

Josu 15 Reputation points

2023-07-24T09:46:20.09+00:00

Finally it started to work without doing anything, maybe I was banned because using free tier? :) I do not know...

It took around one week before started to work
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Notification payload is invalid (WNS)

1 answer

Your answer