Amazon SNS 推送至FCM iOS端失效问题咨询

Hey there! Let's break down why your iOS pushes aren't coming through when using Amazon SNS → FCM, even though Android works perfectly and direct Firebase tests work. The key here is that iOS has specific requirements for FCM payloads when routed through SNS, and your current payload structure might be missing those critical details.

First, Fix Your Payload Structure #

Your existing payload has the notification field at the same level as GCM—that's a problem. When sending to FCM via SNS, the entire FCM payload (including iOS-specific fields) needs to be nested inside the GCM key. SNS expects this structure to properly route the payload to FCM, which then translates it for iOS's APNs system.

Here's a corrected payload tailored for iOS (and it'll still work for Android too):

{
  "GCM": "{
    \"notification\": {
      \"title\": \"Your App Notification\",
      \"body\": \"Enter your message\",
      \"sound\": \"default\",
      \"badge\": 1
    },
    \"data\": {
      \"message\": \"Sample message for iOS endpoints\"
    },
    \"content_available\": true,
    \"mutable_content\": true
  }"
}

Let's break down the important iOS-specific tweaks:

• Nested GCM wrapper: Ensures SNS passes the entire payload to FCM correctly.
• notification.title: iOS requires a title for notifications in most cases (Firebase's test page might auto-fill this, but SNS won't).
• badge: Optional but standard for iOS—sets the unread count on your app icon.
• content_available: Triggers background processing for your app (if you need it), while mutable_content allows modifying the notification before it's displayed (useful for media attachments).

Additional Checks to Rule Out Other Issues #

• Verify SNS Platform App Type: Make sure your SNS platform application is configured as a FCM type, not APNs. Since you're routing through FCM, SNS needs to talk to FCM first, not directly to Apple's APNs.
• Confirm Device Tokens: Ensure the iOS device token registered with SNS is the one obtained via Firebase (not a raw APNs token). FCM tokens are what SNS needs to target iOS devices through this flow.
• FCM Server Key in SNS: Double-check that your SNS FCM platform app has the correct Firebase Server Key configured—this is how SNS authenticates with FCM to send pushes.
• iOS Client Handling: Even though direct Firebase pushes work, confirm your app's notification delegate (UNUserNotificationCenterDelegate) handles notifications from FCM consistently, whether they come directly from Firebase or via SNS. The payload structure should be identical once it reaches your app, so the handling logic shouldn't need changes.

Why This Works for Android but Not iOS #

Android is more flexible with FCM payload structures, and it doesn't require the strict nesting that iOS (via APNs translation) does. Firebase's test page automatically handles the correct payload formatting for iOS, but SNS relies on you to structure the payload properly for the target platform.

Give the corrected payload a try, and double-check those configuration steps—this should get your iOS pushes working through SNS → FCM just like Android!

内容的提问来源于stack exchange，提问作者brk