FCM ttl property is not respected

Viewed 15

Seems like ttl property for FCM Android config is not being respected. I disconnected my device from internet for 24h, sent multiple notifications throughout the day and once reconnected, I received every single one of them. I have set the ttl to 35s.

My notification request looks like this:

{
  "message": {
    "android": {
      "priority": "HIGH",
      "ttl": "35s"
    },
    "data": "<data>",
    "token": "<token>",
  }
}

I'm using the new new FCM API, not the legacy. Any ideas why ttl is not being respected? Could it be that data notifications are always delivered?

0 Answers
Related