You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
push notification server listens to those topics for any new message
you get removed from that group next sync you process the commit and it sets the group to inactive but the only way you know the group is inactive is because is by going to the group and calling group.isActive() In a sync all the commit would get processed behind the scenes and no unsubscribe would be triggered?
The push notification server is still listening on this topic and sending push notifications for messages in that group that you can no longer decrypt. After receiving one push you can see the decryption error catch it and then unsubscribe but the user would still get one more push?
I see what you're saying. I guess we could add some sort of callback or hook as part of sync to notify the caller that they need to update their subscriptions. Then they could be unsubscribed before the next message comes in (edited)
The text was updated successfully, but these errors were encountered:
I see what you're saying. I guess we could add some sort of callback or hook as part of sync to notify the caller that they need to update their subscriptions. Then they could be unsubscribed before the next message comes in (edited)
The text was updated successfully, but these errors were encountered: