tjanczuk / wns Goto Github PK

Are there any issues atm with the npm package?

Exceptions thrown in user code should be left unhandled.

wns relies on nock and mocha for running the tests. Both of those libraries are woefully out of date. I tried updating them but then the tests failed, so I'm opening a ticket.

tags is listed twice, in duplicate.

As of right now, if an application needed to send push to many thousands of recipients, handling the error 401 might be problematic, unless we send the next push in the response of the previous one, which is impractical when so many need to be sent at once.

If for exemple I sent 1000 push in a forEach loop or even by calling setImmediate 1000 times, a problem would occur when the access token expires: An error 401 would come back many times before the first callback could be handled which would allow the app to put the new access token in the options.

Wouldn't it be easier to handle the access token internally with no need to have the client app do it. And knowing when an access token came in, eliminate all the new 401 errors after that, instead of calling obtainaccesstoken again and again?

It should not be an error to pass a payload with text1, text2, etc set to a number or bool. Just use toString on these types.

As per http://msdn.microsoft.com/en-us/library/windows/apps/hh761468.aspx

The launch attribute allows developers to pass a token of data into the application if it's launched from that toast - a very common scenario to allow apps to support contextual/deep link from toast.

Hi @tjanczuk could you help us with this issue?

appfeel/node-pushnotifications#50

Thanks!!

Hi Tomasz,
Just received your mail, and as you said that mention the issues here so, from Yesterday I have been stuck in this error

"Error: The cloud service is not authorized to send a notification to this URI even though they are authenticated."

as a response to my toast notification although fulfilled the requirements which were mentioned in the documentation please help me on this.

Regards

Syed Haider Abbas Rizvi

The latest guidance from Windows is for developers to send both square and wide tiles in a single payload so the user can get the notification regardless of how they've sized their app tile. See the .NET reference implementation provided by the team.

http://msdn.microsoft.com/en-us/library/windows/apps/hh761491.aspx#TileSquare310x310Text03

Windows 8 supports 'attention' icon (http://msdn.microsoft.com/en-us/library/windows/apps/br212849.aspx), but th library returns error in this case.

Can this be updated with new WP 8.1 and W 8.1 templates?

Great plugin. We are currently working on getting wns notifications working for our app and are having a few problems.

When the notification is sent we receive the notification when the app is open and the toasts are coming through as raw. If the app is closed then we see no notification at all.

To send Im using
var options = {
client_id: settings.push.windows.clientId,
client_secret: settings.push.windows.clientSecret
};
wns.sendToastText02(channel, {
text1 : title,
text2 : message
},
options,
callback);
};

on the client it calls the httpnotificationreceived event not the toastnotificationreceived event.

I sended notify successfull but it only send 1 device / request. i want push notification multiple devices in one request. like Android or IOS, where i can send notification to ~1000 devices per request. That's pretty easier. please let me now. thanks u.

We've experienced timeouts from requests to the WNS service. The library should allow us to configure a timeout for the request.

Hi,

When sending a push notification request to WNS, the response header "x-wns-notificationstatus" is being replaced with "x-wns-status". I'm not sure if they have already deleted the old header or if they keep it for the transition, but I guess it will be discarded soon.

Source : official documentation : http://msdn.microsoft.com/en-us/library/windows/apps/hh465435.aspx#send_notification_response