Quantcast
Channel: Service Bus forum
Viewing all articles
Browse latest Browse all 1916

Notification Hubs issues uncovered in documentation

$
0
0

Hi,

I've got two important in my opinion questions on Notification Hubs that are not covered enough in the documentation.

1) Registration time to live and Apple token expiration:

http://stackoverflow.com/questions/23823813/azure-notification-hubs-registration-time-to-live-90-days-limit

2) APNS Feedback service handling:

http://stackoverflow.com/questions/23825835/how-does-azure-notification-hub-handle-expired-apple-tokens

It would be great to have answers on this question not only on StackOverflow, but in the documentation too.

UPD

Just to illustrate both questions here are some examples:

  1. Client sends its push token to backend on day 0.
  2. Backend stores push token to DB with current date. Then it creates registration in Notification Hubs.
  3. On day 91 an event occurs that triggers backend to send push notification. In APNS the token is still active. But Notification Hub treats it as expired. Notification is not delivered.

Let's try to fix it. On step 3 before we send notification backend checks if more than 90 days passed and do re-registration if it's needed. But what happens if the token was really invalidated by APNS feedback service?

So I think the expiration period for APNS should be unlimited by default. By now as it's said in the documentation it's not even possible to configure (max. expiration period is 90 days).



Viewing all articles
Browse latest Browse all 1916

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>