Live Activity - Firebase Cloud Messaging, APNs iOS 18+

Hello,

We are using the Firebase Admin SDK (firebase-admin framework) to send push notifications via Firebase Cloud Messaging (FCM) for Live Activity updates in our iOS app.

With the introduction of iOS 18, a new key "input-push-token": 1 has been added to the Live Activities push payload structure.

1) Can this new key ("input-push-token": 1) be used when sending payloads via FCM?

We noticed that FCM is still using the push update format introduced in iOS 17.2. Will FCM be updated to support the new push structure introduced with iOS 18? Or is the "input-push-token" feature only available when sending notifications via direct APNs?

2) We are concerned about the expiration of the Live Activity start push token.

If a user doesn't open the app for a long time, the token may expire, and this could result in failed updates. That’s why we are looking into the new "input-push-token" behavior in iOS 18. Do you have any recommendations on how to manage or prevent token expiration? Is there any official guidance on the lifespan of the Live Activity push tokens? Will FCM support the delivery of start/update/end Live Activity actions even when the app is completely terminated? We would highly appreciate any official clarification or roadmap regarding this. It would help us determine whether we should wait for FCM support or switch to sending notifications directly via APNs.

Thank you for your help!

We can't answer what FCM is planning to implement, and when. It is best to contact their support channels for those answers.

The push tokens will expire. You will need to observe the pushTokenUpdates and pushToStartToken properties of the activity to get the new tokens.

We also cannot help with your business decision to wait for FCM or manage your own push servers. That will be a decision based on your business needs.


Argun Tekant /  DTS Engineer / Core Technologies

Live Activity - Firebase Cloud Messaging, APNs iOS 18+
 
 
Q