iOS Push Notifications, Amazon SNS

Today, I set out to find answers for following 2 questions

  1. Can APNS device token change?
  2. Does Amazon SNS handle token changes?

For 1st, I figured that device tokens can change. Apple developer docs mention following
Note: A device token is not a unique ID that you can use to identify a device. Device tokens can change after updating the operating system on a device. As a result, apps should send their device token

Looking at other sources, it seems OS update is not the only event that can change the device token. This includes Device Reset, Wrong Backup Restore (of a different device) and 2 years lifetime elapsed. Refer http://stackoverflow.com/a/7999690

Now, I wanted to know if this can be handled by Amazon SNS, instead of me creating a device token change notification from my app. 
Turns out, Amazon SNS does handle it by disabling the end point, for which GCM / APNS has notified of expiry or replacement. SNS also notifies this through an event.
GCM does a better job in its notification, and also reports the new token along with old / expired one. SNS then, instead of disabling the current end point, replaces the old token with new one. This reduces the overhead of new endpoint creation, and removal of disabled one.

Finally it means, for my iOS app, I will need a notification service from app to notify me of device token change. I will have to create a new endpoint to ensure notifications get delivered. I can (optionally) choose to remove the old endpoint.

Comments

Post a Comment

Popular posts from this blog

AWS RDS incompatible-parameters solved

Recently, I rebooted one of my RDS (Mysql) instance, as it was hanging every now and then.

What should have been a breeze, became stormy. Instance rebooted, and picked wrong Parameter Group. The parameters, understandably, were not set with this instance in mind. The instance went in incompatible-parameters Status (i.e. DB Instance Status).

I figured the issue, and tried to change the right parameter group. BUT, because instance is in incompatible-parameters Status, the change will not be allowed. I tried looking with our friend Google on how to get my instance in Available status again, only to find that people already are in distress, from as long as 2010. There have been no plausible and easy solution to do this. Refer following

https://forums.aws.amazon.com/thread.jspa?threadID=237385https://forums.aws.amazon.com/thread.jspa?messageID=587725https://forums.aws.amazon.com/thread.jspa?threadID=55800 

BTW, I cannot change my Parameters Group values, as that Group is being used in a ot…
Read more

504 Gateway Timeout on Amazon AWS ELB (Elastic Load Balancer)

Faced it recently!!

The Client request is sending large data set to Server. Till date it worked fine on our Test & Staging servers. Put it on Live, and Kaput!!

Checked it across various clients, i.e. iOS, Android, Postman etc. Worked on all, but iOS. Increased time outs for Live to check, but still the same.

Eventually figured, Amazon ELB (Load Balancer) is timing out. ELB's idle timeout was 60 seconds. Increased it to 180 seconds, and Voila! it worked.

Load Balancers are nifty machines to help with keeping one address for outside world, and contain multiple sub addresses internally. ELB accepts the HTTP/HTTPs request which contains the large data set, and maintain a connection with the Client (along with a connection with Server). If client / instance does not send data in the duration specified in idle_timeout, the connection is closed by ELB.


Read more