How do I troubleshoot Firebase Cloud Messaging (FCM) mobile push notification failures in Amazon SNS?
My Firebase Cloud Messaging (FCM) mobile push notifications are failing to send through Amazon Simple Notification Service (Amazon SNS). How do I troubleshoot the issue?
"My Firebase Cloud Messaging (FCM) mobile push notifications are failing to send through Amazon Simple Notification Service (Amazon SNS). How do I troubleshoot the issue?ResolutionConfigure and view push notification delivery status attributes for Amazon CloudWatch LogsFollow the instructions in How do I access Amazon SNS topic delivery logs for push notifications?Verify if you can receive notification's directly from FCMTo see if the issue is on the Amazon SNS endpoint's side or the client application's side, send a test message on the FCM console. For instructions, see Send a notification message (for iOS) or Send a test notification message (for Android) in the FCM documentation.After you send the test notification, the FCM console displays a panel that provides the test notification results. If you don't receive the notification, then follow the instructions in the Confirm that you're using the correct FCM message type section of this article.Verify if the platform endpoint associated with the device that's not receiving push notifications is activated1.    Review your delivery status logs for failed push notification deliveries ("status": "FAILURE").2.    Check the failed push notification delivery logs for the following value: "providerResponse": "Endpoint is disabled". If you see this value in the failed delivery logs, then the platform endpoint associated with the device that's not receiving push notifications is deactivated.3.    If the platform endpoint is deactivated, reactivate it by running the SetEndpointAttributes API action. Running the SetEndpointAttributes API action associates the endpoint with the latest valid device token.Note: For more information, see Re-enabling a platform endpoint associated with an invalid device token in the Troubleshooting section of Creating a platform endpoint.Failed FCM push notification delivery CloudWatch log event example{  "notification": {    "messageMD5Sum": "c8c339cf07dc39c9388253dgc81f257",    "messageId": "fg207f98-0244-6767-96e2-45b1fg451gg8",    "timestamp": "2021-05-25 22:27:51.889"  },  "delivery": {    "deliveryId": "76ab7dcd-f444-5b4f-9d1b-24ea8863d9bc",    "destination": "arn:aws:sns:us-east-1:123456789101:endpoint/GCM/MyAndroidApp/682dc992-a47f-45f7-b980-97727cce0a9c",    "providerResponse": "Endpoint is disabled",    "dwellTimeMs": 28,    "attempts": 1,    "token": "ojnco9nc9weucn9encx9ewunc9nu9w9euncec9necn9xexnexex9encewcerve0f0o0dmco9j",    "statusCode": 400  },  "status": "FAILURE"}Confirm that you're using the correct FCM message typeNote: FCM supports two types of messages: Notification messages and Data messages. Notification messages are handled by the FCM SDK automatically. Data messages are handled by the client app. For more information, see Message types in the FCM documentation and Sending platform-specific messages in the Amazon SNS Developer Guide.If you're processing message data on your client appMake sure that you use Data messages. For more information, see Data messages in the FCM documentation.If you want the FCM SDK to handle displaying notifications on your client app's behalfMake sure that you use Notification messages. For more information, see Notification messages in the FCM documentation.Identify and troubleshoot any FCM error response codes1.    Review your delivery status logs for failed push notification deliveries ("status": "FAILURE").2.    Check the failed push notification delivery logs for any other platform response codes. Then, follow the Recommended Action listed for that code in the Downstream message error response codes section of the FCM documentation.Note: For more information on FCM error codes and troubleshooting best practices, see ErrorCode in the FCM documentation.Related informationMonitoring Amazon SNS topics using CloudWatchMobile push notificationsFollow"