- 新しい順
- 投票が多い順
- コメントが多い順
It appears that you're encountering issues related to throttling and potentially unstable delivery of push notifications. Here are some steps to help diagnose and resolve the issues:
-
Inspect CloudWatch Metrics: First, review the CloudWatch metrics for your SNS topic to check for any throttling or delivery failures. You can do this by navigating to the CloudWatch console and selecting "Metrics," then choosing the "SNS" namespace. Look for the
NumberOfMessagesPublished
,NumberOfNotificationsDelivered
,NumberOfNotificationsFailed
, andPublishSize
metrics. -
Review SNS retry policies: SNS has a default retry policy for message delivery. In case of delivery failures, SNS will retry sending the message according to the policy. However, if the failure persists, the message might not be delivered to all subscribers. Review the retry policy for your topic and make adjustments if necessary: https://docs.aws.amazon.com/sns/latest/dg/sns-message-delivery-retries.html
-
Check the message size: The payload size limit for SNS push notifications is 256KB for iOS. If the payload exceeds this limit, the notification will be rejected. Ensure that your message size is within the limit.
-
Rate limiting: If you're sending a high volume of notifications in a short period, you might hit rate limits on the SNS or APNs side. Ensure that you're adhering to the rate limits imposed by both services. You can also consider implementing a backoff strategy to prevent hitting these limits.
I am facing this same issue using SNS for iOS Live Activities.
Did you ever find a solution for this problem?
I am considering moving away from SNS if it is not a reliable way to deliver Apple Push notifications.
関連するコンテンツ
- AWS公式更新しました 9ヶ月前
- AWS公式更新しました 5ヶ月前