Channels not being vacated
Closed this issue · 1 comments
Ever since yesterday or so, we have been noticing users not receiving pusher events, channels are sometimes not being vacated properly, even though client-side code ensures both, unsubscription and disconnection is done correctly. Debug console logs show disconnection events, however they are not followed by vacated events. Did something break/change within pusher api lately? Our channels are not being vacated properly and also, what we've noticed is that the status of whether channel is occupied or not that is being returned from API is incorrect, depending on which endpoint you're calling and with which params, e.g.
Contacted the pusher team - indeed there was an issue on their end, and they managed to fix it, all looks good now.
