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
Once servers send the right badge number, we might then need client-side logic (or logic in the push bouncer?) to aggregate those numbers, because the app might be logged into different accounts on different servers. E.g., for logged-in accounts A and B, if there are 3 unread notifications for A, and 2 for B, presumably we should show 5 as the badge count.
The text was updated successfully, but these errors were encountered:
Counterpart to zulip/zulip-mobile#438. Quoting from there:
I believe what has stalled that issue is a server-side bug with the payloads we're constructing; see discussion: https://chat.zulip.org/#narrow/stream/243-mobile-team/topic/iOS.20badge.20count/near/938530
Once servers send the right badge number, we might then need client-side logic (or logic in the push bouncer?) to aggregate those numbers, because the app might be logged into different accounts on different servers. E.g., for logged-in accounts A and B, if there are 3 unread notifications for A, and 2 for B, presumably we should show 5 as the badge count.
The text was updated successfully, but these errors were encountered: