@nmalzieu trying to clean up some of these older issues

I believe we already catch most of these from a push notification perspective (correct me if I'm wrong), but we are not doing syncing only notifications

My understanding of this is is for messages like group updates (member or metadata changes), we will want to sync the group

Is that understanding correct?

@alexrisch yes sometimes the group change notification payload is bigger than APNS / FCM's payload max size and so it fails

We could probably

• compute size of the payload before sending it rather than waiting for it to fail
• when size of the payload is bigger than size limit, send a new kind of notification that just syncs the group

Maybe we can be smarter than that and also understand during the sync what the latest event was and still show a notification but more work for sure

@nmalzieu thank you for the background info, I'll add additional details and add it to the backlog, assigning back to me for now

Dev Direction:

iOS

Update ios/ConverseNotificationExtension/NotificationService.swift to handle new type from backend changes
Add new function to handle syncing the appropriate group for the account and silencing the push notification

Android

Update android/app/src/main/java/com/converse/dev/NotificationParser.kt to parse new type from backend changes
Add new function to handle syncing the appropriate group for the account and silencing the push notification