Apologies for late response here! Sharing below inputs about rich iOS push notifications might be helpful.
This docs seem to indicate that rich notifications are implemented via silent notifications with custom properties on the payload (see above richId,
richMessage,
richType`) that the iOS application code then has to intercept and handle (documented in the provided link).
Sorry we don’t have specific docs for this scenario, but it’s possible to infer the payload format from the linked docs:
var aboutUser = "{\"aps\": {\"content-available\": 1, \"sound\":\"\"}, \"richId\": \"" + richNotificationInTheBackend.Id.ToString() + "\", \"richMessage\": \"" + richNotificationInTheBackend.Message + "\", \"richType\": \"" + richNotificationInTheBackend.RichType + "\"}";
{
"aps": {
"content-available": 1,
"sound": ""
},
"richId": "<richNotificationInTheBackend.Id>",
"richMessage": "<richNotificationInTheBackend.Message>",
"richType": "<richNotificationInTheBackend.RichType>"
}
Further I will reach out to concern team for this as document feedback and document enhancement.