Getting “EndpointDisabled” from Amazon SNS

Question

I\'m using Amazon SNS. Notifications work well, but sometimes I get this error:

{
    \"message\": \"Endpoint is disabled\",
    \"code\": \"EndpointDisabled         


        

Answer 1

There are few reasons why an end point can be disabled. I didn't see it documented anywhere (might have missed it), here's what I got from support:

• You push to an endpoint but the token is invalid/expired. Tokens become invalid if:

• It belongs to an app that is no more installed on the device.

• If device has been restored from backup. This renders token invalid and your app should request a new token and update SNS endpoint token accordingly.

• App has been re-installed on the same device. In case of Android, the app is assigned a new token. This happens as well with APNs but more often with Android.

• In case of APNs, a wrong provisioning profile is selected in xCode. In this case notifications fail and device becomes disabled later after APNs feedback.

• If mistakenly use a token for IOS development to IOS production app and vice versa.

• If Apple for any reason invalidates your IOS push cert or someone revokes the push cert from itunes connect portal. This takes a few hours before device gets disabled.

• Same with GCM if you update API key from Google developer console without updating the Platform application credentials in SNS.

• You push to an APNs device endpoint but application has been disabled due to expired push certificate.

• You push to GCM device endpoint however API key has been updated in Google developer console but not the SNS platform application credentials accordingly.

For Details, I recommend this excellent article which solves my problem