Critical notification and data.tag attribute

data.tag attribute is used to achieve several features. Some of them are not supported by iOS in conjunction with critical notifications (like replacing critical notification) others are supported.

Anyway, I noticed strange behavior, and later on narrowed it down to tag attribute usage.

When:

  1. message is actionable
  2. message is critical
  3. message contains tag

The first message sent works as expected. In particular, it opens a popup with actions to be selected.
Let’s leave this message untouched and send the same notification again.
After that:

  1. previous notification is not accessible
  2. the phone shows notifications but it’s not able to show its preview nor open popup with options. The only possible thing is to click on it opening HA application.

Are we aware of such behavior?
As I mentioned earlier, documentation says:

iOS does not support replacing critical notifications.

But it doesn’t say it breaks them.
In my understanding "doesn’t support’ mean the feature doesn’t work / setting is ignored.

The app doesn’t do anything for this, but it’s possible on Apple’s side they’ve broken the secondary messages with a tag. I believe it functioned before, are you using iOS 16?

Yes, on iOS 16.0
But I’m almost sure it was the case in 15.x too

in addition to the previous findings, looks like using apns_headers.apns-collapse-id together with critical messages ends up with the same issue.