Perché le notifiche push arrivano senza suono solo su iOS?

Perché su iOS il suono richiede il blocco specifico apns.payload.aps.sound dentro il payload FCM v1: senza questa sezione, APNs (Apple Push Notification service) non riproduce alcun suono anche se la notifica arriva correttamente.

La legacy API di FCM funziona ancora?

Google ha dismesso progressivamente la legacy API a favore della v1, quindi è consigliabile migrare alla struttura payload v1 mostrata in questo snippet per garantire compatibilità futura.

Serve una configurazione diversa per il web push rispetto a nativo?

Sì, il web push ha un proprio blocco webpush nel payload FCM v1, distinto da quello Android e da quello APNs per iOS: ognuno ha campi e comportamenti specifici da configurare separatamente.

← blog

JavaScript Firebase FCM Multipiattaforma Push notification

FCM push with guaranteed sound on Web, Android and iOS

Complete Firebase Cloud Messaging v1 payload that guarantees notification sound across all platforms — including the apns.payload.aps.sound block which, if forgotten, makes pushes arrive silent on iPhone.

The problem

A push notification that's "correct" for Android and desktop can arrive completely silent on iOS if a specific payload block is missing. The reason: APNs (Apple Push Notification service) explicitly requires aps.sound, while webpush and Android have a default sound.

Full payload: webpush + android + apns

fcm-payload.js

const msg = {
  message: {
    token,
    // Browser desktop e Android via PWA
    webpush: {
      headers: { Urgency: 'high' },
      notification: {
        title, body, tag,
        silent: false,           // esplicito: usa suono di sistema
        requireInteraction: requireInteraction
      }
    },
    // Android nativo
    android: {
      priority: 'HIGH',
      notification: { sound: 'default', default_sound: true }
    },
    // iOS — senza aps.sound la push arriva MUTA
    apns: {
      headers: { 'apns-priority': '10' },
      payload: {
        aps: { sound: 'default', 'content-available': 1 }
      }
    },
    data: strData
  }
};

requireInteraction: add it in the webpush.notification block for notifications that must stay visible until the user explicitly dismisses them — useful for appointments or critical events, unlike chat messages that can disappear on their own.

Warning: the apns block is mandatory to guarantee sound on iPhone — without apns.payload.aps.sound the notification still gets delivered, but completely silent, and it's a hard bug to spot because it only manifests on a subset of devices.

Why sound and push behave differently in background

In-app, sound via AudioContext only works while the page is open and in the foreground — browsers block audio in non-visible tabs due to autoplay policy. When the PWA is in the background or closed, the only reliable way to get sound is to delegate it to the OS via native FCM push.

Firebase calendar PWA: push notifications and session restore bug — real-world case

→

When you need this push notification pattern

This snippet shows how to build a Firebase Cloud Messaging v1 payload that guarantees sound on web push, native Android, and iOS all at once, including the apns.payload.aps.sound block often forgotten for iOS.

When to use it

Your app sends push notifications across multiple platforms (web, Android, iOS) via FCM and sound doesn't work consistently on all of them.

You're migrating from FCM's legacy API to v1 and need to rebuild the multi-platform payload from scratch.

Notifications arrive but stay silent on iOS while working fine on Android.

When NOT to use it

You only use one notification channel (e.g. web push only) without needing to handle cross-platform differences: in that case the base FCM payload is enough, without the APNs-specific sections.

Alternatives

OneSignal or managed notification services when you want to avoid manually handling differences between Android/iOS/web payloads.

Separate native notifications per platform if the app doesn't already share a common FCM base.

Common mistakes

Forgetting the apns.payload.aps.sound block: without it, notifications on iOS arrive silent even if the Android payload is correct.

Confusing the legacy FCM API syntax with v1, which has a different payload structure (message instead of a flat notification/data).

Not testing separately on web, Android, and iOS: a payload that works on one platform can silently fail on another.

Frequently asked questions about cross-platform push notifications

Because on iOS, sound requires the specific apns.payload.aps.sound block inside the FCM v1 payload: without this section, APNs (Apple Push Notification service) plays no sound even if the notification arrives correctly.

Google has progressively phased out the legacy API in favor of v1, so it's advisable to migrate to the v1 payload structure shown in this snippet to ensure future compatibility.

Yes, web push has its own webpush block in the FCM v1 payload, distinct from the Android one and from APNs for iOS: each has specific fields and behaviors to configure separately.