SNS uses which version of Firebase Cloud Messaging API?

Same here, a timeline by AWS would be nice.

Hello, I just upgraded my platform application. However, according to https://firebase.google.com/docs/cloud-messaging/migrate-v1#update-the-payload-of-send-requests the message payload structure changed significantly and breaks the legacy message payload structure. Upgrading to the FCM v1 API is therefore no one-click upgrade! I'm trying to test the new payload structure via AWS' "Publish message to endpoint" test environment. However, there are no docs how the new payloads have to be structured in SNS and specific GCM payloads don't really seem to work. Fields in the "apns" object don't seem to get picked up, the messages go through and are sent to my iOS device but APNs-specific fields like "subtitle" and "sound" seem to be ignored. Tested payload:

{ "GCM": "{ \"notification\": { \"title\": \"Title\", \"body\": \"Body\" }, \"apns\": { \"payload\": { \"aps\": { \"alert\": { \"subtitle\": \"Subtitle\" }, \"sound\": \"default\" } } } }" }

Update: following my SNS failure messages in CloudWatch, it looks like SNS GCM.notification is mapped to the new FCM message.android.notification object which is very wrong! The GCM object has to be mapped to the FCM message object, which would map GCM.notification to message.notification, GCM.apns to message.apns and GCM.android.notification to message.android.notification. Please fix this ASAP as SNS push notifications via FCM is unusable with the HTTP v1 API right now!

Firebase API specification: https://firebase.google.com/docs/reference/fcm/rest/v1/projects.messages

For further clarification as this faulty new API support persists since days, here's a SNS error where I tried to include "subtitle" in the GCM.notification object (I know, via the new HTTP v1 API specification, "subtitle" should appear in a nested "apns" object but it clarifies that GCM.notification is somehow mapped to message.android.notification): { "notification": { "messageMD5Sum": "...", "messageId": "...", "timestamp": "2024-01-22 09:46:53.463" }, "delivery": { "deliveryId": "...", "destination": "...", "providerResponse": "{"code":"400","message":"Invalid JSON payload received. Unknown name \"subtitle\" at 'message.android.notification': Cannot find field.","status":"INVALID_ARGUMENT","details":[{"@type":"type.googleapis.com/google.rpc.BadRequest","fieldViolations":[{"field":"message.android.notification","description":"Invalid JSON payload received. Unknown name \"subtitle\" at 'message.android.notification': Cannot find field."}]}]}", "dwellTimeMs": 49, "token": "...", "statusCode": 400 }, "status": "FAILURE" }

We are having problem at our end aswell, using the TOKEN based authentication breaks exiting and working push capability using AWS APIs. I can't really see any documentation that the message format has been updated towards AWS with the new authentication.

We are also getting a 400-error with invalid json payload message.

@ValHus @Czyze Sounds bad! Have your opened a support ticket regarding this issue? If so, what was the answer?

Same here. We're now considering moving away from SNS and implementing FCM Admin SDK directly on our servers as a last resort before June 2024.

Ryan, are you able to provide an update on this? I've now received the notice of discontinuation from FCM that the legacy API will no longer be available after 20 June 2024, so very keen to understand timescales for AWS to make the v1 API available to support migration and testing well in advance of this deadline. Thanks.

This matter is crucial for us as some functionalities, particularly analytics labels, are currently not working as expected. The accurate functioning of these features is integral to our operations. Given the impact on our analytics and overall workflow, could you please provide me with the current status or any updates on the matter at your earliest convenience?

@Ryan_A: Time is running out, after 9 months we really need a confirmation that AWS will migrate to the new API in time, otherwise we have to switch to another solution.

any news for this? tnx

Will there be any news? We need to know if we need to program custom solution to work directly with new Firebase API or we can continue using SNS for this.

Do you have an update on this? Please see my answer re. recent announcements from Firebase.

Could you please give us an update on timeframe to launch support for this please? If AWS do not support this, it will become impossible to use SNS to send Android push notifications. This is a core requirement for SNS and we will be forced to switch platforms if we can’t get a reasonable idea of when you will support this.

Hello, is there any update to this please?

Hi, we would also be interested to hear any update here. We are concerned that we may need to migrate to another solution to maintain Android push notification support if there is no news about a timeline in the coming weeks.

Can anyone suggest alternatives to send Push Notifications from AWS to Android devices if AWS fail to provide an update on this in the short remaining time available?

Hi Ryan, I hope you are well. As this deadline approaches, we are starting to consider migrating to another provider to avoid any interruption. Can you provide any update or guarantee that AWS will complete their migration in time, so that we can avoid switching provider?